Error 1920 while creating new service
Team
While creating new service in wise 8 it’s giving error
“Error 1920.Service’Reg’(reg)failed to strart. Verify that you have sufficient privileges to start system services.â€Â
Plz help me.
While creating new service in wise 8 it’s giving error
“Error 1920.Service’Reg’(reg)failed to strart. Verify that you have sufficient privileges to start system services.â€Â
Plz help me.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
murali.bhat
13 years ago
Can you create & run the service manually with the logged in user priviledges?
Posted by:
honeyslim
13 years ago
Hi Murali,
Error 1920 resolved but after install application that app service should be start but it’s not starting when try to start manually it’s giving below error
“Error 1053:the service did not respond to the start or control request in timely fashionâ€Â
Error 1920 resolved but after install application that app service should be start but it’s not starting when try to start manually it’s giving below error
“Error 1053:the service did not respond to the start or control request in timely fashionâ€Â
Posted by:
murali.bhat
13 years ago
Try creating the service and starting it manually. Use SC command.
SC CREATE <servicename> <binPath= "C:\Program Files\....">
and then start the created Service.
SC START <servicename>
If that works, you can use the SC in a custom action. Otherwise you may need to contact the developer.
SC CREATE <servicename> <binPath= "C:\Program Files\....">
and then start the created Service.
SC START <servicename>
If that works, you can use the SC in a custom action. Otherwise you may need to contact the developer.
Posted by:
honeyslim
13 years ago
Able to create Service from SC command
But not able to start service from SC command getting Error 1053 any other suggestion plz
But not able to start service from SC command getting Error 1053 any other suggestion plz
Posted by:
anonymous_9363
13 years ago
ProcMon will show you what's happening during the service start-up. Normally, it's due to some other process failing. Does the service talk to a remote server/web site or something like that?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.