Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

5262

October 30th, 2012 06:00

Cannot find attribute 'client id'

We recently installed Netowrker 8 with PS install configuraiton.   Last night we received the error message "90018:save: Cannot open a save session with NetWorker server 'servername': Cannot find attribute 'client id'."  The previous 2 nights the backups worked and we have made no changes.  Since the install, 3 weeks ago, this occurs randomly throughout the week.  Any ideas on what would be causing this error? TIA

544 Posts

October 30th, 2012 13:00

I forgot to mention that if the above steps did not solve the problem , You may need to perform the following steps to solve the issue:

  1. Take a copy of the client ID from the client configuration
  2. Take a notes for all the client configurations (schedule, saveset, browse policy, retention polict, etc,.....)
  3. Delete the client from the NMC
  4. Stop the NetWorker services on the client
  5. Rename the /nsr/tmp and /nsr/res/nsrladb  folders to tmp.old and nsrladb.old
  6. Start the NetWorker services again.
  7. Re-add the client to the NMC again with the same client ID you take a copy of in step 1
  8. Re-configure again the client with the same old configurations taken in step 2
  9. Start a test backup.

Waiting your updates.

Ahmed Bahaa

544 Posts

October 30th, 2012 13:00

Hi dcharmatz,

In most cases the "Cannot open a save session " errors are either connectivity or name resolutions issue, you have to test the communication between server and client, you can perform the following steps:

Try to do the following from the backup server to the networker client ( using short name and FQDN name):

•check hosts-file if you can find the client

•ping

•nslookup

•rpcinfo -p

If this all works, try to do the following from the client to the backup server ( using short name and FQDN name):

•check hosts-file if you can find the backup server

•check server file under the nsr directory if the backup server is added there

•ping

•nslookup

•rpcinfo -p

Hope this helps,

Ahmed Bahaa

No Events found!

Top