Posted: January 27, 2014 at 11:12 pm
|
Using both regular Paypal and Paypal pro and getting the error in title on all transactions. Over the weekend I updated to the latest version of EE but I also moved my DNS to different name servers. So, the questions: Any insights appreciated |
|
Hi Tim, There is no known issues with the PayPal gateways, the last few point updates didn’t touch those gateways. It is likely that something may have gone awry during the DNS change, but what that is I’m not sure. Is that error message exact? Where does it come up? I cannot trace that message as originating from us OR PayPal, at least it is not in the PayPal error list codes https://developer.paypal.com/docs/classic/api/errorcodes/ |
|
Hi Dean, the exact error message is Thank You It comes up after entering payment information and submitting – or, i.e. the Thank You page Thanks, and any further help appreciated. I am not sure exactly how DNS change would affect it either. (The IT guy assured me the SSL would not be affected, but then again, he has been wrong before . . . I am not sure what else it could be) |
|
Hi Tim, Thank you, the full message helped. The only part of the plugin for that error message is in the Quickbooks gateway, not either of the PayPal gateways. Do you have Quickbooks activated? Also, have you modified any of the gateway files at all? |
|
Dean, thanks for you help with this. You investigations helped ultimately weed through a lot of potential confusion – I found out there were other updates that happened server-side prior to the weekend as well. But ultimately, here was the problem: Someone had activated the Quickbooks gateway in the backend. But since there was no connection ticket, etc. (as the error stated) it obviously did not work. Since the “Pay with credit card” icon looks the same as that which would be connected to Paypal Pro . . . all errors were ultimately from the wrong button being pushed. So really simple problem, really simple solution, but if you hadn’t pointed out that was a Quickbooks error, we would have been wasting a lot more time looking in all the wrong places. I am posting this to say thanks but I am also posting if anyone else should ever come up against something like it again. It’s like the instructions on the clothes washer – look for the simplest solution first. “Before calling for service please ensure your washer is plugged in . . .” |
|
Hi Tim, I’m happy that it turned out to be a simple problem in the end, and thank you for posting the details as that will no doubt help others in the future.
|
The support post ‘Transaction Failed 2040: Connection ticket is missing’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.