Windows: Installation Fails When User Does Not Have Correct Privileges or Incorrect Password Is Entered (6394017) (Sun N1 Service Provisioning System 5.2.1 Release Notes)

Sun N1 Service Provisioning System 5.2.1 Release Notes

Previous: Problems Starting the Master Server on Solaris Systems That Do Not Meet Minimum System Configuration Requirements (6395197)
Next: Uninstallation Issues

Windows: Installation Fails When User Does Not Have Correct Privileges or Incorrect Password Is Entered (6394017)

The user is installing a Master Server, Remote Agent, or Local Distributor on a Windows system. If the user chooses to run the Windows Service as Other Account, the user needs to provide a username that has Log on as a service privileges. If the user types an invalid password or the username does not have Log on as a service privileges, the installed services fail to start.

When the services fail to start, one of the following error messages is displayed:

Master Server

After reboot, the installation will fail because the database setup requires that the postgres services are running. Since the credentials given for the Other Accountare invalid, the postgres service fails to start, the installation hangs, and the following error message is displayed:

At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.
Remote Agent

Error 1920.Service cragent (cragent) failed to start. Verify that you have sufficient privileges to start system services.
Local Distributor

Error 1920.Service crdistributor (crdistributor) failed to start. Verify that you have sufficient privileges to start system services.

This error occurs because the user typed an invalid password or the username does not have Log on as a service privileges. Username validation only validates the existence of the user on that computer. The credentials are not checked to see if the password is valid for that user or if the username has "Log on as a service" privileges.

Workaround: To prevent this error, implement one of the following workarounds:

Verify that the password to be entered for the Other Accountis valid and that the username has Log on as a service privileges.
Select the System Account option instead of the Other Account option. In this case, the user is not required to provide a username or password. The installation will continue and the services will run under the SYSTEM user.