Jump to content
DamanC

Sage pay Server Error 5006

Recommended Posts

Hi Guys,

 

I have spent the last few days trying to solve a problem I am having with Sage Pay Server 1.1 on my 2.2RC2 Store.

 

I have been given a test account from sage and in order to get our live account I have to process a dummy transaction through the test server and then refund it. Easy you would think!

 

Its all setup, works nicely though the iframe however when the proceed button is clicked (or cancel) i get the dreaded 5006 error;

 

 

HTTP Status Code: 500

HTTP Status Message: The request was unsuccessful due to an unexpected condition encountered by the server.

Error Code : 5006

Error Description : Unable to redirect to Vendor's web site. The Vendor failed to provide a RedirectionURL.

 

 

I have read thread after thread on here and on the sage forum to no avail and just cannot make head or tail of it. Im fairly sure its something to do with a redirection URL IE - The checkout_success page but im at a loss as to where its defined, or why it would need to be edited?

 

So anyone able to help?

Share this post


Link to post
Share on other sites

Just to add, Sage pay Form in simulator mode works perfectly!

 

Its just sage pay Server in either simulator or Test is not having any of it! Im not the only one having problems, it seems many are having the same problem but with an unresolved outcome :(

Share this post


Link to post
Share on other sites

Just browsing though old transaction details - before I had setup the IP addresses Sage pay end, the transaction would fail even before stuffing in card details but it did log the request;

 

Towards the end of the request I note

 

notificationurl=https://www.mydomain.co.uk/checkout_process.php?check=SERVER&osCsid=07859e3396eba48a966ab5164f53296a

 

Does that look right?

Share this post


Link to post
Share on other sites

Another day in, have spend a good 3 hours on the phone to sagepay tech support who basically know naff all. OSC is the last line of support.

 

I have installed the module to the test site which resides on the same domain, same issue.

Share this post


Link to post
Share on other sites

I have been testing out Sagepay Server on an existing site and ran into the redirect issue. My problem turned out to be that the site was set to "Force Cookie Use" to true. Disabling Force Cookie use stopped the site redirecting the simulator to the login page.

 

As I wanted to keep "Force Cookie Use" enabled I added an IP check in application top that lets Sagepay IP's through.

Share this post


Link to post
Share on other sites

Have this same problem with a heavily modified version of 2.2. and have just now completed a new clean install of OSC 2.3.1 and am still receiving the 5006 error. Will I ever get this sorted?

Share this post


Link to post
Share on other sites

I'm pretty sure that the problem is that & changes to & and thus looks like a different url.

 

Try using oscommerce's own search engine friendly urls. This has worked for me with a similar problem, and if it may work for you with this.

Share this post


Link to post
Share on other sites

I'm pretty sure that the problem is that & changes to & and thus looks like a different url.

 

Try using oscommerce's own search engine friendly urls. This has worked for me with a similar problem, and if it may work for you with this.

 

Did you have same problem with Sagepay?

 

I have just tried using OSC built-in Search Engine Friendly URL's but this didn't work either. Now getting a "Your ID address has been logged, please go away message".

 

In my current version of 2.2 I have SEO Url's turned OFF, and the new 2.3.1 doesn't have this installed as normal. I did see other post which seemed to point to what you are saying, but I don't know if this was sucessful answer for them, nor unfortunately was there very clear instructions.

 

HAve been on the phone to Sagepay all morning, but no success yet. Have quite given up yet, but very close to it.

Share this post


Link to post
Share on other sites

For anyone struggling with this, I had to upgrade to V1.2 Sage Pay Server and since I have version 2.3.1 not 2.2 I had to compare the files and ensure no issues with 2.3.1 before doing so.

 

It now works fine.

Share this post


Link to post
Share on other sites

I posted that I fixed this on 20th January, but I am now having the exact same problem once again... Same 5006 error even though I am using V1.2 I am running oscommerce 2.3.1 can anyone help, I can't put my site live without fixing this.

 

Is there anything I can do to debug this and see what is happening????

 

Please help. :'( :'( :'( :'( :'(

Share this post


Link to post
Share on other sites

Hi Denise..

 

Can you see if the following changes exist in your module version:

 

https://github.com/osCommerce/oscommerce2/commit/32b7a6cf0ec8d32770b158e3ae24a866043f445a#diff-e05dbbbe0d8176b3f875e044c98fb45a

 

The module file to check against is located at:

 

catalog/includes/modules/payment/sage_pay_server.php


:heart:, osCommerce

Share this post


Link to post
Share on other sites

Has anyone managed to find a solution to this problem?

 

I have osC 2.3.3.4 which runs the older version of the SagePay server add-on (v1.2 )just fine, I have today tried to upgrade to the current version of this add-on (v2.1) mainly due to the fact that this uses the later Protocol v3.00 of the SagePay API, SagePay has announced that they will be dropping support for older Protocol versions later this year, so this means that anyone using SagePay needs to upgrade to the later add-on.

 

However I have the same problem as mentioned by earlier posters 'Error Code 5006' - Unable to redirect to Vendors website. The vendor failed to provide a redirection URL' I don't know if it makes any difference but I am using the 'low' method, i.e. I have my payment pages in an iframe.

 

Any help would be a gratefully received!

 

Thanks - Paul

post-4300-0-18336700-1424275685_thumb.jpg

Edited by Paul_w

Share this post


Link to post
Share on other sites

Just to provide a little more information to my earlier post, the problem occurs after having entered the card details, then filling out the 3D secure screen, it is after submitting the 3D data that the problem happens.

 

The page that I am left stuck on with the error message shown above is 

https://www.xxxxxxxxxxxx.co.uk/ext/modules/payment/sage_pay/checkout.php?osCsid=b002d7a9b80ded64c4785c0c61922029

Share this post


Link to post
Share on other sites

OK, a suggestion here, make sure you do not have .htaccess password protection running when testing the functionality of SagePay server as this will cause the problem described above.

 

All is fine now that I have removed .htacess password protection from my site :)

Share this post


Link to post
Share on other sites

I have been trying to solve this 5006 error for the past few days with a developer. The error happened in the final stage after the 3D secure password. When my woocommerce site was http it seems fine, only when I made it https with a valid https certificate, I am getting this error 5006.

 

Sagepay done a VPSTxld on a few failed transactions and their response is as below.

 

" I have investigated the all the log and each time the transaction are timing out due to the fact that we cannot connect to the following URL

(http://www.mywebsite.com/?wc-api=woocommerce_sagepayserver)

I would advise on investigating the URL in question to see if it is active and responsive."

 

When I click on the above link I get this:

 

Status=INVALID StatusDetail=SagePay Server, No VendorTxCode posted. RedirectURL=https://www.mywebsite.com/wp-content/plugins/sagepay-server-gateway-for-woocommerce/includes/pages/redirect.php?page

 

All my plugin were fine and working, only when switch over to https. Can anyone help me and pinpoint the actual place where I have to put this url in? I mean should it be automatic? I never created this url. 

 

I would really appreciate if someone can help and explain how I can do this in simple english and not coding. thanks

Edited by thaithai21

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×