Error: "NDPSM-2.20-280. Error (327682) occurred while creating a Service Registry reference."

(Last modified: 11Apr2005)

This document (10058960) is provided subject to the disclaimer at the end of this document.

fact

Novell Distributed Print Services (NDPS) 2.1.1

Novell NetWare 5.1

Novell Distributed Print Services (NDPS) 2.0

Novell NetWare 5.0

symptom

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 <printer agent name> with the SRS."

NDPS unable to connect to an SRS broker, even though broker with SRS enabled is running on same NetWare server and NDPSM.

Running DISPLAY SLP SERVICES SRS.NOVELL at the server console fails to show SRS service running on local server.

cause

An NDPS Service Registry Service (SRS) broker service cannot be located by the NDPSM.NLM.  We observed that this problem can occur after changing the IP Address of the server.

fix

Whenever an NDPS Service Registry Service (SRS) broker service cannot be located by the NDPSM.NLM, the error "NDPSM-x.xx-280. Error (327682) occurred while creating a Service Registry reference" will appear at the server console when NDPSM.NLM is loading.  What this message literally means is that by querying SLP and SAP (depending on which protocols are present) an NDPS SRS broker service could not be located.

Although this represents a problem, it may be an accurate condition to report about the current environment.  i.e. Indeed, neither SLP nor SAP were able to successfully locate a running NDPS SRS broker service.  To troubleshoot this condition investigate the following aspects:

1.  If you are seeing this error after changing your server's IP address, then follow these steps.
          a.  Edit DPLSV386.REG.  
          b.  If the old IP address is found within that registry file, then change it to the new IP Address.
          c.  Reboot the server, or
                               - unload NDPSM, BROKER, DPLSV386 (with all of it's dependencies)
                               - load Broker, ndpsm

2. Ensure BROKER.NLM is successfully running on the server(s) where it is expected to be located.  Ensure BROKER.NLM isn't reporting any error conditions during load or on the "NDPS Broker" console screen which may pertain to why the broker services are not available.

3. Ensure that the Service Registry Service (SRS) service is actually enabled on the BROKER.NLM server(s) where it is expected to be located.  BROKER.NLM can be successfully running without any SRS broker service enabled.  When viewing the "NDPS Broker" console screen, ensure that the "Service Registry Service" status shows "(Enabled)".  If it does not show "(Enabled)", highlight the "Service Registry Service" status on the "NDPS Broker" console screen and press ENTER to enable the service.  Ensure there are no errors reported as the SRS broker service attempts to initialize.  Use NWADMN32.EXE to view the NDPS broker object's SRS tab and ensure the SRS broker service is enabled on the NDPS broker object such that it should start automatically.

4. On the server(s) where BROKER.NLM is running, use "display slp services" and/or IPXCON.NLM to determine whether the SRS broker service advertisement is visible from the local server.  To check for the IP advertisement (if the server has IP bound), run "display slp services srs.novell" at the server console; an IP address from the local NetWare server should be listed as one of the service:srs.novell URLs.  To check for the IPX advertisement, in IPXCON.NLM go to Services | Display Selected Entries and in the "Type" field enter "8202" and then select "Proceed"; the name of the local NDPS broker object should appear as a type 8202 advertisement on circuit "Internal Network".  If the SRS broker service can be confirmed to be running without error yet the advertisement cannot be seen even from the local server, then one of the actual known issues described below may be at fault for why the SRS service cannot be located.

5. On the server(s) where NDPSM.NLM is running (if different from the server(s) where BROKER.NLM is running), use "display slp services" and/or IPXCON.NLM to determine whether the SRS broker service advertisement is visible from the local server.  To check for the IP advertisement, run "display slp services srs.novell" at the server console; an IP address(es) from the NetWare server(s) where BROKER.NLM is running with SRS enabled should be listed as "service:srs.novell" URLs.  To check for the IPX advertisement, in IPXCON.NLM go to Services | Display Selected Entries and in the "Type" field enter "8202" and then select "Proceed"; the name of the broker(s) running SRS should appear as a type 8202 advertisements.  If the SRS broker service(s) can be confirmed to be running without error, if the advertisements CAN be seen from the server(s) where BROKER.NLM is running but CANNOT be seen from the server(s) where NDPSM.NLM is running, then there is most likely some factor in the SLP, SAP, routing or switching configuration which is keeping the advertisements from successfully propagating and being visible to other parts of the network.

In short, after confirming that the NDPS SRS broker service is even running and is launching without error, check whether the NDPS SRS broker service is visible locally on the server where BROKER.NLM is running.  If it's not visible even from the same local server, then there is likely some SLP or protocol-level issue which kept the NDPS SRS broker service from successfully registering with SLP and/or SAP.  If the NDPS SRS broker service IS visible locally on the server where BROKER.NLM is running but IS NOT visible from other servers where NDPSM.NLM is running, then something is preventing mechanisms such as SLP multicast, SLPDA registration or propagation, SAP propagation, etc. which are required in order for the services to be successfully resolved from across the network.

Known issues:

The SLP v1.07 modules included with NW51SP1 and NW5SP5 may show an issue which presents 327682 error symptoms at the NDPS level.  This issue is described in "NDPS unable to find SRS in IP-only environment after applying NW51SP1 or NW5SP5".

The SLP v1.04 modules included in NetWare 5.0 SP4 and the NetWare 5.1 shipping code also presented a similar issue which resulted in 327682 errors being reported, as described in "NDPS unable to find SRS in IP-only environment after applying NW5SP4 or installing Novell NetWare 5.1".

.

document

Document Title: Error: "NDPSM-2.20-280. Error (327682) occurred while creating a Service Registry reference."
Document ID: 10058960
Solution ID: NOVL34590
Creation Date: 05Dec2000
Modified Date: 11Apr2005
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.