First of all, 3005 is a generic error. With googling I've found several outbreaks of this error with the same code and different causes and fixes. Sub-optimal. Whenever you disguise the actual error details for security, this should always be done with very detailed internal logging so that your developers are never scratching there head trying to figure out what happened. You should have any problems fixed within minutes, long before they affect more than a handful of people. I get the distinct impression that paypal is flying by the seat of their pants based on how you are reacting to this problem and the out break 15 months ago. I feel like volunteering to help you guys out with this which is totally ridiculous given the scope of your company. Why are you still using CGI? (This is why there is a consistant delay for EVERY web access.) Why don't you have logging and debugging built in to your system? I am now forced to add support for Google Checkout to my app.
... View more