I'd say check first if other applications are working on the Windows host and check the event logs for errors that would point to the source of the problem.
If you do come to the conclusion that everything works except NetWorker, then make sure Dr. Watson is enabled and check for a crash of nsrd and check the daemon.raw for details. If nsrd keeps failing on startup, you can also start the nsrd from the command line "nsrd -D9 > nsrd_out 2>&1" and check the nsrd_out file for details of what it's doing on startup. This should give you some indication of why it fails.
This will at least give you good data to provide to support.
Having library issues, which required reboots/installations, the server shutdown suddenly on one occasion now takes a long time to come back up (applying computer settings)
Every time you reboot, or just this 1st time it did?
Tried to open NMC, and started getting the message "Program not registered" when attempting to connect
That means nsrd is not running.
When it does start, the "NetWorker Backup and Recover Server" wont start
I cant get any info from nsrlic, it reports nsrd isnt running,
That would be alligned with previous.
Tried to start the service and I get the following message:
"Could not start the NetWorker Backup and Recover Server service on Local Computer" The service did not return an error. This could be an internal Windows error or an internal service error. If the problem persists, contact your system administrator."
Any advice ?
For some reason service does not start. if the machine itself is no longer healthy, this could be the reason itself.¸ Unless you tried, do another reboot and check if it comes back properly. If not, check event logs and examine what error do you get. Some of notes there sometimes pinpoint to what the problem is. If nothing helps, go to cmd and check if nsrexecd is running (client service). If not, try to start it by typing nsrexecd -D9
Check if you get any error messages (if it was not running, most likely you will see it there).
If it is running, and it is just server daemon you can't run, do nsrd -D9 and check what error messages do you get.
In case of nsrexecd running and nsrd not starting, most likely you have mdb corruption which is caused by crash. In such case, quickest way out is really to restore from bootstrap. However, if the whole box is unhealthy, you may wish to reinstall whole server and then restore from boostrap. In such case, pay attention to original settings like domain name, hostname and stuff which is in hosts table.
coganb
736 Posts
0
October 21st, 2011 00:00
Hi,
I'd say check first if other applications are working on the Windows host and check the event logs for errors that would point to the source of the problem.
If you do come to the conclusion that everything works except NetWorker, then make sure Dr. Watson is enabled and check for a crash of nsrd and check the daemon.raw for details. If nsrd keeps failing on startup, you can also start the nsrd from the command line "nsrd -D9 > nsrd_out 2>&1" and check the nsrd_out file for details of what it's doing on startup. This should give you some indication of why it fails.
This will at least give you good data to provide to support.
-Bobby
coganb
736 Posts
0
October 21st, 2011 06:00
You should check the system date on the machine as well. If this was reset after the reboot, it could cause a lot of problems.
-Bobby
ble1
4 Operator
•
14.4K Posts
0
October 24th, 2011 10:00
Every time you reboot, or just this 1st time it did?
That means nsrd is not running.
That would be alligned with previous.
For some reason service does not start. if the machine itself is no longer healthy, this could be the reason itself.¸ Unless you tried, do another reboot and check if it comes back properly. If not, check event logs and examine what error do you get. Some of notes there sometimes pinpoint to what the problem is. If nothing helps, go to cmd and check if nsrexecd is running (client service). If not, try to start it by typing nsrexecd -D9
Check if you get any error messages (if it was not running, most likely you will see it there).
If it is running, and it is just server daemon you can't run, do nsrd -D9 and check what error messages do you get.
In case of nsrexecd running and nsrd not starting, most likely you have mdb corruption which is caused by crash. In such case, quickest way out is really to restore from bootstrap. However, if the whole box is unhealthy, you may wish to reinstall whole server and then restore from boostrap. In such case, pay attention to original settings like domain name, hostname and stuff which is in hosts table.