Overview For our project, we were developing bunch of AIF Web Services to be consumed by external applications such as Commerce Server and Custom ASP.Net web apps.
Issue We initially tried to generate some of the standard out of the box web services for creating customer, vendor etc. The generation was successful but when consuming these web services through a Test harness .Net Windows App, We encountered the following two errors in Event Viewer
Event Log 1
Microsoft Dynamics AX Business Connector Session 9.
An X++ exception has occurred.
Request Failed. See the Exception Log for details.
Event Log 2:
The description for Event ID 0 from source Dynamics Application Integration Server cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
An error occurred while Web service request http://wdmaxaosdev01vm.retail.ad.cmltd.net.au/MicrosoftDynamicsAXAif50/liqtrlrservice.svc and action http://tempuri.org/LIQTRLRService/create were being processed. Error details:
.
Request Failed. See the Exception Log for details.
**Exception:**
Message: Stack trace: at Microsoft.Dynamics.BusinessConnectorNet.Axapta.CallStaticClassMethod(String className, String methodName, Object[] paramList)
Request Failed. See the Exception Log for details.
at Microsoft.Dynamics.IntegrationFramework.Service.WcfAxAdapter.SubmitMessageToAx()
The specified resource type cannot be found in the image file
Solution
There was no track of any X++ exception messages in the Basic > Periodic > Application Integration Framework > Exceptions Form.
After some time of troubleshooting, got to know that the .Net Business Connector Configuration was missing on the AOS Server where AIF was installed. Creating a .Net Business Connector Configuration by going to Control Panel > Administration Tools > Client Configuration Utility resolved the issue.
You can find some related information about AIF in my previous post
http://daxdilip.blogspot.com/2010/05/aif-links.html