When you say adding are you referring to wizard creation step or something else? If wizard, what about manual client creation? Or this is already defined client, but you get this after daemons on client have been restarted and backup is started from server towards client?
You might want to start with checking if NetWorker client is properly installed on if the services are running as expected. if you find all is OK, run a save on the client system to if you get a similar error. Don't forget about the iptables on the centos, (if running) add an exclusion or just turn it off.
You should Install the same version of client as the NetWorker server. After installing and starting the client do let us know if you get the same error.
If it already worked, there should be no need to do anything else.
Yes, an update would be nice but this also depends on the compatibility. Often you cannot update due to this reason.
NW 8.0.1 for Centos 5.7 is fine - at least not wrong.
However, make sure that all required libraries are (still) available.
Let me suggest you do the following:
- verify that nsrexecd on the client is still active
- verify that the connection to the client can be established (nsradmin -p nsrexec -s nw_client)
If you see the prompt, press 'q' to quit.
- verify the same from the client to the server (nsradmin -p nsrexec -s nw_server)
If both tests work, you should be fine to proceed with a manual backup from the client like for example : save [-s nw_server] /etc).
Then configure your resources and run the scheduled backup.
When exactly do you get the error? - I doubt it is at the creation of the client resource because ... if you create the client resource, NW just checks the hostname resolution.
You can easily verify that if you fake NW with an appropriate entry in the hosts table.
The servers file 'only' restricts the connection to the listed NW server. If you have more than one, make sure you have listed the correct one.
I've had similar problem. Client v8.0.2.2, Console 8.2.2.0. When try to configure client using wizard I get the message "Unable to connect to server: Application ID 62 is not recognized". I Upgrade client to v8.2.2.0 and it solved my problem.
ble1
4 Operator
•
14.4K Posts
0
March 31st, 2016 05:00
When you say adding are you referring to wizard creation step or something else? If wizard, what about manual client creation? Or this is already defined client, but you get this after daemons on client have been restarted and backup is started from server towards client?
crazyrov
4 Operator
•
1.3K Posts
0
March 31st, 2016 07:00
Hello @roberto_carna
You might want to start with checking if NetWorker client is properly installed on if the services are running as expected. if you find all is OK, run a save on the client system to if you get a similar error. Don't forget about the iptables on the centos, (if running) add an exclusion or just turn it off.
gautamgp
226 Posts
0
April 4th, 2016 22:00
Hi Roberto,
You should Install the same version of client as the NetWorker server. After installing and starting the client do let us know if you get the same error.
bingo.1
2.4K Posts
0
April 5th, 2016 03:00
If it already worked, there should be no need to do anything else.
Yes, an update would be nice but this also depends on the compatibility. Often you cannot update due to this reason.
NW 8.0.1 for Centos 5.7 is fine - at least not wrong.
However, make sure that all required libraries are (still) available.
Let me suggest you do the following:
- verify that nsrexecd on the client is still active
- verify that the connection to the client can be established (nsradmin -p nsrexec -s nw_client)
If you see the prompt, press 'q' to quit.
- verify the same from the client to the server (nsradmin -p nsrexec -s nw_server)
If both tests work, you should be fine to proceed with a manual backup from the client like for example : save [-s nw_server] /etc).
Then configure your resources and run the scheduled backup.
When exactly do you get the error? - I doubt it is at the creation of the client resource because ... if you create the client resource, NW just checks the hostname resolution.
You can easily verify that if you fake NW with an appropriate entry in the hosts table.
The servers file 'only' restricts the connection to the listed NW server. If you have more than one, make sure you have listed the correct one.
StuartWhitby
45 Posts
0
April 5th, 2016 08:00
Any messages in the client's daemon.raw?
mkos_180881
2 Posts
0
October 14th, 2016 02:00
I've had similar problem. Client v8.0.2.2, Console 8.2.2.0. When try to configure client using wizard I get the message "Unable to connect to server: Application ID 62 is not recognized". I Upgrade client to v8.2.2.0 and it solved my problem.