HELP!!! Cannot start a custom service during setup...

[DCCoolBreeze]

I have created a custom service and included it into a WISE MSI. The application compiles fine but when I run the setup MSI it created the application will not start the service. It responds after a timeout with Error 1920 insufficient priviledge problem. The installation program has no problem creating the service and I can start the service from the "Windows Services" application. I can also start the service using SC.EXE. Does anyone know why the setup program is unable to start the service????

Also Priviledged property is TRUE

 

[JACEVEDO10]

Symptoms
Error 1920 is a Windows Installer error that occurs only at run time and is displayed in the following format:

Service '[SERVICE]' failed to start. Verify that you have sufficient privileges to start system services.
[SERVICE] resolves to the name of the service.


--------------------------------------------------------------------------------


Causes
The service name specified in the InstallShield Development Environment (IDE) is not the correct service name. This may happen if the Windows Control Panel Services name was used instead of the 'internal' name of the service. The service has a registered, or internal, name and also has a displayed name. These names do not necessarily match. The 'internal' name must be specified in the IDE in order for the service to be controlled.

A dependent service is not installed or is disabled on the target machine. Some services require other services to be running on the target machine before it will successfully run itself. If these service are not available, the service attempting to be controlled may fail.

The user does not have rights to run the service. Some services are only available to run under a specific Log On account. The user must be logged on under this account to successfully run the service.

--------------------------------------------------------------------------------

Resolutions
Resolution 1

Go to the Components section of the IDE and expand the component node in your project that is controlling the service in question.

Expand the component's Advanced Setting folder and click the Control NT Services section.

On the right, you will see the name of the service the component is trying to control. Make sure that you do not confuse the event with the service name (the event is found under the service name). Take note of the service name.

To find the 'internal' name you must go to a machine that already has the service installed. On that machine, go to the registry by typing regedit at the Start | Run command box.

Once in the registry, navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services. The service's 'internal' name has its own key under the Services key. Because the internal name can be different from the display name, you may not recognize the name displayed. If this is the case, you can click each key under the Services key and check the DisplayName value for the key. The DisplayName value is the name as it appears in the Windows Control Panel. Once you find the correct DisplayName, take note of the key it is found within.

If the 'internal' name matches the name specified determined under step 3, this is not the cause of the issue. Otherwise, change the name from step 3 to match the internal name.

Rebuild the release.
Resolution 2

If you are not sure which services the service you are trying to control depends upon, check on a machine that the service is already installed. On Windows 2000/XP machines, dependencies can be checked by right-clicking the service and choosing Properties. Under the Dependencies tab, there is a list of the dependent services.

Verify that all dependent services are installed and running.
Resolution 3

If you are not sure which account the service logs on as, check on a machine that the service is already installed. On Windows 2000/XP machines, the Log On field can be checked by right-clicking the service and choosing Properties. Under the Log On tab, you can see which account the service logs on as.

Verify that the user is logged on under the correct account when launching the installation.

aLSO CHECK THE ACTIONS AND MAKE SURE YOU ARE INSTALLING THE SERVICE