"Error -765: Error getting NDS name from pool" and "Error -765: -765 Error converting GUID to name"
during Update NDS (F4)
We were successful doing it this way all the times till now.
Cybersecurity
DevOps Cloud
IT Operations Cloud
If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more
fgiese;2216767 wrote:
After successfully reinstalling edirectory on OES11 server, I need to recreate nss-pool and volume object into edirectory. By using the nssmu-tool, we get the error
"Error -765: Error getting NDS name from pool" and "Error -765: -765 Error converting GUID to name"
during Update NDS (F4)
We were successful doing it this way all the times till now.
fgiese;2216802 wrote:
Before reinstalling edirectory, we deleted all server related objects including pool and volume object in NDS. After this successful operation, we used the yast2 nss command to recreate the local admin object as we did serveral times. After that the nssmu utility is listing pool and volume but updating NDS is failing. The server holds no replica of the root partition.
Viewing pool and volume during iManager produces following message:
"Error: CIMOM error occurred: could not seek in the management file."
Doing this on other servers works pretty good. Ndsrepair commands (-T, -E, -C -Ad -A) showed other servers in the tree and ended without any error message.
--Ferdi
fgiese;2216802 wrote:
Before reinstalling edirectory, we deleted all server related objects including pool and volume object in NDS. After this successful operation, we used the yast2 nss command to recreate the local admin object as we did serveral times. After that the nssmu utility is listing pool and volume but updating NDS is failing. The server holds no replica of the root partition.
Viewing pool and volume during iManager produces following message:
"Error: CIMOM error occurred: could not seek in the management file."
Doing this on other servers works pretty good. Ndsrepair commands (-T, -E, -C -Ad -A) showed other servers in the tree and ended without any error message.
--Ferdi
fgiese;2216997 wrote:
Thanks, El for Your patience with me. I checked the Unix Workstaion object and found out that there was no openwbem entry under LUN enabled services. And I didn't find any oportunity to make a change on that settings. If this may cause the error, it would be very nice if you can tell me how this can be done.
Thanks
--Ferdi
HvdHeuvel;2217210 wrote:
On Mon, 03 Sep 2012 20:16:02 0000, fgiese wrote:
I think you need to update your server to latest patches to resolve this
particular issue. This seems to be described in TID 7005336.
This was addresed in the "June 2012 OES11 Hot Patch for NCP - 6385"
Thanks
Hans