Export (0) Print
Expand All

Microsoft Dynamics CRM Server 2011 installation troubleshooting

The following section describes known issues and troubleshooting steps when you are installing Microsoft Dynamics CRM at a command prompt.

Setup fails or client receives an unhandled exception when trying to connect after you install Microsoft Dynamics CRM Server 2011

Setup may not complete successfully or any of the Microsoft Dynamics CRM 2011 clients may receive an error message when trying to connect to the Microsoft Dynamics CRM Server 2011 that is similar to items in the following list:

Exception from HRESULT. 0x80048306.

Description. An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details. System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80048306.

Source Error. An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

This problem can occur if you run Microsoft Dynamics CRM Server Setup when the following conditions are true:

  • One or more of the following Active Directory security groups was created in the organizational unit where you are installing Microsoft Dynamics CRM 2011:

    • PrivUserGroup

    • ReportingGroup

    • SQLAccessGroup

    • PrivReportingGroup

  • The previously mentioned security groups do not have the correct group membership.

  • You use the automanagegroupsoff=false attribute and value in the <Groups> entry for the Setup XML configuration file. To use a configuration file, you must install Microsoft Dynamics CRM Server 2011 at the command prompt.

To resolve this issue, you must manually add the correct membership to each of the required security groups in Active Directory, and then run Microsoft Dynamics CRM Server Setup again.

ImportantImportant
Direct user account membership to the Microsoft Dynamics CRM privusergroup security group is required and group membership nesting under privusergroup currently is not supported. For example, if you add a security group named mycrmprivgroupusers to privusergroup, members of mycrmprivgroupusers will not resolve as privusergroup members. This includes the CRMAppPool or the SQL Server Reporting Services service identities, which if granted membership to privusergroup through another security group, can cause system-wide failures in the Microsoft Dynamics CRM web application and reporting features.

To manually add the objects to Active Directory, use Active Directory Users and Computers. The following table contains the users and computers that you must add to each security group.

 

Security Group Object Type Description

PrivUserGroup

User

User who is running Microsoft Dynamics CRM Server Setup.

PrivUserGroup

Computer

Computer where Microsoft Dynamics CRM Server 2011 is installed.

PrivUserGroup

Computer

Computer where the Microsoft Dynamics CRM E-mail Router is installed (if you are using the E-mail Router).

SQLAccessGroup

Computer

Computer where Microsoft Dynamics CRM Server 2011 is installed.

PrivReportingGroup

Computer

Computer where Microsoft Dynamics CRM Reporting Extensions is installed.

ReportingGroup

User

User who is running Microsoft Dynamics CRM Server Setup.

ReportingGroup

User

Any user who will run Microsoft Dynamics CRM.

You Receive an Unknown Error (0x80005000) error message during a quiet-mode installation

You may receive an "Unknown Error (0x80005000)" during a quiet-mode installation. This issue can occur when you try to install Microsoft Dynamics CRM Server 2011 on a Windows Server computer that does not have Internet Information Services (IIS) installed and configured. To resolve this issue, install Internet Information Services (IIS) and then run Setup again. For more information about how to install Internet Information Services (IIS), see the Windows Server Help.

See Also

Send comments about this article to Microsoft.

© 2013 Microsoft Corporation. All rights reserved.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

Show:
© 2014 Microsoft