Yeah I ran dsrepair unattended and local.
Also advanced/check volume objects and trustees.
Object is still yellow circle and question mark.
Main Topics
Browse All TopicsNDS Server appears as Unknown object (yellow circle with ?).
NW 6.5.6
Anyone know how to repair this?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
An eDirectory object becomes unknown because it has somehow lost one or more mandatory attributes. Is this the only server in the tree? If not does it hold volumes with user files on it? I ask the second question because it will mean trustee assignments need to be preserved by transferring External References (a nwconfig process when a server is removed from the tree).
If this is the only server in the tree, and you can still login to it, I'd suggest copying all user files from all volumes, running a utility called tbackup.exe from the root of each volume. You can download the utility by searching for tback3.exe. Running the exe will create a trestore.bat with the explicit trustees in each volume. Once you've done this, remove the server from the tree and after reboot, put it back in.
Another option is to build another server and use the server migration utility (SCMT.EXE downloadable from www.novell.com/downloads).
Lastly or first, you might try to run DSREPAIR -P which will mark unknown objects as "referenced" which may bring it back. You might also use the DSBROWSE -a utility and do a tree browse to the server object and see if you can see the attributes. DSBROWSE doesn't usually let you edit anything.
Novell Tech Support can "dial-in" and fix the problem if none of the above work. Their DSDUMP utility is magic. If you need a Service Request, I have plenty.
Scott
Business Accounts
Answer for Membership
by: alextoftPosted on 2008-12-31 at 03:50:22ID: 23269290
FIrst port of call would probably be DSREPAIR. If you're not acquainted with its more complex capabilities, run an Unattended Full Repair. See what that turns up, and perhaps post the Errors section here if possible.