Server installation and upgrade issues
This section describes how to troubleshoot Microsoft Dynamics CRM Server 2011 installation issues.
In This Topic
Timeout expired error message during organization upgrade
Clients cannot connect to Microsoft Dynamics CRM Web application
Microsoft Dynamics CRM Server 2011 cannot connect to Microsoft SQL Server
Troubleshooting WIF installation failures
Claims-based authentication issues
'Login failed for DomainName\ServerName$" error message after Microsoft Dynamics CRM Server 2011 install, repair, or configure
Timeout expired error message during organization upgrade
During an organization database upgrade, you may receive the error message:
InstallDatabaseAction failed. ---> System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
To work around this issue, add the OLEDBTimeout and the ExtendedTimeout registry subkeys to increase the time-out values. For more information, see A time-out occurs when you import large customization files into Microsoft Dynamics CRM
Clients cannot connect to Microsoft Dynamics CRM Web application
Clients may be unable to connect to the Microsoft Dynamics CRM web application. This issue can occur when the following conditions are true:
The Microsoft Dynamics CRM web application is configured for a TCP port that is not the default port (80), such as 5555.
Windows Firewall does not include an exception for the TCP port.
To resolve this issue, add the port as an exception in the firewall configuration on the server where Microsoft Dynamics CRM is installed.
Microsoft Dynamics CRM Server 2011 cannot connect to Microsoft SQL Server
This issue can occur when Windows Firewall does not include an exception for the TCP port used by Microsoft SQL Server. By default, the TCP port used by Microsoft SQL Server is 1433. For more information, see Configuring the Windows Firewall to Allow SQL Server Access.
Troubleshooting WIF installation failures
To help resolve issues that may occur when you install Windows Identity Framework (WIF), start Event Viewer and locate the Setup folder under Windows Logs. Filter on the source WUSA.
Claims-based authentication issues
Verify the certificate that you are using is valid for the associated Web site. Open the certificate and view the name. A wildcard certificate (for example, *.contoso.com) can authenticate all sub-domains in the contoso.com domain. You can also use a Subject Alternative Names certificate or an individual certificate (for example, auth.domain.com:5555).
'Login failed for DomainName\ServerName$" error message after Microsoft Dynamics CRM Server 2011 install, repair, or configure
You may receive this error message when you try to sign-in to Microsoft Dynamics CRM after you install, upgrade, repair, or configure Microsoft Dynamics CRM Server 2011.
This issue occurs when the following conditions are true:
The server where you perform the installation, upgrade, repair, or configure action is located in a domain that is operating at a Windows Server 2003 domain functional level.
One or more Microsoft Dynamics CRM service accounts are configured to use Network Service.
To work around this issue, restart the server where Microsoft Dynamics CRM Server 2011 is installed.
See Also
Concepts
Troubleshooting installation and upgrade
Install Microsoft Dynamics CRM Server 2011 on multiple computers