Unable to see print drivers in the NDPS/RESDIR directory from the NDPS broker object in NWADMIN.
(Last modified: 13Nov2002)
This document (10063957) is provided subject to the disclaimer at the end of this document.
fact
Novell NetWare 5.1 Support Pack 3
NetWare Cluster Services v1.01
symptom
Unable to see print drivers in the NDPS/RESDIR directory from the NDPS broker object in NWADMIN.
RESDIR file not compressing when loading the broker for the first time.
Error message An error occurred listing banner files Message Number :890 For more information, look up the following error code in the online documentation 0x01060004: 962
Error message An error occurred listing banner files Message Number :895 For more information, look up the following error code in the online documentation 0x01060004: 936
Printer drivers are not being compressed as they are on traditional or non-clustered NSS volumes.
Printer drivers on non-cluster volumes are not being compressed either.
The \RESDIR directory and/or subdirectories are set to Read-Only instead of Read-Write.
change
Upgraded from NetWare 5.1 Support Pack 2A to Support Pack 3
fix
This problem has been resolved with a new RMANSRVR.NLM dated 09AUG2001 and should be available from support.novell.com/filefinder. The name of the patch file NDP21P3C.EXE.
*** NOTE: Make sure the RMSSP3.TXT readme is read and understood before application of the patch. Failure to do so will result in the loss of your RESDIR and printer drivers. ***
The RMANSRVR.NLM dated 09AUG2001 will also check the \RESDIR directory and the contents below for Read-Only attributes. If the files or directories are set to Read-Only, RMANSRVR.NLM dated 09AUG2001 will flag those files and directories as Read-Write and then start directory structure move and file compression.
If the patch file is unavailable or you do not have access to the patch, you can do the following workarounds:
Workarounds:
1.) Stay on support pack 2a for NetWare 5.1
2.) Backrev the support pack 3 off the NetWare 5.1 server.
3.) Copy the Broker's driver database from the cluster volume to the SYS or non-cluster enabled NSS volumes on one of the servers in the cluster. Follow steps a - j of option 4 to have the printer agents use that new Broker. NOTE: The Broker will not be cluster enabled and will not fail over in the case of a server ABEND.
4.) If options 1, 2 and 3 are not options, then create a new Broker on a non-clustered server. Copy over any new drivers to the RMS database for each of the OSes that had drivers updated. To ensure that this new Broker gets used, do the following:
a.) Create your new broker on your non-clustered server. Copy any files you have added to RMS database to that Broker. Load that new Broker and make sure it is up and running.
b.) At the server cluster console running the NDPS Manager, type in "NDPS MANAGER DEBUG DISPLAY=ON" (without quotes).
c.) Toggle to the "NDPS Manager Debug Display" screen. This screen will be black.
d.) Type in the letter O (as in Other) and a list of 10 options will appear. Select option "4) Display PA info".
e.) You will be presented with "Enter Printer Agent Name or PA Number:" Type in the number 0 (zero). You will be given a list of information about printer agent 0. You will see "paName:" listed at the top. Write down the actual name of that printer agent, such as "Joe's color printer".
f.) Repeat steps c and d for the first 4 or 5 printer agents.
g.) Toggle to the server's console screen. Type in "NDPS MANAGER DEBUG DISPLAY=OFF" (without quotes). The "NDPS Manager Debug Display" screen will go away.
h.) Run NWADMN32 and find those 4 or 5 printer agents in the tree. Once you find the printer agents in the tree, select the printer agent in question and view the printer agent's details.
i.) Make sure the "Printer Control" button is available and selected. Click on the "Features" button. A "Features" box will open up. Select the "Services ..." button and a "Support Services" box will appear. At the bottom is a "Preferred Services" section. Change the "Notification Service" and "Resource Service" to be the new broker. Repeat this for the first 4 or 5 printer agents that you selected off that manager.
j.) Restart (unload and load) the NDPS Manager. What will happen is the NDPS Manager will see that the first printer agents have a preferred RMS and ENS selected and it will attempt to establish a connection to those preferred services. The remaining printer agents that were not modified will fail to connect to their preferred RMS and ENS. However, because the NDPS Manager has an established connection to an existing RMS and ENS, the Manager will use that connection and bind the remaining printer agents to the preferred RMS and ENS of the first few printer agents selected.
document
| Document Title: | Unable to see print drivers in the NDPS/RESDIR directory from the NDPS broker object in NWADMIN. |
| Document ID: | 10063957 |
| Solution ID: | NOVL54768 |
| Creation Date: | 02Aug2001 |
| Modified Date: | 13Nov2002 |
| Novell Product Class: | NetWare |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.