Unsolved
This post is more than 5 years old
2 Posts
0
4732
October 28th, 2013 07:00
Error code53362
I want to recover files for a client from EMC Networker 7.6.5. and i get this error message.
error code 53362:winworkr cannot start session with server xxxxxxx
xxxxxxx server is not properly configured on the networker server.
Can someone help.
Thanks
Mann
0 events found
No Events found!
JPCommunityMgr
Community Manager
•
3.1K Posts
0
October 28th, 2013 16:00
It seems this is Networker question. I moved this thread to an appropriate space "Networker Support Forum" from "Japanese Storage" space.
ble1
4 Operator
•
14.4K Posts
0
October 28th, 2013 18:00
Without exact error and logs it may be anything, but according to your description and most common mistakes, this seems to be an issue with configuration where client is missing alias in NSR client definition.
CarlosRojas
1.7K Posts
0
October 30th, 2013 03:00
Hi Mann,
Please check the following steps:
Does save set recovery fails with the same error?
Does nsrinfo -v client_name fails with the same error?
Started with a new index folder for client.
Ran nsrck -v lnalnm01.na.lafarge.net.
C:\>nsrinfo -v client_name
scanning client `client_name' for all savetimes from the backup namespace
error: nsrinfo: cannot start session with server
error: nsrinfo: error, Cannot lock file index for client 'client_name' (Access is denied.)
Permissions on the index folder are correct.
*@* added to Remote Access results in the same error.
Removing nsrauth results in the same error.
No clientid issues.
Forward and reverse lookup works successfully.
Networker services started with Local System.
Issue does not occur when running nsrck -L1.
Issue occurs when running nsrck -L2-L7.
A Group Policy (GPO) set in the customer environment caused the issue.
Confirmation:
When running filemon.exe (sysinternals) discovered that the NT AUTHORITY\SYSTEM account was getting ACCESS DENIED when trying to read the C:\Program Files\Legato\nsr\index\ \db6\v6hdr file.
When nsrck -L2-L7 is run the v6hdr file is recreated and thus the GPO takes effect.
The SYSTEM account does not have permissions.
Resolution
Workaround:
1. For the GPO: "Computer Configuration -> Security Settings -> Local Policies -> User Rights Assignment -> Restore files and directories", added the SYSTEM account:
- Created a new Group Policy for all of the NW servers in the environment.
- Added SYSTEM account to this policy to allow full control.
- Administrators & Backup Operators are default.
The 'Member Server Baseline Policy' has many restrictions in it which may also be affecting this.
The inheritance of this policy no longer gets applied to the parent 'Member Servers' OU.
2. For a temporary solution to complete the restore, replace permissions on the index folder affected allowing SYSTEM to have Full Control