NDPSM fails to load for new Print Manager

[Anonymous_User]

Hello,

I’m trying to set up iPrint services on a server that I’ve had to rebuild after a hardware failure. Backups did not include the NDPS folder at the root of the SYS volume, so I decided to delete the broker, print manager and associated printer agents from eDir and start over. I am able to use iManager to create the broker and upload printer drivers without any problem. I can create the print manager also, but starting it seems to be an issue. When I go to the server console and type load ndpsm and browse to the print manager, I get the following message:

“The NDPS Manager’s database resides on volume ‘NI_FS1_SYS.NI.SBUSD’. The database for the NDPS Manager is not on this file server or the volume containing the database is not mounted. The database must be moved to a mounted volume on this file server to continue.”

I’m then prompted to move the database and if I select yes, the only available volume listed is ADMIN_NI_FS1.NI.SBUSD. If I select no, then NDPSM unloads.

The NI_FS1_SYS.NI.SBUSD volume is mounted, so I'm not sure why I'm having a problem with it.

The server is running NetWare 6.5 SP 8, the broker is v 3.0.12, and the print manager is v 3.02f.

iPrint was installed to the server after rebuilding it, but the old broker, print manager, and printer agents were still in eDir, but I’m not sure if this means anything. I was planning on visiting the school site and uninstalling iPrint and deleting the broker and print manager from eDir and then reinstalling. I’m not sure if there are any log files that I can take a look at for more info, but any suggestions for a course of action are appreciated.

Thanks!

[phxazcraig]

Perhaps using the command line option /DBVOLUME=NOCHECK to load NDPSM
will let you get farther along?

Craig Johnson
Novell Support Connection SysOp

[Anonymous_User]

Thanks, that command line option allowed the NDPS Manager load up without complaint and I was able to start creating printer agents to test. Is this something I can continue to use to load NDPSM on this server? After I set up a few printers and tested them, I unloaded the manager and reloaded without the /DBVOLUME=NOCHECK option and got the warning again, then reloaded with it again and was fine.

Thanks again!

[phxazcraig]

In article <mwagnon.3zehoo@no-mx.forums.novell.com>, Mwagnon wrote:
> Thanks, that command line option allowed the NDPS Manager load up
> without complaint and I was able to start creating printer agents to
> test. Is this something I can continue to use to load NDPSM on this
> server? After I set up a few printers and tested them, I unloaded the
> manager and reloaded without the /DBVOLUME=NOCHECK option and got the
> warning again, then reloaded with it again and was fine.
>
There should be a fix - I just don't know what it is off the top of my
head. Probably something along the lines of moving ndpsm from one
server to another. (Actually, you could try moving it to another
server and then back again. There's got to be a shorter way, but that
might be the easy way.)

Craig Johnson
Novell Support Connection SysOp

[Marcel_Cox]

The NDPS Manager makes regular backups of its database to NDS. When you
select "NDPS Manager Status and Control" -> "Database Options" you should
have the option to restore the database from NDS. This will also restore
all the printers with their settings.

--
Marcel Cox
http://forums.novell.com