/build/static/layout/Breadcrumb_cap_w.png

Start Service Problem

Am trying to start a system service SENTINEL during installation but the Installer is throwing Error 1920 and says you donot have sufficient privileges to start system service.

Could any1 help me out on this problem.

0 Comments   [ + ] Show comments

Answers (19)

Posted by: anonymous_9363 15 years ago
Red Belt
0
Clearly, the account with which you're installing doesn't have sufficient privileges to control services. Use an account which does! :) Alternatively, use an administrative account to assign the right 'Log on as service' to the account you're using.
Posted by: mekaywe 15 years ago
Brown Belt
0
am using admin account to install the application/ control the service.
Posted by: Inabus 15 years ago
Second Degree Green Belt
0
Is it a re-package?
Posted by: anonymous_9363 15 years ago
Red Belt
0
am using admin account to install the application/ control the service.Can you start the service from the command line or from Services.MSC? Is the service set to use Local System in the MSI?
Posted by: mekaywe 15 years ago
Brown Belt
0
its a legacy setup so capture using setup capture.

The service is not listed in services.msc
its present under msinfo32->system drivers
Posted by: anonymous_9363 15 years ago
Red Belt
0
My apologies...once again, I skim-read instead of reading properly. You did say that it's a system service.

So, is it set to use Local System in the MSI?
Posted by: mekaywe 15 years ago
Brown Belt
0
could you let me know how can we check whether the service is set to use local system in MSI?
Posted by: anonymous_9363 15 years ago
Red Belt
0
Use the (free) tool Orca to open the MSI if you don't have other MSI-authoring software.

Browse to the 'ServiceInstall' table. If the column 'StartName' is empty, then the service will use the System account.
Posted by: mekaywe 15 years ago
Brown Belt
0
Thanx for the update

checked the StartName using Wise., its Empty

the issue is not resolved still
Posted by: anks_09 15 years ago
Orange Senior Belt
0
Hi mekaywe,

I had encounter the same problem with package VPN client.Actually seens the package installs the drivers and the service which it is running is a driver service.Take picture taker(tool used to capture the installation resources) snapshot for the msi which you have capture and also a picture taker snapshot for the legacy setup(Source).Compare both the picture taker file few registry in Service hives("HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\") must be missing you can spot the difference through registry compare tool like Beyondcompare.Include those missing registry into the package through registry table i am sure it will work then.The problem is the driver is not been installed properly.Try the solution..i hope it will work!!

Regards,
anks_09
Posted by: Inabus 15 years ago
Second Degree Green Belt
0
I would personally suggest that its an issue with either capturing and deploying too much registry information for the service or not enough registry information and / or not using the services tables correctly.

Without seeing the package I coudlnt say which.

P
Posted by: mekaywe 15 years ago
Brown Belt
0
Thanks anks
will give a try
Posted by: Inabus 15 years ago
Second Degree Green Belt
0
("HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\")

The above shouldnt be captured only ("HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\") as 001 is simply a clone of CurrentControlSet.

P
Posted by: mekaywe 15 years ago
Brown Belt
0
Actually after SetupCapture during saving WSI it is prompting that
" During installation a service was created that included a account name. The password for this account is need for the service to function. Do you want to enter the password now? "

What does it mean? does it effect anything on the service ?
Posted by: anonymous_9363 15 years ago
Red Belt
0
NOW you tell us?!? I give up...
Posted by: mekaywe 15 years ago
Brown Belt
0
Am sorry.... thought that this might not effect service functioning.

Could you pleast atleast let me know whether we can start the service in this case?
Posted by: anks_09 15 years ago
Orange Senior Belt
0
Hi mekaywe,

That means it is capturing information which is account based.I guess you get back to the vendor of the application for finding the solution how can you avoid this problem.You cannot make an msi of legacy application which installs a resources which is machine dependent or application which capture resources which is account specific.

Regards,
anks_09
Posted by: mekaywe 15 years ago
Brown Belt
0
Is there any other way we can package the application or going back to Application Owner is preferred?
Posted by: Inabus 15 years ago
Second Degree Green Belt
0
Yes, this should be an account which will be available to every machine which the package will be deployed too, a local admin for example.

P
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