Re: SBS 2003 failed on reboot!
From: WK (wkent_at_netsandbytesdotcom)
Date: 02/09/05
- Next message: Les Connor [SBS Community Member - SBS MVP]: "Re: SBS 2003 failed on reboot!"
- Previous message: Dave Nickason [SBS MVP]: "Re: SBS 2003 failed on reboot!"
- In reply to: Bryan Linton: "SBS 2003 failed on reboot!"
- Next in thread: Les Connor [SBS Community Member - SBS MVP]: "Re: SBS 2003 failed on reboot!"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 9 Feb 2005 06:50:56 -0900
The server rebuilt the active directory database from the log file due to
corruption caused by the "hard reset". If the server is performing properly
and no further errors are reported it should be fine. It would be better if
you turned of automatic updates so the server does not restart without you
being there to monitor it.
"Bryan Linton" <blinton@nospam.connellinsurance.com> wrote in message
news:efOCJ2rDFHA.936@TK2MSFTNGP12.phx.gbl...
>I was greeted at work this morning by everyone telling me the system was
>down. I looked at the monitor and saw that the SBS had apparently rebooted
>sometime during the night and was stuck at "Preparing network
>connections...." I did a hard reboot and the system came up fine, but it
>displayed an additional message prior to the appearance of the
>ctrl-alt-delete logon prompt: "The Active Directory is rebuilding
>indices...." (I think this displayed before "Preparing network
>connections...", but it may have been after). My server is now running
>normally and is apparently healthy. An examination of the event logs
>revealed that the server reboot was initiated by Automatic Updates after it
>installed critical updates downloaded during the day. Further examination
>revealed three messages were logged in the Directory Service log after the
>automatic reboot, before the system hung:
>
> Event Type: Information
> Event Source: NTDS ISAM
> Event Category: General
> Event ID: 102
> Date: 2/8/2005
> Time: 11:16:28 PM
> User: N/A
> Computer: CONNELL1
> Description:
> NTDS (556) NTDSA: The database engine started a new instance (0).
> -------------------------------
> Event Type: Information
> Event Source: NTDS General
> Event Category: Service Control
> Event ID: 1000
> Date: 2/8/2005
> Time: 11:16:43 PM
> User: NT AUTHORITY\ANONYMOUS LOGON
> Description:
> Microsoft Active Directory startup complete, version 5.2.3790.62
> ----------------------------------
> Event Type: Information
> Event Source: NTDS General
> Event Category: Service Control
> Event ID: 1394
> Date: 2/8/2005
> Time: 11:17:13 PM
> User: NT AUTHORITY\ANONYMOUS LOGON
> Description:
> Attempts to update the Active Directory database are succeeding. The Net
> Logon service has restarted.
>
> No other messages were logged until this morning when I hard rebooted the
> server. Then the following seven interesting messages were logged. (I've
> consolidated and trimmed a bit for the sake of simplicity and space, but
> all the info's there.):
>
> -----
> Event Type: Information
> Date: 2/9/2005
> Computer: OURSERVER1
> -----
>
> Event Source: NTDS ISAM
> Event Category: General
> Event ID: 102
> Time: 8:04:28 AM
> User: N/A
> Description: NTDS (556) NTDSA: The database engine started a new instance
> (0).
> ----------------------------
> Event Source: NTDS ISAM
> Event Category: Logging/Recovery
> Event ID: 300
> Time: 8:04:29 AM
> User: N/A
> Description: NTDS (556) NTDSA: The database engine is initiating recovery
> steps.
> ----------------------------
> Event Source: NTDS ISAM
> Event Category: Logging/Recovery
> Event ID: 301
> Time: 8:04:29 AM
> User: N/A
> Description: NTDS (556) NTDSA: The database engine has begun replaying
> logfile C:\WINNT\NTDS\edb.log.
> ----------------------------
> Event Source: NTDS ISAM
> Event Category: Logging/Recovery
> Event ID: 302
> Time: 8:04:29 AM
> User: N/A
> Description: NTDS (556) NTDSA: The database engine has successfully
> completed recovery steps.
> ----------------------------
> Event Source: NTDS General
> Event Category: Service Control
> Event ID: 1000
> Time: 8:04:42 AM
> User: NT AUTHORITY\ANONYMOUS LOGON
> Description: Microsoft Active Directory startup complete, version
> 5.2.3790.62
> ----------------------------
> Event Source: NTDS General
> Event Category: Service Control
> Event ID: 1394
> Time: 8:05:12 AM
> User: NT AUTHORITY\ANONYMOUS LOGON
> Description: Attempts to update the Active Directory database are
> succeeding. The Net Logon service has restarted.
> ----------------------------
> Event Source: NTDS KCC
> Event Category: Knowledge Consistency Checker
> Event ID: 1404
> Time: 8:09:48 AM
> User: NT AUTHORITY\ANONYMOUS LOGON
> Description: The local domain controller is now the intersite topology
> generator and has assumed responsibility for generating and maintaining
> intersite replication topologies for this site.
> _____________________
>
> I don't know what caused the SBS to hang on startup, and I want to make
> sure it doesn't happen again. I've tried to rundown those messages but
> haven't found anything helpful. I'm running SBS2003 with Exchange SP1.
>
> Any assistance appreciated, and as always, thanks in advance.
>
> Bryan
>
- Next message: Les Connor [SBS Community Member - SBS MVP]: "Re: SBS 2003 failed on reboot!"
- Previous message: Dave Nickason [SBS MVP]: "Re: SBS 2003 failed on reboot!"
- In reply to: Bryan Linton: "SBS 2003 failed on reboot!"
- Next in thread: Les Connor [SBS Community Member - SBS MVP]: "Re: SBS 2003 failed on reboot!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
