Internal Server Errors (500)

[fsng-saiello]

We've been seeing a lot of Internal Server (500) errors over the weekend and this morning.

Our application is written in C# and uses the Authorize.net API.  We have been making successful calls to all of the methods for almost a year now.  The 500 errors are happening when we make calls for everything from:

Customer Payment Profiles:

var controller = new getCustomerPaymentProfileController(request);

to

One-time payments:

 var controller = new createTransactionController(request);

The weird thing is some of the payments are going through, some are returning with the 500 (and one 504) error.  And we've even seen a few responses about the system being in maintenance.

Authorize.net chat support says that everything looks good on their side and it must be an end user application issue.  But a 500/504 error is typically a server side issue.  How can I get support to look further into this???

[RichardH]

Hello @fsng-saiello

Based on your code, it appears you're using our .Net SDK.  Do you know which version you are using?

Richard

[fsng-saiello]

Hi Richard,

AuthorizeNet.1.8.10\lib\AuthorizeNet.dll

Runtime Version - v2.0.50727

Does that give you what you're looking for?

-Steve

[jayagnew1]

We are eperiencing the same issue. We use version 1.9.1.

We have seen with customer profiles, payments, etc. Started 3/18.

Currently the transactions reporting api also returns the Internal 500 error.

[RichardH]

@jayagnew1 @fsng-saiello

If you have not done so already, please contact customer support by phone an open a ticket, indicate you're getting errors starting on 3/18, you reported this to developer community and ask for escalation.  When you get a response from a support specialist, please provide the IP address of your server and a traceroute to Authorize.Net.  If possible, provide a wireshark or fiddler log of the connection will help as well.

Richard

[leo2017]

hi jay, any update on this? a ton of people are having the same issue.

[RichardH]

This should now be resolved.  If you continue to see errors, please contact customer support by phone at 877-447-3938.

Richard

[fsng-saiello]

Just got two more 500 errors....contacting support...

[jayagnew1]

no, still getting the errors. just called support myself, but this has been going on for 48 hours. 

[greenwind82]

I have the same problem starting last Friday up until now. We process close to 700 transactions a day and seem like roughly 20-30% of them failed on a daily basic with Internal Server Error. E-ticket is already created but no response so far.