SagePay problem, VSP Protocol

[Paragon]

Thanks Chris, look forward to an Actinic answer that I trust.
I can't do anything till I get back this evening anyway

I knew this forum wouldn't let me down

[Darren B]

do you have paypal setup, i always recommend that people have it as a backup, besides alot more people use it these days so could increase sales (i cant belive i just said that, i always hated paypal but i guess things move on)

[Kiran]

Hi All

I can confirm that Version 7.0.7 does use Protocol V2.22, you can check this by looking for the following line in OCCPROTXScriptTemplate.pl (usually in C:\Program Files\Actinic v7\OCCUpgrade\CommonOCC)

$sHiddenValues .= "<INPUT TYPE=HIDDEN NAME=\"VPSProtocol\" VALUE=\"2.22\">\n";

You can use the latest V7 Payment Service Provider(PSP) installation file if you need to upgrade. I've attached a zipped file to this post. Ideally though you should be on version 7.0.7, the patch is available for download from HERE.

Important: If you are upgrading please remember to have backups, and if you just want to install the latest v7.0.7 PSP setup you will need to firstly shutdown Actinic, then uninstall "Actinic Payment Service Provider Component V7" through Control Panel | Add/Remove Programs and then run the attached .exe file , when you reopen Actinic again your site will go through the PSP upgrade.

[jxm28788]

PORTANT - EXISTING USERS
Before upgrading:
- Back up your site
- Suspend ordering on your site
- Wait for about half an hour and download any orders
After upgrading:
- Refresh your site
- Re-instate ordering

Refresh? Noooooooooooo.... that'll take forever on my big site...

[Duncan Rounding]

Does this only affect the older protocol versions v2.20 and v2.21 in Actinic versions earlier than v707?
In other words is v2.22 OK in the more recent Actinic versions v707 onwards?

[jxm28788]

Just in from my other PSP, Secure Trading...

"As we are currently experiencing an outage with our Primary ISP and are liaising with them to resolve issue as a matter of urgency, you can, in the meantime ,direct your payments to one of two alternative sites:"

Really? FFS. On the same day??? Are you kidding me? Do I need to find a 3rd backup now?

[guccij]

Do I need to find a 3rd backup now

PayPal. Just PayPal.

From another confirmed PayPal sceptic, who recently saw the light.

[jxm28788]

Never! or at least not until they are protected against chargebacks. And stop freezing peoples accounts and holding onto their money for over a month because they allegedly think they saw some suspicious activity on the account - yes, it was ME, trying to get MY money out of my paypal account!

[Paragon]

Yes, we have Paypal as a backup/alternative...

Tried the Actinic provided solution, but on restarting Actinic it did not go through the upgrade? (we are using Windows 7 ???).
So I just changed the OCCPROTXScriptTemplate manually from 2.20 to 2.22, uploaded and it seems to be working.

[gcamley]

Does this only affect the older protocol versions v2.20 and v2.21 in Actinic versions earlier than v707?
In other words is v2.22 OK in the more recent Actinic versions v707 onwards?

The problem, by Sage Pay's own admission, is limited to their pre 2.22 protocols.

The latest PSPSetup.exe installers for v6 through v9 all work with protocol version 2.22.

The problem will arise for customers not running the latest v6 or v7 releases or if they upgraded to the latest Actinic version without running the latest PSPSetup.exe installer.

Downloading and running the latest PSPSetup.exe installer will ensure that protocol 2.22 is used and therefore avoid the problems being encountered with earlier protocol versions.

[Paragon]

Downloading and running the latest PSPSetup.exe installer will ensure that protocol 2.22 is used and therefore avoid the problems being encountered with earlier protocol versions.

Didn't work for us, Actinic software didn't automatically start the upgrade process when restarted. I manually changed the Protx script template from 2.20 to 2.22 and it seemed to work..

[jxm28788]

Can someone from tech support let me know if there is a shorter way to upgrade just the protocols without having to upgrade the software?

I have a lot of sites so if the upgrade introduces a problem I suddenly have a big problem on a lot of live sites (which are currently working fine, albeit without protx).

Also, the instructions say to suspend trading requires an upload of every single page of the site. So for my big site that means it will have to update every single page with the suspended message, then during the refresh it has to delete all of the pages (which seems to take an abnormally long time!) and then re-upload all the pages, then unsuspending requires all the pages to be uploading again (without the suspend message). Based on previous experience that would take about 2 days!!!!

[gcamley]

Didn't work for us, Actinic software didn't automatically start the upgrade process when restarted. I manually changed the Protx script template from 2.20 to 2.22 and it seemed to work..

Probably the version used in OCCUpgrade.ini had been manually incremented. If the version in the latest file is not higher than the version used for the last upgrade then the upgrader will not kick in.

If after installing PSPSetup.exe the PSP upgrade does not kick in when Actinic is started then edit the OCCUpgrade.ini file and set the version number at the top of the file. To determine what to set it to; look in the OCCVersions table of the DB ActinicCatalog.mdb find the highest listed version number and use this plus 1 in the OCCUpgrade.ini file.

While editing the protocol version may get the interface working there would have been other changes to the script that you will be missing. Using the PSPSetup.exe will ensure that you have complete support for the new protocol.

[gcamley]

Can someone from tech support let me know if there is a shorter way to upgrade just the protocols without having to upgrade the software?

Using the PSPSetup.exe is the easiest and quickest way to upgrade.

Actinic always advise on the safest way to upgrade but when upgrading the PSPs it is not really necessary to suspend the site. The upgraded site will be able to read any payment authorisations from the server whether they were created using protocol 2.22 or an earlier version.

I would still advise taking a DB backup just to be safe though.

[jxm28788]

Do you have a link to the PSPsetup?

Thanks.