When running a data migration with Quest NDS Migrator, the following entries may be seen in the logs:
139 - [12:00:00.055] Unable to resolve SID 12345 on QUEST-SOFTWARE-INC/SERVERNAME. Object not added to cache. Error was FFFFFDA7
The "unable to resolve SID #####" means that Novell trustee (SID #####) is no longer within the Novell Directory (been deleted). And if a file has that removed user as an Owner, then this is returned to the logs.
This error can be reproduced using the following steps:
- Create user ABC in Novell
- Assign user ABC as the owner for file 1.TXT
- Delete user ABC
- At this point, trustee ABC is still set as the owner for 1.TXT; when Quest NDS Migrator reads the owner value, Quest NDS Migrator will try to resolve the value (SID #####) by doing a reverse lookup within the Novell Directory (which will fail).
...at this point if an attempt is made to view the Owner value via NWAdmin, a prompt about the owner will appear.
To resolve these properly, run DsRepair and the OwnerId value will be set to 0 (the correct value where an owner is deleted) and these errors will be suppressed when Quest NDS Migrator is run. Please see also below recommendation from Novell about DSREPAIR:
Otherwise, these "Unable to resolve SID #####" can be ignored as within Quest NDS Migrator will set the value to either the current logged on account (using Quest NDS Migrator) or there is a option which if the owner is not found, a specified owner can be specified.
For more information on the 'File Ownership' option, please see the current Quest NDS Migrator User Guide section titled "File Ownership" for more detail.
For more information on Novell's DSRepair, please see the following Novell article titled "Using DSREPAIR to Maintain the Novell Directory Services Database" found at the following link:
For more details on the returned Novell error 'FFFFFDA7', please see the following Novell article titled "-601 FFFFFDA7 NO SUCH ENTRY" found at the following link: