Sage Pay upgrade, do we need to do anything?

[TJWM]

Received this e-mail (beow) from sage pay today, do we need to do anything?

Hello,

Preparation for Sage Pay’s system upgrade will commence on Saturday 17 April 2010 at 22:00

We are now ready to start preparing our system for the essential upgrade as outlined by our MD, Simon Black. Once complete this will dramatically enhance the service you receive from Sage Pay.

Please take time to read the important information below and where relevant pass on to your technical contact.

If you have any questions or need assistance with any of the below, please don’t hesitate to contact our 24-hour support team on 0845 111 44 55 or email support@sagepay.com

What’s happening on Saturday 17th April?

This phase of the upgrade will involve moving the Sage Pay Live Payment Gateway service across to our Disaster Recovery (DR) site, which will enable us to rebuild our live site into the much improved and upgraded system. The new hardware enables us to increase the speed and capacity of our systems and will ensure that we are able to cope with predicted demand over the coming years.

Work will start at 22:00 on Saturday 17th April 2010. The upgrade has been carefully planned to minimise disruption to you and your business and the only potential risk of downtime will be the time it takes the internet Name Servers to pick up our new IP addresses. This could be as little as a few seconds, however it may be slightly longer — unfortunately we have no control over the internet Name Servers except to suggest how often they check for new addresses.

Important technical information

We will be changing the IP Address of the following domains during this upgrade: live.sagepay.com, test.sagepay.com and www.sagepay.com – The Sage Pay Live payment gateway address, our test environment address and our website.

How does this affect me?

You will need to make some technical changes to your website if ANY of the following statements are true:

1) You have hardcoded your IP addresses within your website/shopping cart

2) You have cached your DNS entries

3) You have firewall rules in place to only accept access to and from your systems from specific IP addresses

Download technical details you need to configure your systems

Please note: If a 3rd party is hosting or providing your shopping cart, they will need to make changes and will need to download our technical document . We will do everything we can to notify the 3rd party, however we strongly advise you to forward this email to them too.

If you answer NO to all of the above:

You will not need to make any changes to your website and your transactions will not be affected by the IP Address switch. Your local DNS server will automatically update with the correct IP Address

Once again, if you have any questions, at all, please don’t hesitate to call our support team anytime on 0845 111 44 55 or email support@sagepay.com

Thank you for your continued support, while we work to upgrade our systems.

Kind regards

The Sage Pay Operations Team


Download technical details HERE

Download technical document HERE

[martindowling]

I've also received this email and am at a loss as to whether I need to do anything.

Searching on Google for anything on this I came across this thread on the Sage Pay forums which seems related

https://support.sagepay.com/forum/To...1.aspx#bm11082

[Darren B]

Looking at this, i would say you dont need to do anything, this is a server change so its a DNS update, although you will experience some downtime everything should be settled within 24hours.

Actinic does not use IP's but full url's

[martindowling]

Looking at this, i would say you dont need to do anything, this is a server change so its a DNS update, although you will experience some downtime everything should be settled within 24hours.

Actinic does not use IP's but full url's

Thank you.

So, does this mean that there could be up to 24 hours when Sage Pay will not be working?

[Darren B]

possibly but it all depends on what sagepay are going to do to minimise it, they might route the traffic to the new ip's but this could cause SSL problems

You will need to ask them about expected downtime

[debi]

Going through main server to host server

Do I need to do anything if I go through 1 server (the office one) to my host server? I always have problems when there is any kind of change as I have to go through the main server first which has every kind of firewall and security measures possible!!

[JulieB]

Sagepay not Working with Actinic after Upgrade

Just spoke to Sagepay there appears to be a problem with Actinic websites after upgrade.

They are investigating will let you know if and when they call back

[plantsforshade]

The error seems to have been sorted, sage pay emailed very quickly to say they had resolved the issue with Actinic shopping carts. No orders lost, but a few customers paying 2 or 3 times !

Sagepay support seems on this occasion to be very good, though I would question the logic for doing an update on a Saturday night ! At least they are there on Sundays and not doing it, then going home for the weekend.

Nigel

[Buzby]

We are still experincing customers ordering 2,3 or 4 times due to problems with Sagepay.

Sagepay say that the issue is with my host caching the DNS.

My hosts response will be, as always, Actinic is a third party software and we do not support it, contact Actinic.

Any ideas on where the fault is before I start pushing my host?

Many thanks

[Chunkford]

What version of Actinic are you using? does this help - http://kb.actinic.com/activekb/quest...TX+to+Sage+Pay

[janep]

SagePay URLS changed - no update for v8

Hi
I am still using v8 as both v9 and v10 have problems with my layout and i dont have weeks to spend totally redoing everything from scratch

I changed the URLs in the Protx OCC file and thought everything was going to the correct ones

however SagePay inisist i am still using the old ones - these must be hardcoded somewhere as i have changed every instance i can find
and no update has been released to bring v8 up to date

is this a ploy by Actinic to get people to upgrade?

regards
jane

[Jan]

Go to your site and place an order, look at the URLs that are used and you will be able to see if you are using the right ones. I thought I had upgraded but when I checked like this last week saw that I hadn't.

Regards,

[jxm28788]

I upgraded all my sites to the new ones weeks ago, and tested them to make sure they were using the new URLs - now this morning I find that the protx 'payment pages' go to a protx holding page telling my customers I'm using the old URLs!

Anyone else got this?

[jxm28788]

and strangly the URL that comes up with this error is:

https://live.sagepay.com/vps2Form/submit.asp

which looks like the new urls (off the top of my head).

[jxm28788]

Ah, looks like I changed it in every single website protx template, and the occupgrade file, but missed the global file - OCCPROTXScriptTemplate.pl

though strangley it's been working fine since I changed it weeks ago, and pointing to the correct urls in the address bar, while apparently being configured half old / half new...

I hope that's it, I'll test it just as soon as my site finally finishes refreshing from another problem...