Article
Problem
A Forum reader asked this question:
"I have had the server which was our master eDirectory replica for several partitions crash. The server was also the DA and ran the Broker for NDPS. I have deleted the server object from eDirectory and changed the replica settings to make a different server master. I have also recreated the CA and the SLPDA object and made the necessary changes to the servers.
We are now experiencing problems with our NDPS Managers and our users not being able to print. The users cannot connect to the printers. When the manager is unloaded and reloaded, a screen comes up and lists the root context with nothing but a dot in its content. I have tried loading ndpsm referencing the manager object but have not had any luck.
Are there any procedures I should be going through to restore these services? Any ideas on why NDPS is acting up?"
And here's a suggestion from Novell's Akos Szechy ...
Solution
As you removed the server from the tree all the references are gone for the server, volume. Therefore NDPSM does not know which server and volume it belongs to.
1. In ConsoleOne, go to the Manager object.
2. Click the Other tab.
3. Add the following two attributes:
- Host device => point it to the NCP server object
- Database volume => point it to the volume where the NDPS database is stored (most likely the SYS volume)
The Database Dir Path should be there.
4. Assign [S] trustee rights for the Manager objects to this path.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.
Related Articles
User Comments
- Be the first to comment! To leave a comment you need to Login or Register
- 3047 reads


0