I have written a fairly basic web service and deployed from AX2012R2.
I have then wrote a quick Visual Studio project to consume the webservice so I can test it. The service loads in fine, and I can set most of the values, but when I try and create the record I get the following message:
"The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK "
This message is generally tellin gme I need to switch on debugging (IncludeExceptionDetailInFaults) the question is how, what and were do I complete this?
On the server I have the web config file, which I have read should have the IncludeExceptionDetailInFaults set to false, change to true, but it is not present. (see below)
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.web>
<compilation debug="false" targetFramework=".NETFramework, Version=v4.0">
<assemblies>
<add assembly="System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add assembly="System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
</assemblies>
</compilation>
<!--
The <customErrors> section enables configuration of what to do if/when an unhandled
error occurs during the execution of a request. Specifically, it enables developers
to configure html error pages to be displayed in place of a error stack trace.
-->
<customErrors mode="RemoteOnly" />
<!--
The <authentication> section enables configuration of the security authentication
mode used by ASP.NET to identify an incoming user.
-->
<authentication mode="Windows"/>
<!--
The below settings (httpModules,trust) are in place to make sure AIF works
when deployed with Windows Sharepoint Server (WSS). E.g. With Enterprise Portal (EP).
WSS overrides certain Asp.NET configuration which makes standard Asp.NET applications to fail.
For more details refer to http://support.microsoft.com/?id=828810
-->
<httpModules>
<!--
<add name="WindowsAuthentication" type="System.Web.Security.WindowsAuthenticationModule" />
<add name="UrlAuthorization" type="System.Web.Security.UrlAuthorizationModule" />
<add name="FileAuthorization" type="System.Web.Security.FileAuthorizationModule" />
-->
</httpModules>
<!--
Set the trust back to Full.
WSS configures a very restrictive trust policy that does not allow most applications to run correctly.
-->
<trust level="Full" originUrl="" />
</system.web>
<!-- Configure tracing information for debugging in production version -->
<system.diagnostics>
<!-- This is relevant only for DEBUG build.
This disables assert dialog when Debug.Assert() is used in code. Since code will be running in IIS (no-ui)
we have to disable dialogs. We will redirect it to a file
Please make sure to give a full file path to where the assertion file should be located
-->
<assert assertuienabled="false" logfilename="AifDebugAsserts.webinfo" />
<!-- This is used for enabling tracing in retail and debug builds.
AIF Service processing stack outputs information messages used for debugging.
Possible values for switch are Off, Error, Warning
Change switchValue to Information to enable this.
-->
<trace autoflush="false" indentsize="4">
<listeners>
<add name="AxTraceListener" type="System.Diagnostics.EventLogTraceListener" initializeData="Dynamics AX Services (IIS)" />
</listeners>
</trace>
<switches>
<add name="ServiceTraceLevel" value="Off" />
</switches>
</system.diagnostics>
<appSettings>
</appSettings>
</configuration>
So my question is how to I debug the webservice to determine what the issue is with the create...?
Thanks for your help.