Two Win2K Domain Controllers Not Responding after March 2008 Updat

  • Thread starter Thread starter Andreas
  • Start date Start date
A

Andreas

Guest
Configuration: 2 HP/Compaq Proliant Win2K Domain Controllers, both with
DNS/DHCP/FRS and a Dameware Remote Control Agent (acted strange in logs Too,
so writing it down here).

On March 13th server 2 was not responding with messagelog:
Event Id 2510 : The server service was unable to map error code 1453.

On March 12th server 1 was not responding with a number of strange messages.

In both cases a Cold Boot was required, but the systems did not hang
completely.
 
Re: Two Win2K Domain Controllers Not Responding after March 2008 Updat

Hello Andreas,

Please post the complete error message.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Configuration: 2 HP/Compaq Proliant Win2K Domain Controllers, both
> with DNS/DHCP/FRS and a Dameware Remote Control Agent (acted strange
> in logs Too, so writing it down here).
>
> On March 13th server 2 was not responding with messagelog: Event Id
> 2510 : The server service was unable to map error code 1453.
>
> On March 12th server 1 was not responding with a number of strange
> messages.
>
> In both cases a Cold Boot was required, but the systems did not hang
> completely.
>
 
Re: Two Win2K Domain Controllers Not Responding after March 2008 U

Re: Two Win2K Domain Controllers Not Responding after March 2008 U

Event Type: Error
Event Source: Server
Event Category: None
Event ID: 2510
Date: 13-03-2008
Time: 08:17:16
User: N/A
Computer: SRV2
Description:
The server service was unable to map error code 1453.


"Meinolf Weber" wrote:

> Hello Andreas,
>
> Please post the complete error message.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
> > Configuration: 2 HP/Compaq Proliant Win2K Domain Controllers, both
> > with DNS/DHCP/FRS and a Dameware Remote Control Agent (acted strange
> > in logs Too, so writing it down here).
> >
> > On March 13th server 2 was not responding with messagelog: Event Id
> > 2510 : The server service was unable to map error code 1453.
> >
> > On March 12th server 1 was not responding with a number of strange
> > messages.
> >
> > In both cases a Cold Boot was required, but the systems did not hang
> > completely.
> >
>
>
>
 
Re: Two Win2K Domain Controllers Not Responding after March 2008 U

Re: Two Win2K Domain Controllers Not Responding after March 2008 U

I am having this exact same error message; After receiving this error
message; All my printers on this server stopped working. It took 2 reboots
before it started working... I was told that this might be due to Veritas
backup software and it possibly having invalid kernel filters.... Or due to
print drivers...

"Andreas" wrote:

> Event Type: Error
> Event Source: Server
> Event Category: None
> Event ID: 2510
> Date: 13-03-2008
> Time: 08:17:16
> User: N/A
> Computer: SRV2
> Description:
> The server service was unable to map error code 1453.
>
>
> "Meinolf Weber" wrote:
>
> > Hello Andreas,
> >
> > Please post the complete error message.
> >
> > Best regards
> >
> > Meinolf Weber
> > Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> > no rights.
> > ** Please do NOT email, only reply to Newsgroups
> > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> >
> > > Configuration: 2 HP/Compaq Proliant Win2K Domain Controllers, both
> > > with DNS/DHCP/FRS and a Dameware Remote Control Agent (acted strange
> > > in logs Too, so writing it down here).
> > >
> > > On March 13th server 2 was not responding with messagelog: Event Id
> > > 2510 : The server service was unable to map error code 1453.
> > >
> > > On March 12th server 1 was not responding with a number of strange
> > > messages.
> > >
> > > In both cases a Cold Boot was required, but the systems did not hang
> > > completely.
> > >
> >
> >
> >
 
Back
Top