We have created a custom windows service. The deployment package is done in InstallShield and the installation prompts for the user name and password for the service Log On account.
We have had no issues at all installing on various Windows 7 (Professional) and Windows 8 machines, but we get the 1920 error when trying to deploy to a Windows 7 Ultimate machine. We have not yet confirmed whether the issue is to do with the OS or the specific machine that we are trying to install this on.
The installer is always run by right-clicking and "Run as Administrator", and the users (both, the user running the installer and the Logon User for which the credentials are supplied) are administrators on the machine. Usually the logged in user installing the service, and the Logon user running the service are the same.
Here are the things we have tried.
But none of the above work.
Hope that someone else has come across a similar issue and has a fix..
UPDATE:
I have also tried the following:
Navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies >User Rights Assignment. In the details pane, double-click Log on as a service. Click Add User or Group… and add the account to the list of accounts that have the Log on as a service right.
The error code 1603 means that the program is already installed so you should check that out. A solution for this issue is to close some of the processes in Windows 10. Lack of disk space can cause this problem therefore check if you have enough free space.
1920 is a generic error code that means the service didn't start. My hunch is this:
http://blog.iswix.com/2008/09/different-year-same-problem.html
To confirm, with the installer on the abort, retry, ignore, cancel dialog up... go into services.msc and set the username and password manually. If you get a message saying the user was granted logon as service right, try hitting retry on the MSI dialog and see if it starts.
It could also be missing dependencies or exceptions being thrown in your code.
I also had the same issue. I fixed this by installing the .NET framework version 4.5.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With