Script error after customer account checkout

[gloescher]

Hi folks!
I have user accounts set up with access to a wholesale price schedule. Authorize.Net processes the credit cards and the transaction goes through, but on the return from transact.dll I'm getting this General Script Error:

"Sorry, but we found your account but couldn't read the details. This may be because the login page you used is an old copy stored in your browser cache. Press the Browser Back button, then refresh the login page and try again."

Refreshing the login page has no effect.

I've tried recreating several accounts and refreshing the site, but that didn't help.

Any ideas? I'm tearing my hair out here.

Thanks,
Gary

[cdicken]

I have not seen this one before. Have you tried doing a 'Web | Rerfresh Website' to re-send up all the perl files and the custom account files? If this does not work then I will run it past the development team.

[gloescher]

Hi Chris,
I refreshed the site a couple of times, made sure there weren't any locked order files sitting around, and rechecked file permissions just to be sure.

It might have something to do with the old Authorize.Net web interface code. I hear there's a new version coming out soon that complies with Authorize.Net's new access methods--maybe that will fix the problem. It just seems strange that the non-account transactions work fine...Hmm. I just had a thought. I wonder if it has something to do with sessions not being carried over after bouncing back from transact.dll? Maybe Actinic loses the login.

Gary

[BPJSURF]

I am working on this issue with Gary (fyi Chris)..
I think the problem is most likly caused by the fact that the account is logged in and when completing checkout with Auth.net the browser then leaves the Actinic site and goes too the Auth.net to complete the card processing.

Authorize.net then directs the browser back to the confirmation page. But because the browser is expecting to go back to a logged in sesssion and UAth.net does not direct back to a logged in session you get a failure. This is my best guest.

I am testing the Sims implementation of Auth.net and will post results when I have completed the task.

Brian

[gloescher]

And by the way, Brian had a good workaround for the time being...to disable credit card processing for customer accounts and just collect the info for offline handling.

Gary