Enterprise Portal on WSS 3.0 – Ax32.exe.config

When setting up  Enterprise Portal on WSS 3.0 , the deployment wizard gives “ClrObject not initialized”  error. How to resolve this to deploy EP successfully on WSS 3.0

Enterprise Portal 4.0 SP1 is supported on both WSS 2.0 and WSS 3.0. WSS 3.0 assemblies are different than WSS2.0. So the EP deployment wizard uses a config file to redirect to the right WSS assemblies in case of WSS 3.0. This file is named AX32.exe.config and should be kept at Program Files\Microsoft Dynamics\4.0\Client\Bin folder ( Where the AX32.exe is kept).

When you install AX Client on a WSS 3.0 machine for setting up EP, the setup automatically puts this folder. So you don’t need to do anything manually and the deployment wizard will just work fine.

But if you have already installed AX Client on a machine where there is no WSS 3.0 and later installed WSS 3.0 on that machine, then this file may be missing. In this case you can copy this file from the CD \Client\Program Files\Microsoft Dynamics\4.0\Client\Bin to the Program Files\Microsoft Dynamics\4.0\Client\Bin folder on the machine Or create this file manually and copy the below xml to it. After this close and reopen the AxClient  and start using the EP Deployment wizard.

?xml version=”1.0″ encoding=”utf-8″ ?>
    <assemblyBinding xmlns=”urn:schemas-microsoft-com:asm.v1″>
        <assemblyIdentity name=”Microsoft.SharePoint” publicKeyToken=”71e9bce111e9429c” culture=”neutral” />
        <bindingRedirect oldVersion=”″ newVersion=”″ />

Comments (11)

  1. Frank says:


    I have the mentioned file but I still get the CLR error when opening manage deployments. I have also added the two xml entities in the web.config file.

    Any Ideas?

  2. samunai says:

    mb you forgot "<" in the begin of this file

  3. perbiker says:

    Thanks for this very usefull ‘tip’ it did help me.

    In your sample config code you are missing the beginning ‘<‘ so actually the config chould look like this

    <?xml version="1.0" encoding="utf-8" ?>



       <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">


           <assemblyIdentity name="Microsoft.SharePoint" publicKeyToken="71e9bce111e9429c" culture="neutral" />

           <bindingRedirect oldVersion="" newVersion="" />





  4. Scott says:

    I have followed the June 2007 Instructions exactly. I did have DAX installed before I installed IIS and WSS 3. I copied the Ax32.exe.config file to the directory specified earlier.  I am still getting the error with CLR Object.  Has anyone found any other solutions? Is there a sequence that I am missing?



  5. Chandra says:

    I tried to deploy Enterprise Portal after putting this file but gets following error

    "Enterprise Portal cannot be deployed because Windows SharePoint Services is not installed on this computer."

    Please help, thank you.

  6. dartigue says:

    If you have Enterprise Portal cannot be deployed because Windows SharePoint Services is not installed on this computer." message still

    then you can uninstall AX client and AX NET connector and reinstall them

    that will fix the issue


    Gilles dartiguenave

  7. rakesh.darge says:


    How to deploy Enterprise portal in DAX 4.0 using MOSS 2007 on Windows 2003 R2 64-Bit Edition.


  8. sundeep says:

    Feature ‘cb7a647c-b9ab-4cc3-8249-c8f749d07012’ is not installed in this farm, and can not be added to this scope.

  9. Chandra Shekhar Mantha says:

    Even we faced the same problem of CLR Error

    Uninstalling the AX Client and Business Connector,Reinstalling worked.

    The file "Ax32.exe.config" is created  when you run AXSetup and also  have a prior installation of WSS or MOSS,

    you can also copy and paste the file from the following location open the AX setup DVD navigate to the following folder

    MsiClientProgram FilesMicrosoft Dynamics4.0ClientBin

  10. ferhan says:

    Is this required in ax2009, i am not able to locate file Ax32.exe.config

  11. Thanks for your great article!!!!!

Skip to main content