The installation of Project Server 2003 rolls back and an error message is logged in the verbose installation log file: "StartPrjServices: Failed to start service" (917486)

RESOLUTION

To resolve this issue, use one of the following methods.

Method 1: Configure permissions for the folder where Project Server 2003 is installed

Make sure that sufficient permissions are configured for the folder where you want to install Project Server 2003. If the Local Service account does not have permissions to the folder where Project Server 2003 is installed, follow these steps:

1. Add the Local Service account to the folder where you want to install Project Server 2003. For example, if you want to install Project Server 2003 to a subfolder of the Program Files folder, follow these steps:
   1. Start Windows Explorer, right-click the folder the Program Files folder, and then click Sharing and Security.
   2. Click the Security tab.
   3. Click Add, type local service in the Select Users or Group dialog box, and then click OK.
   4. In the Permissions for LOCAL SERVICE area under Allow, click the following check boxes, and then click OK.
      • Read & Execute
      • List Folder Contents
      • Read
   5. Make sure that the permissions are propagated to all subfolders in the Program Files folder.
2. Change the identity of the default application pool in Microsoft Internet Information Services (IIS) 6.0 to use the Local Service account. To do this, follow these steps:
   1. Start Internet Information Services (IIS) Manager.
   2. Expand ServerName, and then expand Application Pools.
   3. Right-click DefaultAppPool, click Properties, and then click the Identity tab.
   4. Click Predefined if it is not already selected.
   5. Click Local Service, and then click OK.
   6. Make sure that the permissions are propagated to all subfolders in the Program Files folder.

Method 2: Verify that security settings in the local computer policy are configured correctly

Verify that the following security settings are configured correctly in the local computer policy:

• Deny logon as a batch job
• Deny logon as a service
• Impersonate a client after authentication
• Logon as a batch Job
• Logon as a service

Note If another computer is available on which Project Server 2003 is successfully installed, compare these security settings with the security settings on that computer.

To verify security settings in the local computer policy, follow these steps:

1. Click Start, click Run, type gpedit.msc in the Open box, and then click OK.
2. Under Local Computer Policy, expand Computer Configuration, expand Windows Settings, expand Security Settings, expand Local Policies, and then click User Rights Assignment.
3. Right-click the security setting, and then click Properties.
4. Verify that the security setting is configured correctly, and then click OK. The following are examples of settings to verify:
   • Verify that the "Deny logon as a batch job" security setting and the "Deny logon as a service" security setting do not deny access to accounts that are required to install Project Server 2003 and to start Project Server 2003 services.
   • Verify that the appropriate accounts are added to the "Impersonate a client after authentication" security setting. These accounts include the following:
     • Administrators group
     • ASPNET account
     • IIS_WPG group
     • Service account
   • Verify that the appropriate accounts are added to the "Logon as a batch job" security setting and the "Logon as a service" security setting. These accounts may include the following:
     • ASPNET account
     • Network Service account
     • Local Service account
     • IUSER_ComputerName account
     • IWAM_ComputerName account
     • Windows domain user account that has sufficient credentials
     • IIS_WPG group