Error 1920 / Service failed to start during client install

I had similar issues with one box and remedy was:

a) uninstall NW

b) reboot machine

c) install NW

I'm not sure why reboot was needed after uninstall actions, but it did clear whatever was keeping install from succeeding previously.

Hrvoje Crvelin  - I can not uninstall because nothing has been installed, I am trying a fresh installation, I rebooted the machine and tried again but that has not helped as well.

Regards

tech88kur

Hrvoje Crvelin - yes, registry cleanup was done.

Regards

tech88kur

Did you run cleanup of registry? 

I believe MSI switches allow debug option - try to install it that way to get more information as to why does it fail.  Also, can you say WHERE does it fail?  Does it fail after installation is done and while it has to start services or somewhere else before?

Ok, I will enable logging, at the moment I have increased the service start up time to 60 second, I am again going to try installation.

Installation never completes, it gives the error 1920: service failed to start just at the very last moment where the installer package tries to bring up the service and from here on nothing progresses; so installation has to be aborted because it does not move forward on retry and I keep getting the pop-up 'Error 1920:........' each time I press the retry button.

Regards

tech88kur

So, so failure is only due to start of service... It would be cool if there would be way to instruct installation without attempt to start service as then you just have to focus on main problem Given that it fails at point of starting service, I doubt MSI debugging will help - it would be great if we could have it installed without service being started and then start service in debug mode - that would be great.

Hrvoje Crvelin  - just tried with increased service start up time ( increased to 60 seconds from default 30 seconds) . But no change, the installation still could not forward from error 1920: Service failed to start.

What could be next to be done.

Regards

tech88kur

Please stop mentioning my name as then I get notifications for thread twice and I find it irritating. 

Next thing it to have debug on Windows level as I said to see why services do not start (or if you know how to install it without services being started, do that first as then it is easier from troubleshooting perspective).

Hi All,

Finally went to EMC support. They were right on target to suggest that this may be due to cryptocme2.dll conflict , we found the file in Program Files, renamed it and re-tried installation. It worked this time, the service came up and installation completed.

Regards

tech88kur

Error 1920 Service Networker Remote Exec Service failed to start: This error is related to permissions. Here is the solution.

Log in to the computer.

Right-Click on Command prompt > Run as Administrator

At the command line, navigate to the location of the networker software on your computer. (Example: C:\temp\setup.exe)

Run the setup.exe from the command prompt.

The installation completes without fail on multiple systems in our DC.

Please give it a try and let me know how it goes. Thanks!

My 2 cents worth.

Seeing this on a few 2008 and 2008R2 boxes, one 2012R2 box.  All test boxes so far.

I'm writing a package to install 8.2.2, same basic switches as previous version and it works on most but, same problem as folks are having here.  The automated install is silent, as is the backout when the services won't start.  I can run the install manually, from an elevated prompt, when it gets to the point where it tries to start the services it spawns the error (rights issue -- I'm logged in as a DA)...  Here's my wrinkle.  I change the logon on the services to my account, save it, says i'm granted rights to start services... I go right back and put them back to the local system account, save it, hit retry on the error dialog box and it finishes the installation.

That said, I can uninstall/reinstall 8.1.1 all day without issues.  But when I encounter this, 8.2.2 is pooched.  Side effect of the above work around is that if I uninstall 8.2.2 I can then install it without issues.

I did just notice the dll above, guess i'll look at that next. 

One thing I can add here is also that I have observed sometimes (I could not see clear pattern as to why and when) that installation may fail at starting daemons and only way to fix it was to delete nsrladb and then try install again. Since that would fix it I suspect something either kept services from not starting or keeping them starting much longer than timeout check.  Yet another possibility to check (makes only sense with installations which already exist - on new ones you have virgin system and therefore no nsrladb exists).

Thanks for the heads up on the file.  nsrdb.lck had restrictive perms, had to take ownership and add perms to delete.  Once that was done the service would start.  Testing with a command line install with the startsvc=0, that allows the install to complete and test with the service installed.  Looks like I need to add a fix in my install script, even a small percentage of failed installs would be problamatic in my environment. 

Thanks again though, that file was the problem. 

Good afternoon!

We have the same problem when trying to install the client 8.2.2. We tried to install on physical and virtual servers. The problem is the same. Windows 2008 R2 x64. Installation tried to do a local administrator and domain administrator.

On other servers where the client is successfully installed, NetWorker server does not see the client. Windows 2008 R2 x64.

If you go back to version 8.1.0.5, then everything works fine.