Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
This page is intended to provide a consolidated view of relevant documentation, videos, solutions to known issues, links to related resources, as well as community sites for implementing Enterprise Portal and Role Centers for Microsoft Dynamics AX 2009.
There are several known issues that have been resolved with Service Pack 1 and Hotfix Rollups (RUs). It is highly recommended that you apply Service Pack 1 for Microsoft Dynamics AX and the latest RU for Microsoft Dynamics AX 2009.
The latest Hotfix Rollup for Microsoft Dynamics AX is available on Partner/Customer Source under Support > Knowledge Base.
Hint: Enter “hotfix rollup available for AX 2009” into the ‘Search for’ field of the Knowledge Base search page.
The setup fails to deploy the Microsoft Dynamics AX site template if not licensed for EN-US. In the DynamicsSetup.txt file, you find the following error: Creating new Enterprise Portal Site with following the parameters:\n URL: http://server/sites/DynamicsAX\n Title: Enterprise Portal Site\n LCID: 1033\n OwnerLogin: domain\user Administration Web Service URL: http://server:44901/_layouts/ep/WSSAdmin.asmx Error: The site /sites/DynamicsAX could not be created. The following exception occured: File or arguments not valid for site template 'AXSITEDEF#0'.. An error occured while Setup was creating a new site. Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown. File or arguments not valid for site template 'AXSITEDEF#0' Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.
This issue is solved by applying the hotfix available in KB 960048. Note: If the Enterprise Portal installation still fails with the same error after applying KB 960048, recompile the SysEpDeployment class on a computer where the Microsoft Dynamics AX Client and the .NET Business Connector are both installed.
The setup fails if the .NET Business Connector is not installed on the Microsoft Dynamics AX client computer in which the initialization checklist is run. If the .NET Business Connector is not installed on the Microsoft Dynamics AX client when the initialization checklist is run, the SysDevelopmentProxy class does not get compiled. If SysDevelopmentProxy class is not compiled, then setup fails to install Enterprise Portal. In the DynamicsSetup.txt file, you find the following error: In SysEPDeployment::clrGenerateProxies... Error executing code: SysDevelopmentProxy (object) has no valid runable code in method 'generate'.
This issue is solved by applying the hotfix available in KB 971185. Additionally, there is the following workaround:
The setup fails when the installer uses the NETBIOS domain name instead of the fully qualified domain nameIn the DynamicsSetup.txt file, you find the following error:Entering method UpdateBusinessConnectorProxyAccountAn error has occured while Setup was establishing a connection through Business Connector. Error: Dynamics Adapter CallStaticClassMethod failed. Leaving method UpdateBusinessConnectorProxyAccount The Microsoft Dynamics AX installer reads the .NET Business Connector Proxy account from the System Service Accounts form and truncates the fully qualified domain name (FQDN), to the NETBIOS name. If NETBIOS is not configured on the domain the then the Business Connector Proxy account will not be authenticated and the installer will fail.
Blank out the Business Connector Proxy account in the System Service Accounts form. Run the installer again and you will be allowed to enter in the fully qualified domain name (FQDN) Note: A similar issue can occur if the Business Connector account stored in the Microsoft Dynamics AX database is using the NETBIOS name and the application pool is using the fully qualified name or vise versa. Make both accounts match using format stored in the Microsoft Dynamics AX database.
The setup fails and the IIS worker process crashes if AMO is not installed. In the DynamicsSetup.txt file, you find the following error:br> An Existing Connection was forcibly closed by remote host
The IIS/EP server requires AMO objects to be installed. Install the AMO objects and run setup again. Refer to the Install prerequisites for Enterprise Portal and Role Centers page on TechNet for SQL specific version downloads of the SQL Server Analysis Management Objects (AMO)
Opening Manage Deployments form generates error when using the 64bit version of WSS If you have Windows SharePoint Services(WSS) and the .NET Business Connector installed as 64bit versions, you cannot use the 32bit Microsoft Dynamics AX Client to deploy or update Enterprise Portal sites. When you try to open the Manage Deployments form you receive the following error message:
Manage Deployment cannot be run because Enterprise Portal is not deployed on this computer.
Microsoft Dynamics AX 2009 Service Pack 1 has a new command line utility, AxUpdatePortal.exe, that gets installed in the C:\Program Files\Microsoft Dynamics AX\50\Setup folder that serves this purpose. More information on this utility is available at http://msdn.microsoft.com/en-us/library/dd261467.aspx You can execute the utility with the following command line parameters to update all local Enterprise Portal sites: AxUpdatePortal.exe -updateWebSites -iisreset Note: On Windows Server 2008 make sure you run AxUpdatePortal.exe from an elevated command prompt. To open an elevated command prompt, click Start, right-click Command Prompt, and then click Run as administrator. More information available on these blogs:
MSDN (public) Dynamics AX Partner Forum (login required)
Please be aware that there is a hotfix KB974767, which will check if you are running AXUpdatePortal in admin mode.
401 Error on a web site that has Host Headers configured When .NET Framework 3.5 Service Pack 1 is installed and the IIS web site has a Host Header configured, the following error occurs: The Web site http://server/sites/Dynamics AX was not created correctly. The remote server returned an error: (401) Unauthorized. System.Net.WebException at System.Net.HttpWebRequest.GetResponse() at Microsoft.Dynamics.Framework.Portal.Deployment.EPFeatureReceiver.CreateAxSitesAndPages(SPWeb site) at Microsoft.Dynamics.Framework.Portal.Deployment.EPFeatureReceiver.ProvisionAxSite(SPWeb site)
The release of .NET Framework 3.5 Service Pack 1 introduced changes to NTLM authentication for HTTPWebRequest. More information on this change is available at http://msdn.microsoft.com/en-us/library/cc982052.aspx The changes in .NET Framework 3.5 Service Pack 1 include a loopback check security feature that is designed to help prevent reflection attacks on your computer. Therefore, authentication fails if the FQDN or the custom host header that you use does not match the local computer name. The changes in .NET Framework 3.5 Service Pack 1makes it necessary to configure the BackConnectionHostNames registry to match the Host Header name on the IIS web site. Adding a registry value tells Windows that the Host Name used in the request is a valid alternate name for the local computer. Refer to one of the Related Articles for detailed steps for editing the BackConnectionHostNames registry key. After making the change in the Registry, reboot the server and repeat Enterprise Portal install. Related Information:
Microsoft Dynamics AX 2009 was only supported with WSS 3.0 SP2, we now support SharePoint 2010 by Appling KB 2278963
See Compatibility Result for Microsoft SharePoint 2010 - August 2010
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
If you are experiencing issues downloading the install file or documentation on CustomerSource/PartnerSource, please contact ITMBSSUP@microsoft.com
Great comments, Jim.
A couple thoughts to some of your comments.
1. The filtered hotfixes specific to this topic will be found under the Common Problems & Solutions section. The Critical Hotfixes for this specific topic doesn't really apply as there isn't any new critical fixes. However, at this stage of v2009, it's important to ensure your on the lastes SP due to so many fixes in this area.
2. Good feedback. We'll also try to include just the most recent or highly impacted ones.
3/4/5. This Resource Page has its own comment section that we are in now for others to comment on...keeping the topic very narrow. Above under the section of Related Resources you will find some additonal blog sites that you are probably more aware of. The Microsoft Dynamics AX Enterprise Portal Blog is actually owned by Microsoft R&D team who are passionate about responding specific to this topic of EP and Role Centers. The other two are Microsoft Support blog sites that have a ton of traffic around all AX topics.
Love the feedback. Thank you.
Check out the great videos and provide feedback if they were helpful.
Business Applications communities