Unsolved
4 Posts
0
2461
September 12th, 2019 20:00
NetWorker Windows upgrade from 8.2.2 to 9.2.2 or 18.2. completed but fails to start nsrexecd
To perform NW update from 8.2.x to NW 9.2.1.5, The update procedure seemed to end up successfully, however, the at the start of 'nsrexecd' that followed, following error has been reported: NetWorker Remote Exec Service error: 1053 [1724:15DC][2019-05-22T12:07:36]i000: nsrexecd : Waiting for service operation timeout. Exit Code is Error Code = 1053. For 1053 system error Microsoft provided one KB article to increase time out value for start up service.But it didn't help.
https://support.microsoft.com/en-us/kb/922918 But when we run manually (nsrexed -D9) and it is runinng and backup also completed. Any other solutions to resolve this problem?
No Events found!
bingo.1
2.4K Posts
0
September 12th, 2019 21:00
I would be good to know whether you talk about a NW client or the NW server himself.
It might also help to know the Windows version and whether you update the OS as well.
Does the service just not start when you start/reboot the system? - Or does it also fail if you manually restart it? - If so, there must be an entry in the daemon.raw file and the reason as well.
Before you do anything else, let me suggest that you pay special attention to name resolution (also check with nsrclientfix). Next I would rename /nsr/res/nsrladb and try to restart the NW client service.
Also, do not forget that the new NW versions require new certificates (available from support).
ShivaYaniki
4 Posts
0
September 12th, 2019 22:00
bingo.1
2.4K Posts
0
September 13th, 2019 00:00
Are you aware that the NW client service will be listed as with the startup type "Automatic (Delayed Start)"? So you should not check to early.
What surprises me are 2 statements:
- no daemon.raw file will be created
- but backups will run successfully
I cannot really see how both can happen at all.
I do not know how you upgraded but could it be that you have to deal with 2 different locations?
As this is 'only' a NW client, may I suggest that you ...
- stop all services and processes (taskmgr)
- delete the NW software
- delete all directories and
- re-install the NW client software
ShivaYaniki
4 Posts
0
September 19th, 2019 23:00
bingo.1
2.4K Posts
0
September 20th, 2019 11:00
I am pretty sure that fragments of an earlier installation exist. Unfortunately, it seems that you have forgotten the path.
In this case, stop all NW programs and delete 'leftovers' from the resistry before you run a new install. Do not forget to look for strings like "EMC", "NetWorker" & "Legato" (lgto).
ShivaYaniki
4 Posts
0
October 15th, 2019 19:00
Finally ,I have resolved this issue. corrupted Java on Host causing this issue.After reinstall Java and set JAVA_HOME environmental variable then all services are working fine without any issue.
Thanks for your help