Pages WebServices - Debugger

1) You can use reverse proxy e.g. Fiddler debugger to catch the communication (you need to enable this functionality in Fiddler registry). It will listen on the port instead the NAVServer and forward the communication to the NAV Server real port.

2) You can enable debugging on the NAV Server and debug the application through Visual Studio Debugger (even remotely if you use the remote debugging functionality). You can find more on the blogs about debugging NAV 2009 RTC/WebServices.

3) Most detailed info (internal info from the NAV Server, not executed C/AL code) could be collected through WCF tracing functionality. How to enable tracing on the NAV Server could be found on the blogs. Result is tracing logs with detailed info about all connections etc. Use it only if you need to know why the service is not working when other ways failed and use it on separate service, or you will kill the service.