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”.

This article describes a scenario where the installation of Microsoft Office Project Server 2003 rolls back and a “StartPrjServices: Failed to start service” error message is logged in the verbose installation log file. There are two possible causes of this issue. A work-around is discussed that you can try as well as two methods that you can try to resolve the issue.

SYMPTOMS:

When you run the Setup program to install Project Server 2003, the installation process unexpectedly rolls back. The following error message is logged in the verbose installation log file:

StartPrjServices: …attempting to start PjSessionMgr
StartPrjServices: Failed to start service.
StartPrjServices: Error 0x80004005: …failed to start PjSessionMgr
Action ended XX:XX:XX: InstallFinalize. Return value 3.

CAUSE

This issue may occur if one of the following conditions is true:

Insufficient permissions are configured for the folder where Project Server 2003 is installed. For example, this issue may occur if the Local Service account does not have permissions to the folder where Project Server 2003 is installed.

Security settings in the local computer policy prevent the Setup program from starting the services that are used by Project Server 2003.

WORKAROUND

Warning! Use this workaround only if the following are true:

You experience the exact error message that is mentioned in the “Symptoms” section.

You suspect that the security settings in the local computer policy are preventing the Setup program from starting the services that are used by Project Server 2003.

To work around this issue, enable the Prohibit rollback security setting on the computer, and then install Project Server 2003. Then, configure the services that are used by Project Server 2003 to use a Microsoft Windows domain user account that has sufficient credentials.

1. Enable the Prohibit rollback security setting.

To do this, follow these steps:
a. Click Start, click Run, type gpedit.msc in the Open box, and then click OK.
b. Under Local Computer Policy, expand Computer Configuration, expand Administrative Templates, expand Windows Components, and then click Windows Installer.
c. Right-click Prohibit rollback, click Properties, and then click the Setting tab.
d. Click Enabled, and then click OK.

2. Run the Setup program to install Project Server 2003. The installation of Project Server 2003 finishes. However, you will receive error messages.

3. Configure the services that are used by Project Server 2003 to use a Windows domain user account that has sufficient credentials.

For example, configure the services to use the Windows domain user account that you specified in the Pscomplus.exe tool. The services that are used by Project Server 2003 include the following:

Project Server Scheduled Process Service
Project Server Session Mgr Service
Project Server Tracing Service
Project Server Views Notification Service

To configure these services, follow these steps:

a. Click Start, point to Administrative Tools, and then click Services.
b. Right-click the service, click Properties, and then click the Logon tab.
c. Specify the user account that you want the service to log on as, and then click OK.
d. Right-click the service, and then click Start.

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:

a. Start Windows Explorer, right-click the folder the Program Files folder, and then click Sharing and Security.
b. Click the Security tab.
c. Click Add, type LOCAL SERVICE in the Select Users or Group dialog box, and then click OK.
d. In the Permissions for LOCAL SERVICE area under Allow, click the following check boxes, and then click OK.

Read & Execute
List Folder Contents
Read

e. 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:

a. Start Internet Information Services (IIS) Manager.
b. Expand ServerName, and then expand Application Pools.
c. Right-click DefaultAppPool, click Properties, and then click the Identity tab.
d. Click Predefined if it is not already selected.
e. Click Local Service, and then click OK.
f. 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

Leave a Reply

Your email address will not be published. Required fields are marked *