SagePay secure server freezing

[dovroc]

Hi,

Please excuse me if this is discussed in a different thread but I haven’t been able to find a solution.

I have just upgraded to v .9.0.4.
When I choose the “pre-authorise transactions” option within the SagePay configurations, I get a message on the SagePay payment page saying:
4006 : The TxType requested is not supported on this account. The value was DEFERRED.

A colleague of mine told me a certain file needs altering within actinic to enable pre authorised transactions.
If I choose the option to take the payment immediately everything works fine.

Any ideas ?

Thanks

[Buzby]

I thought Preauth was now discontinued which may explain the error.

As far as I am aware the current settings are Authenticate and deferred.

Kind regards

Jason

[dovroc]

Up untill this morning I had it working, the problem sems to be that the upgrade has overwritten changes we made to an Actinic file.

The original details of how to make it work and which files to change were posted on the forum a long time ago, but I can't find it anymore.

[grantglendinnin]

Pre-Auth has not been 'discontinued', a few Actinic users had issues with Pre-Auth taking the payments immediately, as far as I know this has been fixed.

In v9.0.4, the SagePay details (vendor name, secret key, encryption key, e-mail address) are edited within Actinic. Previously, in 9.0.3 and before, you had to edit the OCCProtxScriptTemplate file with your SagePay/Protx password and e-mail address.

I would suspect if you have put your settings in to Business Settings > Payments > Sage Pay-Configure Method and it still does not work after a Site Refresh, then you may have a deeper problem.

Help>Troubleshooting>Website Purge and Refresh. Select the option to replace .cat and .fil files, as well as the option for excluding images, then let it run.

If that still doesn't work, post back - there's more solutions but this is just a starting point to ensure you don't have any corrupt scripts causing the issue.

[dovroc]

thanks a lot for you suggestions, which i have followed, but I am still getting the same error message.

[TraceyHand]

I have to admit that I was somewhat confused after I upgraded.
The "configure payment" screen has 4 entries where it previously had 2
It wasn't initially clear to me (not this week anyway, been groggy all week..my excuse ) what went where as it's SO long since I was in this tab!

Hopefully screenshot will clarify a bit. It's very likely that it's more to do with incorrect information entered into prompts than anything else



If you have already editted the script, maybe it will help to go back to the beginning.

Close Actinic.
Copy the original OCCProtxScriptTemplate from the Program Files > Actinic V9 > OCCUpgrade > CommonOCC folder into your SITE1 folder (or whatever your site is named in My Documents > Actinic V9 > Sites)

Then reopen Actinic and enter the correct details into the "Configure Method" prompts in Business Settings > Payment & Security

I'm hoping that just editting these settings will be enough to prompt Actinic to re-upload the payment files.
You'll just need to make sure you have your original Protx/Sagepay Secret Key to hand, in case you have overwritten it in error.

[dovroc]

I have tried to reenter the details and also changing to the old script. If I choose to take the payment immediately everything works fine.

The specific problem is the pre-authorized transaction option, which Actinic is not configured correctly to use. I have checked with SagePay and all their settings are correct.

[Mike Hughes]

The specific problem is the pre-authorized transaction option, which Actinic is not configured correctly to use.

If Actinic isn't working correctly then you'll need to contact support.

Mikr

[Novicebuild]

Sage Pay Error message

This transaction attempt has failed. We are unable to redirect you back to the web store from which you were purchasing. The details of the failure are given below.


Status: INVALID


Status Detail: 5030 : Unable to decrypt the request message. This might be caused by an incorrect password or invalid encoding


I am getting this message after upgrade

[Novicebuild]

This transaction attempt has failed. We are unable to redirect you back to the web store from which you were purchasing. The details of the failure are given below.


Status: INVALID


Status Detail: 5030 : Unable to decrypt the request message. This might be caused by an incorrect password or invalid encoding


I am getting this message after upgrade

Have now resolved by re inputting secret key,encryption key & email address in 'business settings' and 'configure'.

[dovroc]

Is there anyone out there using SagePay witht he pre-authorise option for taking payments?

I am interrested to hear how upgrading went.

Thanks

[grantglendinnin]

Looking at feedback - the upgrade didn't seem to go down well.

Have those using Pre-Authorise Payments got things working OK now?

[dovroc]

I can't say I have.....
Actinic support tell me it is a Sagepay issue, and Sagepay say it is an Actinic issue.

[Duncan Rounding]

Try contactiong Joe at SagePay - he's been very helpfiul sorting out issues recently:
http://community.actinic.com/member.php?u=9622
or:
http://community.actinic.com/showpos...6&postcount=61

[mpwildeman]

SagePay 9.04

Hi,

I have another problem related to SagePay after an upgrade to 9.04.

Was on 9.03 and everything fine.
Upgraded to 9.04 and refreshed website, but when doing tests and I get to the end of the checkout process and select "Pay by Sage Pay.." I get a CGI script error

http://www.bigmatts.com/cgi-bin/os000001.pl

CGI Error
The specified CGI application misbehaved by not returning a complete set of HTTP headers.

I have tried updating the settings in "Businesss / payments.." And reconfiguring SagePay, then refresh but the same error keeps happening. I tried everything, restoring the site backup prior upgrade. Changing scripts back to prvious version etc but still no good.

BTW - SagePay instructions still talk about amending scripts manually.

Finally I have uninstalled v9 and reinstalled v903. Then restored backup of site pre upgrade.

What a nightmare! I'd spent all afternoon sorting this out, god know how many orders I lost because of it! Not a happy bunny.

I'm not going to upgrade again until I can find out why this happened.
Any ideas?