Our support engineers have assembled the top recommended solutions for you.
Microsoft Dynamics AX 2012
Data Import, Export, and Migration in Microsoft Dynamics AX 2012
CRM Connector in Microsoft Dynamics AX 2012
Financials Management in Microsoft Dynamics AX 2012
Upgrading to Microsoft Dynamics AX 2012
Microsoft Dynamics AX 2009
Application Object Server (AOS)
Enterprise Portal and Role Centers
Inventory Costing in Microsoft Dynamics AX 2009
SSRS and SSAS Integration
Provides a consolidated list of published documentation, sources of information, known issues, solutions as well as tips and tricks for troubleshooting CRM Connector for Microsoft Dynamics AX 2012.
Some of the issues described in this page will be corrected in the RU 1 release of the CRM connector for Dynamics AX 2012 due to release at the end of June 2012.
This section lists the most common issues encountered in CRM Connector for Microsoft Dynamics® AX and the solution recommended by the Microsoft Dynamics® AX Support team. Please note that there may be some different security settings depending on your domain policies. You may need to work with WCF resources for WCF related errors or problems.
The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state, when testing the Adapter settings in the CRM connector tool
This message is usually seen when the Dynamics AX 2012 CIL code and X++ code are not in sync. With no other users in the system and only one AOS instance running, complete the following steps: Full X++ compile Synchronize Full CIL generation Resolve any errors that occur during the process, before moving on to any of the next steps. After successfully completing the steps above, restart all AOS instances. If you receive CIL errors, go back and compile the class in the error, look for any potential compile forward when extending code.
Unable to connect when trying the use the Refresh Services button in the CRM Connector tool and when checking C:\ProgramData\Microsoft Dynamics\Connector for Microsoft Dynamics\Logs\Microsoft.Dynamics.Integration.Adapters.Ax2012.Configuration.log You see the error Caught Exception: This operation is not supported for a relative URI near the end of the log file
There is a conflict with Windows App Fabric SDK that is installed on the CRM connector machine. This issue is resolved in the RU 1 release of Connector, the workaround is to un-install Windows App Fabric SDK from Control Panel | Programs and features Once you un-install the Windows App Fabric SDK you may encounter an additional error from entries not being fully removed from configuration files. The following blog post addresses this issue: http://justinlee.sg/2011/04/27/how-to-fix-this-error-configuration-binding-extension-system-servicemodelbindingsnettcprelaybinding-could-not-be-found/ The Windows App Fabric SDK gets installed with CRM, but is only used if you are doing CRM online application development. Windows App Fabric SDK is also installed with Rapid Start and may need to be moved to a different server for that functionality Note: This issue will be corrected in the RU 1 release of the CRM connector for Dynamics AX 2012 due to release at the end of June 2012
A call to SSPI failed, see inner exception error message when you test the connection in the CRM connector tool. When you check C:\ProgramData\Microsoft Dynamics\Connector for Microsoft Dynamics\Logs\Microsoft.Dynamics.Integration.Adapters.Ax2012.Configuration.log you receive the error Caught Exception: Exception occurred on the metadata service on client or server. See exception details below: >A call to SSPI failed, see inner exception. near the end of the log file. When you check the system event logs on the CRM connector machine you receive the following Kerberos error: The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server axAOSServer. The target name used was host/server. This indicates that the target server failed to decrypt the ticket provided by the client…..
If you are getting an SSPI error the issue seems to be related to the Microsoft.Dynamics.Integration.Adapters.Ax2012.Configuration.exe.config. This file is located in the following location: C:\Program Files (x86)\Microsoft Dynamics\Microsoft Dynamics Adapter This file contains an Identity servicePrincipalName value="host/localhost". These entries could be changed to remove the host/localhost and leave it blank as shown here:<servicePrincipalName value="" />The original file has two places where it would to be changed to have the blank entry, below is the original file before any changes are made so you can find and remove the entries: <client> <endpoint address="net.tcp://localhost8201/DynamicsAx/Services/MetadataService" binding="netTcpBinding" bindingConfiguration="MetadataServiceEndpoint" contract="Microsoft.Dynamics.AX.Framework.Services.Metadata.Service.IAxMetadataService" name="MetadataServiceEndpoint"> <identity> <servicePrincipalName value="host/localhost" /> </identity> </endpoint><endpoint address="net.tcp://localhost:8201/DynamicsAx/Services/QueryService" binding="netTcpBinding" bindingConfiguration="QueryServiceEndpoint" contract="Microsoft.Dynamics.AX.Framework.Services.QueryService.IQueryService" name="QueryServiceEndpoint"> <identity> <servicePrincipalName value="host/localhost" /> </identity></endpoint> </client> Note: This issue will be corrected in the RU 1 release of the CRM connector for Dynamics AX 2012 due to release at the end of June 2012
If you are experiencing issues downloading the install file or documentation on CustomerSource/PartnerSource, contact ITMBSSUP@microsoft.com
Can Dynamics CRM online 2013 can be integrated with on-premise Dynamics AX through Connector?
@ka - yes it can using version 3.1 of Connector
Other Microsoft Sites
I'm a Customer
I'm a Partner
Follow Microsoft Dynamics