Symptoms

The NetWorker Management Console (NMC) produces an Error box stating "Unable to decrypt BAD_DATA". This error appears when trying to use various NMC tabs. Rendered Daemon.log 160859:nsrvproxy_mgmt: vProxy management job started with CLI: 'X:\App\EMC NetWorker\nsr\bin\nsrvproxy_mgmt.exe register -s NetWorkerServer.com -v vcenter.com -h vProxy-host-name -p 9090 -j 13 -k 0 ' 161332:nsrvproxy_mgmt: Starting 'vProxy-host-name' vProxy registration to 'NetWorkerServer.com' NetWorker server. 197027:nsrvproxy_mgmt: NW server IP/hostname not enforced during registration. NSR VMware proxy resource on 'vProxy-host-name' deleted. 161327:nsrvproxy_mgmt: Failed to register vProxy 'vProxy-host-name': Received an HTTP code: 500, libCURL message: "", vProxy message: "Error received from vProxy ="500: Unable to log in to vCenter 'vcenter.com': Post "https://vcenter.com/sdk": dial tcp ##.##.##.##:443: i/o timeout". ", url: "https://vProxy-host-name:9090/api/v1/VproxyEngines/RestEngine/Registration", body: "{"Config":{"SessionId":"","LogTag":"105","IdleTimeout":300,"LogLevel":"INFO","Username":"admin","Password":"****","NWS":"","Cp":"-----BEGIN CERTIFICATE----- #### REMOVED FOR BREVITY ######-----END CERTIFICATE-----\n-----BEGIN RSA PRIVATE KEY-----#### REMOVED FOR BREVITY ######" 161319:nsrvproxy_mgmt: vProxy management job completed with errors. - - - - getting an error when trying to ad vProxy: 160859:nsrvproxy_mgmt: vProxy management job started with CLI: 'X:\App\EMC NetWorker\nsr\bin\nsrvproxy_mgmt.exe register -s NetWorkerServer.com -v vcenter.com -h vProxy-host-name -p 9090 -j 13 -k 0 ' 161332:nsrvproxy_mgmt: Starting 'vProxy-host-name' vProxy registration to 'NetWorkerServer.com' NetWorker server. 161327:nsrvproxy_mgmt: Failed to register vProxy 'vProxy-host-name': Cannot create 'vProxy-host-name' vProxy resource: Failed to open lockbox X:\App\EMC NetWorker\nsr\lockbox\NetWorkerServer.com\clb.lb 161319:nsrvproxy_mgmt: vProxy management job completed with errors.

Cause

Incorrect passwords at NSRDB level

Resolution

Windows Servers Create a script file named "ok.txt" For example, to reset all passwords to blank, you can create a file named "ok.txt" and have the following inside: ## SCRIPT EXAMPLE START ## update password: ; y update management password: ; y update NAS management password: ; y update NAS file access password: ; y update Authentication Key: ; y update VMWS user password: ; y update EBR Password: ; y update REST Services Password: ; y update vCenter Password: ; y update Privacy Key: ; y update datazone pass phrase: ; y ## SCRIPT EXAMPLE END ## ACTION PLAN:1. Shutdown NetWorker net stop nsrexecd /y tasklist | findstr nsr 2. Make a copy of nsrdb and lockbox - call them nsrdb.beforepassclean and lockbox.beforepassclean Default Path > C:\Program Files\EMC Networker\nsr\res\nsrdb >> nsrdb.beforepasscleanDefault Path > C:\Program Files\EMC Networker\nsr\lockbox >> lockbox.beforepassclean 3. Run: nsradmin -i ok.txt -d "C:\Program Files\EMC Networker\nsr\res\nsrdb" 4. Make another copy of this modified nsrdb as the next step could corrupt the nsrdb if not done properly. Copy the current nsrdb to nsrdb.passwordblank CAUTION: If not done properly the nsrdb WILL be corrupt when starting. 5. If there is any dbg folder under nsrdb, rename the dbg folder to dbg.old (we do not want any dbg folder).6. Confirm that the ownerships for all files under nsrdb are owned by Administrator. If this is not set correctly, you must correct it. a) In windows explorer, right click on the C:\Program Files\EMC NetWorker\nsr\res\nsrdb folder.b) Select properties.c) Click the "Security" tab.d) Click "advanced".e) In Owner, click "Change".f) In the "Enter the object name to select" box, type: Administrators, then click on "Check Names." (Sometimes you must use the computer name, like BEN-BACKUP-S0\Administrators)g) Click OKh) Check the "Replace all child object permission entries…" and "Replace owner on subcontainers and objects" box.i) Click "Apply," then click "Yes" for "Do you want to continue?" Box.j) Click "OK" NOTE: All files under nsrdb MUST be owned by the group Administrators. If owned by a different user, the entries are sent to the dbg folder corrupting the nsrdb. 7. Start NetWorker services. net start nsrd If the NMC server is installed on the same server: net start gstd 8. Customer MUST reenter ALL passwords (like Data Domain, Modules, passphrases, so on) Linux Servers 1. Stop the NetWorker server services. # nsr_shutdown OR # systemctl stop networker # systemctl stop gst # systemctl stop nwui 2. Before any change, make a copy of the "nsrdb" and "lockbox" directories. # cp -rf /nsr/res/nsrdb /tmp/ # cp -rf /nsr/lockbox /tmp/ 3. Make sure all NetWorker services are down with tasklist: # ps -ef | grep nsr Use kill to kill any nsr service still up after NetWorker has been shut down. # ps -ef | grep savegrp (To get the PID) # kill -9 (To kill the process of savegrp) 4. Create a script file named "ok.txt" For example, to reset all passwords to blank, you can create a file named "ok.txt" and have the following inside: ## SCRIPT EXAMPLE START ## update password: ; y update management password: ; y update NAS management password: ; y update NAS file access password: ; y update Authentication Key: ; y update VMWS user password: ; y update EBR Password: ; y update REST Services Password: ; y update vCenter Password: ; y update Privacy Key: ; y update datazone pass phrase: ; y ## SCRIPT EXAMPLE END ## 5. Then run: # nsradmin -i ok.txt -d /nsr/res/nsrdb 6. Make sure the /nsr/res/nsrdb folder is owned by root (user and group) [root@lnx-nwserv]:~# ls -l /nsr/res/ | grep nsrdb drwx------. 13 root root 131 Aug 9 17:31 nsrdb If this is not set correctly, you must correct it: # chown -R root:root /nsr/res/nsrdb 7. Start the NetWorker server services. systemctl start networker systemctl start gst 8. You MUST reenter ALL passwords (like Data Domain, Modules, passphrases, so forth)

Support Cases