Troubleshooting Enterprise Portal

Troubleshooting Enterprise Portal

Dynamics AX 4.0

This topic describes how to troubleshoot problems with Enterprise Portal (EP).

Symptom

Issue and Resolution

You receive an error message that contains a phrase such as "assembly not found," "could not be created," or "threw an exception."

You might not have ASP.NET 2.0 installed or registered:

  1. At the command prompt on the server that runs IIS, run the following command:

    %SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i

  2. Verify that ASP.NET v2.0.50727 is listed in IIS Manager on the ASP.NET tab:

    1. Click Start, click Run, type inetmgr, and then press ENTER.

    2. Right-click the Default Web site, and then click Properties.

    3. On the ASP.NET tab, in the ASP.Net version list, ensure that v2.0.50727 is selected, and then click OK.

  3. Redeploy Enterprise Portal, and then re-create your Web site.

You receive an error message that contains a phrase such as "access denied" or "do not have permission."

Permissions might not be set correctly for the Business Connector proxy user or a user group.

For more information, see Set up the Business Connector proxy user for Enterprise Portal and Managing Enterprise Portal users.

Users can access EP Web pages, but they do not see content.

You might not have user groups, user access, or user relations configured correctly.

For information about enabling users to view content on Enterprise Portal, see Granting users access to Enterprise Portal.

Error message: "Cannot add the specified assembly to the global assembly cache" or "w3wp.exe unhandled exception (System.UnauthorizedAccessException)"

The Business Connector proxy account might not have the appropriate permissions on the server to allow access. The Business Connector proxy must:

  • Be a user in Active Directory.

  • Be a member of the Power Users, IIS_WPG, STS_WPG, and the Performance Monitor Windows groups on the server that runs IIS and hosts Enterprise Portal.

For more information about creating a Business Connector proxy account, see Set up the Business Connector proxy user for Enterprise Portal.

You cannot locate or install Enterprise Portal templates

You must use an Enterprise Portal template when you create your top-level Web site in Windows SharePoint Services. If you do not see the Enterprise Portal public or private templates in the list, follow this procedure:

  1. Use Windows Explorer to verify that the templates exist on the server. By default, the templates are stored in the following folder: C:\Inetpub\wwwroot\wpcatalog. If this folder does not exist, Enterprise Portal was not installed correctly. Uninstall and reinstall Enterprise Portal.

  2. If the templates are on the server, redeploy the Web site. From a Microsoft Dynamics AX client on your EP server, click Administration > Setup > Internet > Enterprise Portal > Manage deployments.

  3. Clear the Enabled check box for the virtual server. When prompted, click Yes to remove the deployment.

  4. Select the Enabled check box for the virtual server. A message box states that the Web parts were deployed successfully.

  5. In Windows SharePoint Administration, click the Create a top-level Website link and verify that Enterprise Portal templates are now in the templates list.

Error message: "The Web site http://server/sites/site_name was not created correctly. Exception: No .NET Business Connector session could be found."

The Business Connector might not be configured correctly. To verify the configuration, follow this procedure:

  1. On the server that runs IIS and hosts your Enterprise Portal site, click Start > Administrative Tools > Microsoft Dynamics AX Configuration Utility.

  2. In the Configuration target list, click Business Connector (non-interactive use only).

  3. On the Connection tab, verify the server name and the TCP/IP port. If the port is blank, it is assumed to be running on port 2712. To verify the actual port on the AOS server, view Dynamics Information events in the Application Event log after the AOS has started.

  4. If necessary, update the configuration or create a new configuration (click Manage > Create configuration).

    For more information, see Manage a Business Connector non-interactive configuration.

Error message: "http://server/sites/site_name was not created correctly. Exception: Thread was being aborted."

This error occurs because of a connection time-out after you select the Microsoft Dynamics AX template while creating a new top-level Web site in Windows SharePoint Administration. To resolve this problem, follow these procedures:

  • Change the Connection timeout and Http Keep-Alive properties on the server that runs IIS.

  • Change connection time-out properties in the web.config file.

