Microsoft Dynamics 365 Blog

We came across an issue recently where weren’t able to detect SharePoint 2010 installed on the system in order to deploy Microsoft Dynamics AX 2009 – Role Centers and Enterprise Portal (EP):

– SharePoint Server 2010 was successfully installed on a system running Windows Server 2008 R2 Standard edition

– We can created SharePoint web sites and site collections

– The AX 2009 RTM setup files were copied to a local folder on the server, and patched with updated “setup assemblies” from hotfix 2278963 correctly

– We are logged in as a domain user that is a local administrator (and has appropriate rights in AX and SharePoint)

– However when we run setup.exe from the local folder, and select option to deploy Role Centers and Enterprise Portal, we get the following windows displayed, which indicates that it could NOT find any SharePoint installations on the server (Microsoft Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server 2007 or Microsoft SharePoint Foundation/Server 2010) as a pre-requirement. In this case AX setup gives you an option to install Microsoft Windows SharePoint Services 3.0 SP1:



The updated axsetup.exe that ships in hotfix 2278963 will check the registry to identify if Sharepoint 3.0 or 2010 is installed or not. We used Process Monitor (procmon) tool to identify if the registry keys were being read and if so was it encountering any issues e.g. like an “access denied” or anything else. In Process Monitor we added the filter to monitor process name setup.exe and axsetup.exe and filtered to capture on registry events.

The log file collected showed that it was actually failing to read the sharepoint 2010 version key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14.0\Version instead!

 we Identified on another running system on which we had successfully deployed EP and there was a Version reg_sz key and its value was set to

Creating the Version key and setting the value resolved the issues and allowed deployment of Role Centers and Enterprise Portal without getting prompt to install th epre-requisites. Later it was reported that the only difference in the setup found between the failing system and other working systems was that SharePoint 2010 was installed using automation by using PowerShell and a SharePoint config file and not by manually running setup.


Other Refereneces:

Resolving some issues you may experience when creating an AX 2009 Role Center and Enterprise Portal Site using SharePoint Server/Foundation 2010 after installing Microsoft Dynamics AX 2009 SP1 hotfix 2278963

Error “Cannot access a disposed object” when deploying AX 2009 Enterprise Portal on a SharePoint 2010 server


–author: Anup Shah
–editor: Anup Shah
–date: 07/Dec/2010



We're always looking for feedback and would like to hear from you. Please head to the Dynamics 365 Community to start a discussion, ask questions, and tell us what you think!