I'm receiving an Internal Server Error when calling the Visa B2B Connect validateEligibility API from within the application I am developing. The request is well formed and tracing shows that the certificate handshake is working properly. The body of the Internal Server Error response is:
<HTML><HEAD><TITLE>Error</TITLE>
</HEAD><BODY>
An error occurred while processing your request.<p>
Reference #179.96392b17.1588869976.3aca9b48
</BODY></HTML>
Can anyone explain the meaning of the "Reference" value and how it relates to the internal server error? How can I determine why the call fails?
The same call works correctly from my host computer when using SoapUI.
hey @Schoenbaum - we're looking into this. Apology for the inconvenience, let me know if anything else comes up in the meantime.
Hey @Schoenbaum - we're looking to troubleshoot but need some more details. When you get a chance, can you send the CR ID as well as the info below:
1. Endpoint
2. Request Header
3. Request Body
4. Response Header (include the x-correlation-id)
5. Response Body
Thanks,
Ricardo
Hi Ricardo,
I'm not clear what you are referring to with "CR ID".
I have extracted the following from the .NET System.Net trace log file:
Thanks for sending! Apologies - what I meant by CR ID was correlation id - can you also share that?
There is no X-Correlation-id value.
Instead the response header has an X-Reference-Error element. This apparently is a custom header element used by Visa.
Thanks for the information. Looks like the response is coming from the Akamai layer, based off "Server:AkamaiGHost" in the response headers. Could be a connectivity issue between their system and Visa.
I can have our ops team check if the call is even reaching our origin - but would need your IP address to do that. You can email that directly to me at rinavarr@visa.com