Knowledgebase

NetWare 6.0 NSS Volume IDs are Zeroed Out By Open File Manager

Return to Knowledgebase

Issue: Some users are reporting that NetWare 6.0 NSS Volume IDs are being zeroed out by St. Bernard Software’s Open File Manager. After DSrepair is run on the server, the following entry appears in the DSrepair log:

Repairing volume object for volume <VOL_NAME>
Directory services volume object ID: 00000000
ERROR: The volume has never been installed
New volume object DN:
CN=HARTSOCK60_<VOL_NAME>.O=SBS.T=HARTSOCK60.
Contacted a replica on server:
.CN=HARTSOCK60.O=SBS.T=HARTSOCK60.
The volume object has been created for this volume, ID: 0000806B
The volume has been attached to the volume object
Volume: <VOL_NAME>, object ID: 0000806B, CN=HARTSOCK60_<VOL_NAME>.O=SBS.T=HARTSOCK60
Checking trustees on volume: <VOL_NAME>.

Cause: When a NetWare 6.x backup job is in progress, Open File Manager maintains a “Synchronized NSS Volume” for each Novell NSS volume on a NetWare 6.0 server. The code that was intended to zero the NDS ID of Open File Manager’s Synchronized NSS Volume objects was zeroing the NetWare 6.0 NSS volume objects instead.

One manifestation of this issue is that if a drive is mapped to more than one of Open File Manager’s Synchronized NSS Volume objects on a server with multiple NetWare 6.0 NSS volumes, each drive mapping will point to the same Synchronized NSS Volume regardless of its actual contents.

Solution: Upgrade to the latest build of Open File Manager to resolve this issue. To upgrade to the latest Open File Manager build, contact your Open File Manager sales representative. If you purchased Open File Manager directly from, use this link to initiate the upgrade: http://ofm.evault.com/contact.asp

NOTE: Running DSrepair resets the volume objects to the correct ID.