Troubleshoot installation issues for a Retail online store [AX 2012]

Updated: September 10, 2014

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2

This topic includes strategies and procedures to help you troubleshoot problems installing the Microsoft Dynamics AX Retail online store.

Tip/Strategy

Details

Check the amount of RAM on the SharePoint Server

The System requirements for Microsoft Dynamics AX 2012 guide suggests a minimum of 16 GB of RAM. Depending on your infrastructure, 32 GB of RAM might be necessary. Many of the stop issues experienced with the Windows PowerShell deployment scripts resolve without additional troubleshooting if you increase the amount of RAM on the server.

Search the SharePoint ULS logs

The SharePoint ULS logs can provide more information about errors than other logging sources. Search the ULS logs for a timestamp that reflects your deployment activities. By default, the logs are stored here:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS

Configure tracing details in SharePoint Diagnostic Logging

The Windows Event log and the SharePoint ULS log store exceptions for events triggered when you deploy the Retail online store. Traces for the Retail online store display “Dynamics AX Retail”. To help you troubleshoot your deployment, you can adjust tracing and information levels.

  1. In SharePoint Central Administration, click Monitoring, and then click Configure diagnostic logging.

  2. Select Dynamics AX Retail.

  3. Use the drop-down lists underneath the Categories and select Verbose as the least critical events and traces to log.

  4. Save your changes.

For manual installation, you can re-run Windows PowerShell scripts

If you experience an error during the execution phase of one of the Windows PowerShell deployment scripts, you can rerun the script after you have resolved the error. You do not have to rerun completed scripts. If you rerun the Deploy-FarmSolutions script, the system automatically invokes the DeactivateOnly-Features.ps1 and RetractOnly-Solutions.ps1 scripts before you deploy the farm solution. These scripts clean up actions performed by the Deploy-FarmSolutions script before redeploying.

Return the SharePoint server to a clean state

Perform the following steps if, for any reason, you want to return your server to a clean state.

  1. In SharePoint Central Administration, click System Settings and then click Manage Farm features. Deactivate the following features: Retail Custom Claims Provider, Retail Logging Service, and Retail Publishing Job. If you do not see one or more of these features, go to step 2, otherwise go to step 3.

  2. On the System Settings page, click Manage farm solutions. Retract each solution and then click OK. IIS and SharePoint Central Administration will be temporarily unavailable.

  3. On the Application Management page, click Manage web applications. Delete C1 Application for Retail Store Front - Internal and Out of box Store front – Public.

  4. In SQL Manager, delete the following databases if they exist: AxRetailSP, SpFBA, and SpSqlAuthz

  5. Restart the web service.

Domain account password changed

If a password for one or more of the required domain accounts changes, then you must update the credentials for that domain account in the following locations:

  1. In IIS Manager for any application pools that were configured to use the domain account.

  2. In the Windows Services console, filter the list of services according to Log On As and change any service that was configured to use the domain account.

  3. If necessary, in SharePoint Central Administration, click Security > Configure managed accounts. Edit or delete accounts as necessary.

Error

Details

The file name is required error

If you experience this error in the Command Prompt window after you execute a script it means that you did not add the oob-topology.xml and oob-settings.xml files to the end of the script. Each script must be executed in the following form:

.\ScriptName.ps1 oob-topology.xml oob-settings.xml

Error: 500 Internal Server

If you experience this error in the Command Prompt window after you execute the Deploy-FarmSolutions script, it means that you have not installed the URL Rewrite Module 2.0 on the SharePoint server. Install the URL Rewrite Module and then execute the Deploy-FarmSolutions script again.

Error: System.Servicemodel.ServiceActivationException

If you see this error in the Command Prompt window after you execute any of the PowerShell scripts, it means that the server has insufficient RAM to complete the operation. Verify that the server has a least 10 GB of RAM. If possible, increase the amount of RAM to 16 GB or 32 GB and then execute the scripts again.

Error: System.InvalidOperationException: standardCategoryField.TermSetId is empty Guid

This error can mean one of the following.

  • One of the SharePoint application pools is not running in IIS Manager.

  • The Managed Metadata Service application is not installed in SharePoint.

  • The wrong SKU of SharePoint is installed on the server.

Verify that all application pools are running in IIS Manager and that the Managed Metadata Service application is installed and running in SharePoint. If you still see this error, then uninstall all versions of SharePoint and restart the server. Reinstall SharePoint Server 2013 and execute the PowerShell scripts again.

Error: Cannot add the specified assembly to the global assembly cache: <DLL name>

There are two possible issues/solutions for this error.

The DLL you are trying to add to the global assembly cache (GAC) already exists on the server and is blocked by another process such as the SharePoint Timer service or IIS. Restart the server and rerun the deployment scripts.

The DLL does not exist on the server and you must manually add the DLL to the GAC by using the following command at a command prompt: gacutil -if <DLL name>

Rerun the deployment scripts

Error: System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)),

Verify that the user you specified in the oob-settings.xml file for the ProductCatalog and PublishingPortal (storefront) application pools has sufficient permission to modify properties on the root website in SharePoint. One of the Windows PowerShell scripts tried to modify the title of the root web site when this error occurred.


Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).

Community Additions

ADD
Show: