IMPORTANT: SellerDeck for Sage Pay v3

[skinnybloke]

All - I have just had a major issue upgrading my client's sites to use Sage Pay v3 which has resulted in 2 days of downtime and having to upgrade the hosting package.

You need to check with your hosting company that the server your website is hosted on has the Crypt::SSLeay module installed otherwise you will get the error 'Error initialising payment service. Please try another payment method' when trying to make a payment.

See http://community.sellerdeck.com/showthread.php?t=56243

Surely this should be in the pre-requisites for this upgrade.

It is not even mentioned in the upgrade actions - see http://community.sellerdeck.com/showthread.php?t=56261

Also this upgrade does not even appear in the latest release notes for v12.

Very sloppy Sellerdeck

[kev67]

This is getting stupid...I've had a ticket open with Sellerdeck since last Thursday over this and they aint being that helpful
Why does this upgrade appear to work for some and not others like me?
Sage say my site is not hitting their server
My host UKFast have the latest Perl 10 installed and it's fine with Sage V.23, but SD V14.03 don't wrok beyond the "Proceed" button on the Sage payment page

Nothing happens apart from a 500 error - Sellerdeck have a snapshot of my site and can't even put it on their server to test it....What utter mental service is that?

Sage have been inundated with complaints and blame Sellerdeck

Has my site been badly upgraded? - How do I know if it has or not?. In the CommonOCC folder I have the new OCCSage script and the old OCCProtx scripts, are they arguing with each other, should they be there? - I don't bl***y know

ARRRRRRRGH

[skinnybloke]

Have you asked your hosting company if they have the Crypt::SSLeay module installed?

[kev67]

Yeah, they have said yes and it's Perl version 10, so that has the Crypt::SSLeay module

I asked them twice to make sure

[skinnybloke]

...and youve obviously logged into mysagepay website and added your website's IP address

[kev67]

I have this exact version installed perl-5.10.1-136.el6_6.1.x86_64 and have every IP address I can find listed by doing the DNS check

I just don't know why I'm so unique in this not working for me. Sellerdeck support have not replied to me since Wednesday about this. If they can't even put my snapshot on their server, then how on earth can they confirm or deny it's not a Sellerdeck issue

[PA.com]

I was only able to establish the IP address by being on the phone to Sage Pay, and putting through an order from my site at the same time they were logged on to my account. The lady on the phone was then able to identify the correct IP address, which actually bore no relation to any of the previous ones I had identified through Whois etc. Have you tried this?

[kev67]

I know what you mean, but the guy was on my account just like the lady was for you and he couldn't see nothing at all

That's when he blamed SD for this. Because I'm not an 'IT' person, I seem to be 'piggy in the middle' and I'm getting really bad help over this - especially when Sage say to me that there are other ecommerce packages out there !!

Whoopie doo, I've had SD for years and you can't just bin off your software, but this entire upgrade stuff and Sage is utter crap, and crap support when everyone is blaming the other - the average user and even web designers are having trouble with this

I really am so angry about this, I'm fuming

[kev67]

I was only able to establish the IP address by being on the phone to Sage Pay, and putting through an order from my site at the same time they were logged on to my account. The lady on the phone was then able to identify the correct IP address, which actually bore no relation to any of the previous ones I had identified through Whois etc. Have you tried this?

Would you be prepared to send an image of your IP settings on Sage?

But list what you thought was your IP address that you entered, but that of the IP address that Sage said is the correct one as this is "Wood for the trees" and if it becomes an IP address issue, then I'm going to kick someone's "A***" over this

[PA.com]

Actually I have just checked again with Sage Pay, and the actual IP that worked was actually similar to the ones I had derived (my mistake). The first two parts of the IP address were the same, but the last two parts were different. I'm sorry that method doesn't seem to work for you though. Maybe your hosts could give you a fuller list of addresses that relate to your server?

[janep]

this information should be in the release notes

not in a note tucked away in the community

this information is absolutely key to the installation working and yet the release notes i got with my download dont mention anything about checking Perl

so now i have no SagePay payments until my hosting company can install the relevant bit for me sometime next week

way to go SellerDeck!!

i definitely wont be upgrading and am looking for a replacement with advice from SagePay as to who worked with them in a timely manner to get support for this upgrade in place

i had full developer information from SagePay before SellerDeck even acknowledged that they would have to do anything about this and then they leave it the last minute and force a large number of their customers into a precarious position risking their companies not being able to take payments for order

[kev67]

Hello Jane

Go to this thread at the bottom where there is a bit more information, plus there is a dedicated email address that was setup yesterday afternoon for customers to contact Sellerdeck about the upgrade. It does work, although my experience over this was 10 days and it’s not actually Sellerdeck’s fault. “You’re” stuck in the middle of Sellerdeck upgrade, Sage and your host server company

This is the latest Perl script, so ensure your host server company has this installed for you

Perl-5.10.1-136.el6_6.1.x86_64 that has the Crypt::SSLeay that is required

http://community.sellerdeck.com/show...594#post349594