Tag Archives: IIS

Business Connector isssues

In a webservice I am using the Microsoft.DynamicsBusinessConnectorNet.dll. Today the webservice stopped working giving the error:

Could not load file or assembly ‘Microsoft.Dynamics.BusinessConnectorNet’

This was quite strange since the service was working yesterday. The reason to the error turned out to be a new deployment of a new webapplication to the IIS. This particular webapplication required the IIS to run in 64 bit mode and therefore this was changed. The Microsoft.DynamicsBusinessConnectorNet.dll that I was using was the 32bit version – which ofcourse was the cause of the error.

The solultion was to enable the application pool to allow 32 bit application. This is done by:

  • Right clicking the application pool and selecting “advanced setting”
  • Set the “enable 32-bit applicataions” to true

Here’s a screendump:

Enable 32 bit applicaations in IIS

Enable 32 bit applicaations in IIS


Update 2012-11-27: When enabling 32 bit applications on IIS6 I recently encountered that one need to run aspnet_regiis.exe in order to register the 32 bit version of the .net framework – otherwise I received a “servive not available” message

Update 2015-07-10: Recently we ran into another issue when running OWA on the same IIS. We found this solution very helpful: http://www.mosmar.com.au/chris-blog/2011/3/15/taking-care-of-bitness-or-how-to-run-a-32-bit-app-with-owa-2.html

SVC error when deploying AIF service to IIS

If you are viewing an IIS error page like this after having published Your AIF service to IIS, the svc extension is probably missing in IIS:



This is probably caused by WCF not being correctly installed or registered in IIS.
To fix this do the following:

  1. Open a command prompt
  2. run the following command %windir%\Microsoft.net\framework\v3.0\WindowsCommunicationFoundation\servicemodelreg -i

If you are running a 64 bit OS, You will have to decide whether to run the above command from the “framework64” folder og just the “framework” folder. The easy way to determine this, is to find out whether Your application pool for AIF is running in 32 bit mode. If not you can run the command for the 64 bit version  – otherwise You will have to use the 32 bit version.

To find out whether yourt application pool runs in 64 bit mode do the following:



  1. Go to the application pool section in IIS
  2. right click Your application pool – in this case the “MicrosoftDynamicsAXAif50” pool and select advanced settings
  3. Search the property “Enable 32 bit applications”. A value equal to false means we are running in 64 bit mode and vice versa.

Windows autentication problem on Dynamics AX WCF service

Over the past days I have been involved in a critical issue related to a Dynamics AX 2009 WCF service that used windows authentication on a Windows server 2008 box (IIS 7.0).

When trying to browse the service I was prompted for login credentials, but even though proper credentials were provided, I was not correctly authenticated (and neither was any of the clients that was supposed to consume the service) and a new login prompth just showed up. Looking in the eventviewer, in the security section, I was able to identify that a login attempt using my user account has been made and that it actually succeeded.
The funny thing – that wasn’t funny at all, was that how could it be that the eventviewer stated, that the login attempt was successfull when IIS still kept prompting me for credentials???
It somehow seemed that login credentials wasn’t properly passed on to the WCF service…

Analyzing the server setup further showed that a distributed environment had been configured. This pointed me in the direction of some Kerberos settings that hadn’t been properly configured.

The solution turned out to be quite simpel – the only thing I had to do was to disable “enable kernel-mode authentication” – this is what i did:

  • In the IIS manager right click the website or application where Windows Autentication has been configured
  • In the “features view” double click “autentication”. You will see a list of autentication profiles and their corresponding status.
  • Right click “windows autentication” and select “advanced settings”
  • Disable “enable Kernel-mode authentication”

    disable Kernel-mode

    disable Kernel-mode autentication

Be carefull… As the information box states, this should only be done when using a non custom identity. In my case, the problem related to a Dynamics AX WCF service. Such a service is always configured to use a domain account identity and therefore the “Kernel-mode” could be disabled.

For some reason unknown to me, the Kerberos ticket was not properly distributed to all involved servers – and due to that I was unable to logon to the WCF service. Disabling “Kernel-mode authentication” solved that problem and clients are now able to consume the service.

Update 24.01.2012

Today this woraround didn’t work – apparently I was facing a new problem and I had to have a colleague assist me. Fortunately he knows some tricks:-)

With reference to this article http://support.microsoft.com/kb/926642 (method 1) solved the problem – even though that my issue was on a server 2008 box – here’s a screendump:

For further references on troubleshooting and/or configuring kerberos, please check out this post: