Schema and NDPS Manager

[bobmothers]

Hi

In an attempt to get NDPS printing loaded, in an attempt to get away from well documented queue based hassles, I loaded NDPS Manager which unfortunately bombed out with various errors. Through Novell's website found the problem and followed the fix in TID 100064649. Have now deleted the NDPS Manager in the schema but don't seem to be able to run the NDSSCH.exe and the associated .SCH files (NDPS100,NDPS200 and NDPS 201). In command prompt it returns 'Error -495 attempting to intialise unicode tables'

All I type in at the command prompt is:

'ndssch.exe m:\public\ndps100.sch'

Am I missing something here? I need to get the NDPS manager loading (that was the initial problem) in order to set up NDPS printing.

Currently on NW 5.1 SP3 and am about to jump to SP7. Workstation is XP Pro fully SP'd.

Any help or advice greatly appreciated.

Bob

 

[Provogeek]

Hmm, well I highly doubt you deleted anything in your schema because once it is added to your schema, you can't remove it. You will get errors if you try to install a schema extention that is already there.

Quick NetWare lesson:
The NDS schema defines the classes of NDS objects (such as User, Printer, and Group) that can be created in your NDS tree. Every type of object in an NDS tree has a class defined for it in the tree's schema.


From your post I understand that you deleted the NDPS Manager object in your tree.

Try this, using a 5.1 overlay CD just do an install of NDPS. This will ensure you have all the proper files and schema extentions on your server. If you do not use an overlay and end up using shipping media, be sure to install your current service pack after installing NDPS to get the NDPS updates in the service pack.

First create your broker if you don't already have one, then create your manager. Load your Broker and allow it to complete any operations it chooses it needs to run (normaly wants to do a driver database compression/scan/sanity check/eat up CPU cycles). Once the broker is done playing around, load your manager. You can load either of these just by loading the NLM and browsing the tree to find the broker and manager objects. You can also apend the load command with the distinguished name of the objects (which is how you will want it in your autoexec.ncf).

Note: The Broker and the Manager are not directly tied to each other, the Manager will attach to the nearest Broker it finds. In many organizations, you only need one broker for the entire network. Rule of thumb is one broker for every 5 hops on a network (granted WAN line speeds can change that rule).

If you continue to get errors loading the NDPS Manager, please post what those errors are.

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt Certified nut case
Senior Network Engineer

http://www.kiscc.com

 

[bobmothers]

Hi Brent

Will try this when I get back to the office tomorrow.

Thanks

Bob