Error 1920 / Service failed to start during client install

Open a command prompt as an adminiatrator . I.e right click on the command prompt icon and select "Run as Administrator". Launch the networker.msi from within the command prompt.

--- Original Message ---

Hi guys,

I’m having the same issue with a customer, the environment is a Windows 2012 Hyper-V server and Networker 8.1 client. I had tried all the suggestions and currently working with support and engineering, they think the issue has to do with windows service start-up time, the default 30 seconds isn’t long enough to start the service and eventually times out. Support has tested this and was able to recreate the problem in their lab and work around resolved the issue. The work around is to extend the default start-up time for the services from 30 seconds to 10 minutes. Keep in mind this is a global change and affect default startup time for all windows services. It hasn’t been listed as a bug in Networker as of yet. We have yet to try the fix with customer, hopefully sometime this week.

Thanks,

Ken Ciolek

EMCISA, EMCIEs, EMCTAs, EMCCIS

Solutions Architect

Data Protection & Availability Division (DPAD)

PS Americas East (NY/NJ) Delivery

EMC2

Center 78

184 Liberty Corner Road, 4th Floor

Warren, NJ 07059

mobile: 201-983-1537

email: Kenneth.CiolekJr@emc.com

I suggest:

1. Uninstall any NetWorker components from appwiz.cpl (Programs and Features in Control Panel).
2. Reboot the computer into Safe Mode (When restarting, keep pressing F8 and select Safe Mode).
3. Open cmd, copy and paste the following command and press Enter.

REG ADD HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\MSIServer/VE/TREG_SZ/F/D %Service%

4. Type the following command and press Enter:

net start msiserver

5. Install NetWorker again.

If the issue persists, please verify whether the installation package is correct. In addition, please check whether you can install Office components or Windows Live Messenger (check if Windows Installer is good).

You can also try:

Right-click the installation package and click Run as administrator. Then install the package.

The last time I tried the right click on the msi file did not list the run as administrator option. Anyways its worth a try.

--- Original Message ---

OK. This indicates UAC has already been turned off on your computer and you can ignore this suggestion.

I forgot to mention that I do use "Run as Administrator" option to start the installation.

The service gets stuck in the "Starting" state, so maybe Kenneth is on something here. Kenneth, did youo get the same error message after it failed to start within the allotted time? I guess it isn't really a permission problem because it would pop up immediately, not after a while.

Also, unlike most of our clients, these two are 32 bit.

I will try the rest of the suggestions if we can get a downtime as this is a production server.

Yes….same exact error. We had tried all the previous suggestions, also had Microsoft look into OS issues and nothing. Support finally came up with what I posted earlier and in my case they think it had to do with multiple Hyper-V clusters. The environment was 4 Hyper-V clusters we’re trying to install Networker client on, 2 of them were successful and the other 2 had this error.

Ken Ciolek

EMCISA, EMCIEs, EMCTAs, EMCCIS

Solutions Architect

Data Protection & Availability Division (DPAD)

PS Americas East (NY/NJ) Delivery

EMC2

Center 78

184 Liberty Corner Road, 4th Floor

Warren, NJ 07059

mobile: 201-983-1537

email: Kenneth.CiolekJr@emc.com

Thanks, sounds promising, we will give it a go.

Hi All,

I too faced the same issue while installation on a win2k8 machine. A pop-up came up saying "....Error 1920....Unable to start nsrexecd...check permissions...". Once I had this i went to services.msc saw that there is nsrexecd in stopped mode. I tried starting it but it started and stopped again. I saw that it is trying to come up with local system account .....what was happening is it was starting and then stopping...so i changed the log on account to a user account which had local and domain admin privileges and restarted it, the service came up.....went back to wizard, clicked retry in the pop-up and then the wizard finished successfully.

Regards

tech88kur

Hello all,

This looks like a known issue, currently being investigated by EMC engineering under escalation number:

NW158505

Maybe you would like to open a case with support and mention this reference, or else follow Kenneth's recommendations

Thank you,

Carlos

I can confirm that increasing the service startup timeout in system registry resolved the problem for me as well. IN my case it was not a HyperV cluster member which by the way we do have and they don't suffer from this problem.

I had the same problem with the NW client installation on a Server 2012 ("R1") wich runs the Hyper-V role.

After changing the startup time to 1 min. the installation was comleted successfully.

For those who are not familiar with changing the default service startup time I provide a link to the Microsoft KB where it is described as a workaround:

http://support.microsoft.com/kb/922918/en-us

Dear All,

All the posts described earlier mention the problem in Windows OS >2008.

I am running a VM in vSphere 5.0 environment, guest OS is Windows Server 2003, System Type - X86-based PC and getting the same "Error 1920.....", there are no permissions related issues as the installation was successful on every other VM.

Does changing the service start up time applicable here as well?

I have tried different installer packages from 8.0.2.6 to 8.0.3.3 but all are giving this error.

Regards

tech88kur