Troubleshooting sources and destinations
Sources can be one of the following: HTTP, FTP(s), SFTP, or Service Bus Queue and Topic. If the source endpoint is HTTP, it is common to see HTTP error codes on the client side sending the message, as shown in the following table:
|
Error scenario |
HTTP error code |
Description |
|---|---|---|
|
Message to a nonexistent endpoint or wrong URL |
400, 500 |
Bad Request, Internal Server Error, or Namespace cannot be resolved |
|
Endpoint with malformed message headers |
401 |
Authentication failed or Unauthorized request |
|
Endpoint with malformed message body |
500 |
Internal Server Error; see tracking or trace entries for more information |
|
Destination endpoint down |
500 |
Internal Server Error |
|
Destination with incorrect credentials |
500 |
Internal Server Error |
|
Bridge destination is configured for HTTP relay but receiver is listening on HTTPS |
500 |
Internal Server Error |
In the case of FTP as source, if there are errors during the processing or at the destination, the message will...
