1 Rookie
•
8 Posts
0
7988
October 26th, 2020 03:00
Program not registered
Hello everyone, i got myself into bit of a pickle with networker.
networker server on one of our environments was pretty well stuck after i came in after the weekend, pretty much nothing worked as it should. Decided to go for a restart of services, but "service networker restart" wasnt able to stop the services at all.
So not knowing any better i tried to kill the processes manually and now im .
Basically whatever im trying to do now, i am getting this error message
"Unable to connect to the server : Program not registered.
Running version 19.1.1.1 on RHEL 7.6
I am quite new to the backup and i already scoured all the threads i could find with similar issues with pretty much no result.
One of them suggested bootstrap recovery, which would seem i will not be able to do aswell because of the same error.
Is there some good sould who would be able to help me? Can provide any needed information (i realize i provided basically nothing, but im not sure what i should put here)
Backup_newbie
1 Rookie
•
8 Posts
0
October 29th, 2020 02:00
So over the night my colleague who is leaving fixed the issue (and haven't told me a single word about how as usual) So nothing left to do here now. Sadly i am not able to provide steps to solution here in case someone will have same issue
But really thanks for the provided advices and willingnes to help bingo!
Backup_newbie
1 Rookie
•
8 Posts
0
October 26th, 2020 05:00
Im running this on RHEL server, but i will try to replicate these steps in linux environment, thanks for reply
bingo.1
2.4K Posts
0
October 26th, 2020 05:00
Suggesting a bootstrap recover is the very last method you should use.
The message indicates - as you correctly found out - that some nsr... processes/services did not stop properly and consequently will not be able to be restarted.
Let me suggest the following:
- in Windows Task Manager, kill all nsr... processes to stop the system
- rename ..\nsr\logs\daemon.raw
- you may want to set both NW services startup method to 'manual'
- reboot the system to '...get java stable...'
- start the NW client process: net start nsrexecd - should not cause any issues.
- start the NW server process: net start nsrd ... and wait. Monitor the upcoming processes in the Task Manager details. After some minutes (depending on the size of your system) finally nsrd should appear.
- if not, run "nsr_render_log daemon.raw > file.txt" and investigate the step what will prevent the system form coming up again.
Backup_newbie
1 Rookie
•
8 Posts
0
October 26th, 2020 06:00
So i tried to replicate the steps and reboot the server... after it came back its probably even worse
When i try to start nsrd manually it looks like it cannot connect to itself (server running on localhost)
173680 1603717652 3 2 111 3571103552 17000 0 server01 nsrd RPC error 22 RPC client handle: %s. 1 24 18 Connection refused
172089 1603717652 3 2 111 3571103552 17000 0 server01 nsrd RPC error 91 Unable to create the connection with '%s' to host '%s' with address '%s' at port number %d. 4 20 10 portmapper 12 9 localhost 14 9 127.0.0.1 1 4 7938
Colleague (who is way more skilled than me, but is quitting today) told me after brief description the DB is most likely corrupted and i will need to reinstall the networker.... so now im scouring the internet for some info on how to do that and what should i manually backup beforehand (just to be sure, we should have regular backups, but i have no way of checking them now)
bingo.1
2.4K Posts
0
October 26th, 2020 06:00
Ooops - sure. My mistake.
The procedure is generally the same. You should be able to run the services as processes (if necessary).
bingo.1
2.4K Posts
0
October 26th, 2020 08:00
Re-installing NW will most likely not solve the issue.
First of all, you should not verify the daemon.raw file with a standard text editor but with nsr_render_log. This will replace the variables by the real names/parameters.
"Connection refused" is most likely the key message here. It indicates that the NW server is not allowed to connect to the NW client. To solve the issue ...
- stop the NW service/daemon on the client
- edit /nsr/res/servers appropriately and add at least the NW server name
- restart the NW service/daemon on the client
And of course ensure that the firewall port 9737 & 9738 are open.