Hi,
A user tested sending the API call GetTableForParameter to a non-existing element ID. The response was a "200 OK" with a empty response. This was expected by the user.
The purpose of this exercise was to check what details were logged to help understand the reason for the empty response (or other faulty/unexpected responses).
The SLNet.txt log only shows when the call was made (the same goes for the information events).
On C:\inetpub\logs\LogFiles\W3SVC1, there is also no additional information besides the time when the call was made, what call it was and the result:
2020-08-18 17:14:45 10.178.144.15 POST /api/v1/soap.asmx op=ConnectApp 80 ALLOWED+(single+request,+by+path) 10.48.86.253 Java/1.7.0_72 - 200 0 0 85
2020-08-18 17:14:45 10.178.144.15 POST /api/v1/soap.asmx op=GetTableForParameter 80 ALLOWED+(single+request,+by+path) 10.48.86.253 Java/1.7.0_72 - 200 0 0 268
Is there any other logging that could help troubleshoot API calls? For example, showing more details that could hep explain what went wrong with the call?
Thank you for your help.
Apart of the logging of IIS and SLNet, there is no additional logging. Extra logging would generate too much data and cause unnecessary load on setups with a high API usage.
For troubleshooting, it's possible to follow the API connection with SLNet in the SLNet Client Test tool: it will do a request to get the element which will result in a null response:
The API will return a 500 error message:
I used a recent version (10.0.10), in older versions the behavior can be different.
Thank you for the help Wim. Cheers!