2013-11-01 08:05 AM
I just did an in place upgrade of VSC 4.1 to 4.2.1. When looking at the roles inside the VIC, I do not see any of the new default canned vsc roles. I now have no access to my backups. Has anyone seen this before? Is a reboot required? It is not mentioned in the documentation from what I saw, but it could have been over looked.
Solved! SEE THE SOLUTION
2013-11-01 08:53 AM
The new roles should be created/updated on VSC service startup. Verify that the file VSC_INSTALL_DIR\etc\roleDefinitions.xml was installed, and restart the "Virtual Storage Console for VMware vSphere" service. Do you see any related log entries in nvpf.log during startup?
2013-11-01 09:29 AM
the RoleDefinitions.xml file is on the system. When reading through the nvpf.log the only thing glaring out at me is the following which occurs for some of the roles.
"Communication failure while creating role: VSC Administrator com.vmware.vim25.NoPermission"
2013-11-01 09:41 AM
The account used to register the VSC is an Admin role without the permission to change permission, otherwise it is a full admin. As previously stated, I cannot see any of the "canned" VSC roles inside the VIC.
2013-11-04 07:55 AM
Just so I understand,
What do you see in VSC_INSTALL_DIR\log\nvpf.log on VSC service restart?
2013-11-04 08:16 AM
That is correct. I am seeing the same things in the log. The only thing that glares out to me is "Communication failure while creating role: VSC Administrator com.vmware.vim25.NoPermission".
Checking the event log I see the following: Persistence file ../../etc/vsphere-credentials does not exsist. as well as ../../etc/cred I am however seeing these files.