Share via

Resource Page for Enterprise Portal and Role Centers in Microsoft Dynamics AX 2009

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.

Top Downloads

Critical Hotfixes

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.

Related Resources

Common Problems & Solutions

Issue

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: https://server/sites/DynamicsAX\n Title: Enterprise Portal Site\n LCID: 1033\n OwnerLogin: domain\user Administration Web Service URL: https://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.

Solution

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.

Issue

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'.

Solution

This issue is solved by applying the hotfix available in KB 971185.

Additionally, there is the following workaround:

- Manually compile the SysDevelopmentProxy class:

  • Start the Microsoft Dynamics AX 2009 Client on a computer where the .NET Business Connector is also installed.

  • Open the AOT window.

  • Expand the Classes node.

  • Locate the SysDevelopmentProxy class.

  • Right-click at the class, and then choose Compile from the context menu.

  • If the manual compile does not work, then rebuild the axapd.aoi and then repeat the manual compile. br>

Issue

The setup fails when the installer uses the NETBIOS domain name instead of the fully qualified domain name

In the DynamicsSetup.txt file, you find the following error:

Entering method UpdateBusinessConnectorProxyAccount An 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.

Solution

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.

Issue

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

Solution

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)

Issue

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.

Solution

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 https://msdn.microsoft.com/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:

Please be aware that there is a hotfix KB974767, which will check if you are running AXUpdatePortal in admin mode.

Issue

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 https://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)

Solution

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 https://msdn.microsoft.com/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:

  • KB 896861 - You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or IIS 6

  • KB 956158 - You receive an error message when you use SQL Server 2008 Reporting Services: "HTTP 401.1 - Unauthorized: Logon Failed"

  • NLB Deployment of Enterprise Portal Setup: Stream

Issue

Microsoft Dynamics AX 2009 was only supported with WSS 3.0 SP2, we now support SharePoint 2010 by Appling KB 2278963

Solution

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

Troubleshooting Tips

  1. NET Business Connector session could not be found.

    Possible reasons for this issue:

    • The .NET Business Connector is not installed

    • The wrong version of the .NET Business Connector is installed

    • The .NET Business Connector non-interactive configuration is wrong

    • The application pool does not match the .NET Business Connector account stored in the Microsoft Dynamics AX database (See issue above)

    • In some environments the application pool must match the FQDN, which is stored in the Microsoft Dynamics AX database. (i.e… local.net\BCProxy vs. local\BCProxy )

    • You may need to blank out the .NET Business Connector in the AX database and enter the account in the Microsoft Dynamics AX 2009 installer.

    • The proxy classes are not compiled in the Microsoft Dynamics AX 2009 client on a machine where the .NET Business Connector is installed (see sysdevelopmentProxy issue above).

    • Missing Business Connector or EP Framework license keys.

  2. The 404 error generally means the site creation did not complete successfully.

    Possible reasons for this issue:

    • The application pool is not using the .NET Business Connector proxy account

    • The user who is creating the site does not have the proper permission in Microsoft Dynamics AX

    • The user with being given administrator privileges on the web site being created (in the create site UI) does not have permission in the proper permissions in Microsoft Dynamics AX. The Microsoft Dynamics AX user account should be logged into the server and not only logged into SharePoint Central Admin webpage.

    • The Master page for Microsoft Dynamics AX is not available in the site definition (C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\SiteTemplates\AXSITEDEF\defaultax.master).

Support Information

For technical support questions, contact your partner or direct your questions to the Support for Business hub: https://serviceshub.microsoft.com/supportforbusiness/create

CustomerSource Help and How-To Resources

To access the downloadable material within this content as previously found on CustomerSource, users will need to have the same customer account access. Click here to view more information.