Microsoft KB Archive/929388

From BetaArchive Wiki
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Knowledge Base


An “identity of application pool CRMAppPool is invalid” message is logged in the Application log after you configure CRMAppPool for a domain account user in Microsoft Dynamics CRM

Article ID: 929388

Article Last Modified on 1/4/2008



APPLIES TO

  • Microsoft Dynamics CRM 4.0
  • Microsoft Dynamics CRM 3.0



SYMPTOMS

When you run the CRMAppPool application pool after you configure the application pool for a domain account user in Microsoft Dynamics CRM, the following message is logged in the Application log: The identity of application pool CRMAppPool is invalid.


When this issue occurs, the CRMAppPool application pool cannot start.

This issue occurs even if the domain account user is a member of the local administrator group.

CAUSE

The issue occurs because the permissions or the user rights of the domain account user are insufficient.

RESOLUTION

To resolve this issue, follow these steps:

  1. Include the domain account user in the following groups in Active Directory:
    • The Domain Users Active Directory group
    • The PrivUserGroup
    • The SQLAccessGroup

    To do this, follow these steps:

    1. Log on to a server as a user who has the Domain Admin rights or the rights to update these groups.
    2. Right-click the Domain Users group in Active Directory, and then click Properties.
    3. In the Group name box, type the name of the user who is running the CRM Application Pool, and then click OK two times.
    4. Repeat steps b and c for the PrivUserGroup group and for the SQLAccessGroup group.

    If you have more than one Microsoft Dynamcis CRM deployment installed, multiple groups exist in Active Directory. To determine the groups that you want to update, follow these steps.

    For Microsoft Dynamics CRM 3.0

    1. Run the following SQL statement against the MSCRM database:

      select organizationid from organizationbase
    2. Note the GUID. For example, the GUID may be C8AB1D52-9383-4164-B571-4C80D46674E3.
    3. Find the PrivUserGroup group and the SQLAccessGroup group in Active Directory. The group name contains the GUID that you noted in step b.

    For Microsoft Dynamics CRM 4.0

    1. Run the following SQL statement against the MSCRM_config database:

      select id, friendlyname from organization
    2. Note the GUID. For example, the GUID may be C8AB1D52-9383-4164-B571-4C80D46674E3 Org Name.
    3. Find the PrivUserGroup group and the SQLAccessGroup group in Active Directory. The group name contains the GUID that you noted in step b.
    Note If more than one organization was created in Microsoft Dynamics CRM 4.0, the security groups contain the GUID of the first created organization.
  2. Include the domain account user in the following groups in the Microsoft Dynamics CRM server:
    • The local IIS_WPG group
    • The local CRM_WPG group

    Note The domain account user must have the following local user rights:

    • The Impersonate a client after authentication right
    • The Log on as a service right

    To do this, follow these steps:

    1. In the Microsoft Dynamics CRM server, click Start, point to Administrative Tools, and then click Local Security Policy.
    2. Expand Local Policies, and then click User Rights Assignment
    3. Right-click Impersonate a client after authentication, and then click Properties.
    4. Click Add User or Group.

      Note You may have to click Location to select the domain instead of the local computer.
    5. In the Group name box, type the name of the user who is running the CRM Application Pool, and then click OK two times.
    6. Repeat steps 2c through 2e for the Log on as a service right.
  3. Restart Internet Information Services (IIS). To do this, click Start, click Run, type IISRESET, and then click OK.


Keywords: kbmbscrm40 kbtshoot kbmbsadministration kberrmsg kbmbsmigrate kbprb KB929388