Dynamics Community Forum Thread Details

GP Web Services Tracing?

I am wanting to know if there is additional tracing available for GP Web Services. I have already turned on logging as described by Chapter 10 of the WS Install/Admin Guide. I noticed there is a switch in the DynamicsSecurity.config file named ApplicationTraceSwitch. I cannot find any documenation on this switch.

The problem I am trying to solve is a client attempting to call GP Web Services and receiving the response "The caller was not authenticated by the service". After turning on logging for both endpoints we did not receive any log entry when the other party attempted their call to the service. I want to interpret that as their call not making it to GP Web Services, but I don't know what else would be between them and the web service.

Categories:

Microsoft Dynamics GP

The Web Services Exceptions Console and Event Viewer logs, specifically the 'Dynamics' log is where I'd start first, as usually if there's nothing in either of those, it may not be an actual Web Services issue.

In regards to the tracing you mentioned, I think this may be it:

There is some tracing we can use to try and identify what is causing this to occur. To enable this tracing, we need to do the following:

1. On the Web Services server, browse to C:\Program Files\Microsoft Dynamics\GPWebServices\ServiceConfigs\ directory, make a backup of the DynamicsGP.config file.

2. Open the original DynamicsGP.config file and right after this section:

<system.diagnostics>

</switches>

</listeners>

</trace>

</listeners>

</source>

</listeners>

</source>

</listeners>

</source>

</listeners>

</source>

Add this section:

</add>

</add>

</listeners>

</source>

</add>

</add>

</listeners>

</source>

This would come right before this section:

</sources>

</sharedListeners>

</system.diagnostics>

</configuration>

3. Right after this section in the same config file:

....and right before the end of the config file:

</sharedListeners>

</system.diagnostics>

</configuration>

Add this:

<add initializeData="C:\Program Files\Microsoft Dynamics\GPWebServices\Logs\Tracing\eConnectSvc.log" type="System.Diagnostics.TextWriterTraceListener, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"

name="eConnectSvcTextTracelistener">

</add>

<add initializeData="C:\Program Files\Microsoft Dynamics\GPWebServices\Logs\Tracing\eConnectSvcLog.xml" type="System.Diagnostics.XmlWriterTraceListener, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"

name="eConnectSvcXmlTracelistener">

</add>

<add initializeData="C:\Program Files\Microsoft Dynamics\GPWebServices\Logs\Tracing\eConnect.log" type="System.Diagnostics.TextWriterTraceListener, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"

name="eConnectTextTracelistener">

</add>

<add initializeData="C:\Program Files\Microsoft Dynamics\GPWebServices\Logs\Tracing\eConnectLog.xml" type="System.Diagnostics.XmlWriterTraceListener, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"

name="eConnectXmlTracelistener">

</add>

4. You’ll need to stop and restart the ‘Microsoft Dynamics GP Service Host’ service for changes to go through, and also the user account running this service must have ‘Full Control’ of the C:\Program Files\Microsoft Dynamics\GPWebServices\ folder.

5. Reproduce the issue with the Web Services then look for the files generated under the C:\Program Files\Microsoft Dynamics\GPWebServices\Logs\Tracing\ folder.

6. After troubleshooting, you can change the config file back to the way it was, so you don't bog down your system with ongoing logs, and restart the service again for changes to take effect.

Thanks

Quick Links