NDPS unable to find SRS in IP-only environment after applying NW51SP1 or NW5SP5.
(Last modified: 20Aug2003)
This document (10055901) is provided subject to the disclaimer at the end of this document.
fact
Novell NetWare 5.0
Novell NetWare 5.1
NW5SP5
NW51SP1
Novell Distributed Print Services (NDPS) 2.0
Novell Distributed Print Services (NDPS) 2.1
symptom
NDPS unable to find SRS in IP-only environment after applying NW51SP1 or NW5SP5.
Error: "NDPSM-2.20-280. Error (327682) occurred while creating a Service Registry reference."
Error: "NDPSM-2.11-280. Error (327682) occurred while creating a Service Registry reference."
Error: "-818 Error occurred while registering printer agent with the SRS."
Error occurs when NDPSM.NLM is loaded from AUTOEXEC.NCF or manually.
Problem only occurs in a pure IP environment.
Error does not occur if an SLP directory agent (SLPDA) is present.
Error does not occur if IPX is bound at the server.
NDPS unable to connect to an SRS broker, even though broker with SRS enabled is running on same NetWare server and NDPSM.
Issue occurs with SLP v1.07 modules included with NW5SP5 and NW51SP1.
Running DISPLAY SLP SERVICES SRS.NOVELL at the server console fails to show SRS service running on local server.
fix
This issue is currently under investigation by Novell. Additional information when known will be added to this document.
Primary workaround is to have an SLPDA available to the local server and/or running on the local server. If SLPDA will be running on the same server as NDPSM.NLM and BROKER.NLM, make sure the SLPDA is loaded in the AUTOEXEC.NCF prior to loading BROKER.NLM & NDPSM.NLM.
An alternative workaround is to load and bind IPX on the server to that the SRS can be located via SAP instead of SLP.
Note that if creating a new SLPDA to address this issue, NDPS may still report the 327682 error the first time it is restarted with the SLPDA running. But once the SRS.NOVELL service entry has been registered with the SLPDA, future restarts of NDPS will be able to obtain the service address immediately from the SLPDA.
Note that the 327682 error message will also be reported when the NDPS SRS broker service is legitimately unavailable, e.g. no BROKER.NLM running an SRS service is available, or no NDPS SRS broker service advertisement is able to successfully resolve through SLP or SAP. For a discussion of basic troubleshooting for the 327682 to engage before presuming that the 327682 error is the result of the issue described in this document, see the solution document titled Error: "NDPSM-2.20-280. Error (327682) occurred while creating a Service Registry reference".
Background:
Since applying NW5SP5 or NW51SP1, customer noticed that NDPS starts reporting "NDPSM-2.20-280. Error (327682) occurred while creating a Service Registry reference" during load.
This message indicates that the NDPSM was unable to locate an SRS broker service. Running "display slp services srs.novell" from the same server also fails to list any srs.novell URLs, which seems to be the same condition the NDPSM is reporting.
Currently this issue appears to be occurring on where the SRS must be located over IP (i.e. an IP-only server) and must use multicast ("active") SLP discovery methods. (i.e. No SLPDA available either on the local server or on the local network.)
By adding an SLPDA, SLP information is primarily gathered directly from the DA instead of relying on multicast methods. When troubleshooting, "display slp services srs.novell" should also now return the URL for the local SRS service.
Note that although the symptoms are similar, this issue is different from the SLP v1.04 issue described for NetWare 5.0 SP4 and NetWare 5.1 in NDPS unable to find SRS in IP-only environment after applying NW5SP4 or installing Novell NetWare 5.1..
document
| Document Title: | NDPS unable to find SRS in IP-only environment after applying NW51SP1 or NW5SP5. |
| Document ID: | 10055901 |
| Solution ID: | NOVL22404 |
| Creation Date: | 11Aug2000 |
| Modified Date: | 20Aug2003 |
| 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.