NDPS Broker latest events
(SYS$LOG.ERR)
RMS lost connection SRS
what would cause this?
In the network printer screen there was this message:
Printer Agent needs attention
I would think the this message was there because the NDPS broker had
problems.
Please help.
Fernando
Tim
No Direct e-Mail Please!
--
****************
Tim Heywood
Independent Consultant
Scotland
(God's Country)
Novell Support Connection SYSOP
****************
In theory, practice and theory are the same,
In practice they are different!
I checked the Sys$log.err and there is the following related with RMS:
1-30-2204 8:44:08 am: RMANSRVR-3.3-0
Severity = 3 Locus = 17 Class = 3
RMS Report: Building Driver Table of contents.
1-30-2204 8:44:25 am: RMANSRVR-3.3-0
Severity = 3 Locus = 17 Class = 3
RMS Report: Driver Table of Contents Complete.
I found out about the meaning of severity, locus and class.
3-critical-Critical errores are those that Netware tried to fix and
failed. These can occur when an NLM abends, but the server continues to
work.
17-OS information
3-Authorization failure
by the definition of critical; the NLM for the NPDS Broker abended?What
would cause this? how do I fix this? Do I need to run NSS rebuild?
Thanks for your help.
Fernando
If you look at the abend.log what can you see listed on the correct date?
We also need to know what Service packs and other patches you have applied to
the server. It is unlikely that an NSS patch (or a missing one) would have
caused this.
Tim
Fernando
Tim Heywood (NSC Sysop) wrote: