Troubleshooting has always been one of the most critical and difficult parts of the webservice. As the result of the webservice is pre-defined there is no easy way to respond with an error message in case of any problem. Most problems relate to security issues or wrong/missing settings. So first thing to check should be if the account which is executing the request has the appropiate permission to do so. In most cases this is the account which has been configured for the webservice or better to say for the application pool within this website is running.

Read the installation notices which cover most of the setting which need to be set.

Since Version 7.1 the web service has a new logging provider implemented that can be used to get more information. You can configure this logging provider to your own needs by specifying the detail level, the information that shall be logged and also the target it shall log to (xml file, database, event, etc.). On default only Informational logging is written to a text log file located in the "Logs" folder of your web service. You should find a file per day so you can also easily archive or delete older logs. For your convinience additional default logging options have been added to the nlog.config file and have been commented out. To enable Debug or even Tracing level logging just uncomment the appropriate lines in the nlog.config file as shown below.

Be aware that logging will use some resources on your server. So use the logging that's appropriate to your individual needs. See Add logging to your applications - NLog for beginnersand NLog Documentation - How to configure NLog through the configuration file for more information on how to customize this logging.

If you are using a version prior to 7.1 I highly recommend upgrading to make use of the new logging provider and also from all the bugfixes and improvements implemented in new versions!

Last edited Aug 12, 2010 at 9:51 AM by MaikKoster, version 10


No comments yet.