Sunday, 21 February 2016

A call to SSPI failed, AX-BizTalk WCF service

Recently we developed integration between AX and an external system through BizTalk. The data flow from BizTalk to AX was using a WCF service. Everything worked fine in dev/test/uat systems. Once the code was deployed to production system and configured to talk to BizTalk we started getting the following error.

A call to SSPI failed, see inner exception. ---> System.ComponentModel.Win32Exception: The target principal name is incorrect

On investigation we found that User Principal Name (UPN) was not setup properly on the BizTalk Send port. The UPN is usually the AD user under which AX service is running (in an email format e.g. It can also be viewed from the service WSDL URI. Find the service from the inbound ports and copy the WSDL URI.

Paste the URI in internet explorer and WSDL will be shown. Scroll to the end and UPN is shown (highlighted below).

Copy this value and paste it in the "Endpoint Identity" in the Send port of BizTalk application as shown below

The error message should disappear.

Note: There may be other causes (Kerberos/Double hop issues) of this error message. In our cause this was the only issue.

This posting is provided "AS IS" with no warranties. Use code at your own risk.

Monday, 15 February 2016

Error when accessing AX7 VM

For last few days error started appearing when trying to login to local AX7 VM as shown below

It seems the account we were using was created by MS and was provisioned as Admin in the AX7 VM. For some reason MS have now disabled the account and as a result we cannot access the AX7 environment.

The solution is to provision another user as Admin in the AX7 VM environment. While signing up for AX7 preview (blog post here), you must have gone to and created a user there. The user login is in the form This user can be provisioned as an admin on the AX7 VM.

On the AX7 VM desktop find the icon shown below

Double click it and enter the user that was created on and click "Submit" button.

It takes some time and then you should get the following message

Now if you use the same user (that you provisioned above) to login to AX7, it should work.

This posting is provided "AS IS" with no warranties. Use code at your own risk.