Change the Connection timeout and HTTP Keep-Alive properties on the server that runs IIS

  1. Open the Internet Information Services Manager (Start > Run, type inetmgr, and then press ENTER).

  2. Expand the local computer, expand the Web sites directory, right-click the Web site that hosts your Enterprise Portal site (typically the Default Web site), and then click Properties.

  3. On the Web Site tab, specify a new value in the Connection timeout field. The default value is 120 seconds.

    If for example, the server requires up to 4 minutes to create a new site using EP templates, specify a value of 240 seconds.

  4. Select Enable HTTP Keep-Alives (if it is not selected), and then click OK.

  5. Restart IIS (at a command prompt, enter iisreset, and then press ENTER).

Change connection time-out properties in the web.config file

  1. In a basic text editor such as Notepad, open the web.config file (%SYSTEMDRIVE%\Inetpub\wwwroot by default).

  2. Press CTRL + F to open the Find dialog box.

  3. Find the following tag:

    <httpRuntime maxRequestLength="51200" />

  4. Replace it with this tag:

    <httpRuntime executionTimeout="6000" maxRequestLength="51200" />

  5. Find the following tag (you might need to search from the beginning of the file):

    </sectionGroup>

  6. Add the following tags on new lines after the </sectionGroup> tag:

    <sectionGroup name="DynamicsAX">

    <section name="Deployment" type="System.Configuration.SingleTagSectionHandler, System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />

    </sectionGroup>

  7. Find the following tag:

    </SharePoint>

  8. Add the following tags on new lines after the </SharePoint> tag:

    <DynamicsAX>

    <Deployment SiteCreationTimeOut="1200" />

    </DynamicsAX>

  9. Save your changes and close the web.config file.

  10. At the command prompt, type IISReset, and then press ENTER.

  11. Try to create the top-level Web site in SharePoint Portal Administration.

After Enterprise Portal is installed, the Application Integration Framework doesn't work

For Application Integration Framework (AIF) to run on the same computer as Windows SharePoint Services (WSS) and Enterprise Portal, the virtual directory that AIF is using must be excluded from the SharePoint managed path.

  1. Open the SharePoint Central Administration page or, from the browser on a remote computer, type the URL (for example, http://servername:port) for the pages on the administration port.

    To open the SharePoint Central Administration page, click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Central Administration.

  2. Click Configure virtual server settings, and then click the name of the site that you are managing.

  3. Under Virtual Server Management, click Define managed paths.

  4. Under Add a New Path, enter the AIF virtual directory path, select Excluded path, and then click OK.

Error message: "No .NET Business Connector session found"

The .NET Business Connector is not configured correctly for the IIS and SharePoint Windows groups.

For the procedure to add the Business Connector to the appropriate groups, see Set up the Business Connector proxy user for Enterprise Portal.

Error message: "An X++ exception has occurred"

Microsoft Dynamics AX allows one Enterprise Portal site per company. Verify that the company you are logged on to does not already have a registered EP site (Administration > Setup > Internet > Enterprise Portal > Web sites).

Users have been assigned a user relation for Enterprise Portal, but they still cannot access the site

This problem occurs if the following conditions are true:

•Microsoft Dynamics AX 4.0 compares the first part of the fully qualified domain name (FQDN) to the account name in the Microsoft Windows SharePoint Services database.

•The first part of the FQDN does not match the account name.

A supported hotfix is available from Microsoft to fix this problem. The hotfix will be included in Microsoft Dynamics AX Service Pack 1.

To obtain the hotfix quickly, contact Microsoft Business Solutions Technical Support. To create a new support request on the Microsoft Business Solutions Support site, go to:

https://mbs.microsoft.com/support/newstart.aspx

You can also contact Microsoft Business Solutions Technical Support by telephone at (888) 477-7877.

NoteNote

In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Business Solutions Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.


Show:
© 2016 Microsoft