Re: SBS Randomly Shuts Down!

Check Automatic update settings, We had this the other day after we updates some WSUS info.

<mbuck@xxxxxxxxxxxxxxxx> wrote in message news:04831bb1-82d6-4457-ad08-c37e48487508@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,

I've now experienced this problem twice on the same system and I'm
seriously running out of ideas. We are running a Dell Poweredge with
Windows SBS 2003 R2 (Service Pack 2).

I get a call from the customer saying "everything is down". On
inspection the server has shut itself off! Pressing the power button
obviously brings it back up. During an investigation we deduce the
following:

*There has been no interuptions in power supply and the UPS logs
indicate everything has been fine.
*There is no shutdown notice or unplanned shutdown message.

In the event logs we find the following:

---
Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 1/12/2009
Time: 3:57:17 PM
User: N/A
Computer: SERVER
Description:
LDAP Bind was unsuccessful on directory SERVER.xxx.local for
distinguished name ''. Directory returned error:[0x34]
Unavailable.

---

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2104
Date: 1/12/2009
Time: 3:57:17 PM
User: N/A
Computer: SERVER
Description:
Process INETINFO.EXE (PID=1768). All the DS Servers in domain are not
responding.

---

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Date: 1/12/2009
Time: 3:57:17 PM
User: N/A
Computer: SERVER
Description:
Process MAD.EXE (PID=2676). All Domain Controller Servers in use are
not responding:
SERVER.xxx.local

---

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 1/12/2009
Time: 3:57:23 PM
User: N/A
Computer: SERVER
Description:
LDAP Bind was unsuccessful on directory SERVER.xxx.local for
distinguished name ''. Directory returned error:[0x51] Server
Down.

---

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 1/12/2009
Time: 3:57:24 PM
User: N/A
Computer: SERVER
Description:
The Win32 API call 'DsGetDCNameW' returned error code [0x862] The
specified component could not be found in the configuration
information. The service could not be initialized. Make sure that
the operating system was installed properly.

---

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2103
Date: 1/12/2009
Time: 3:57:27 PM
User: N/A
Computer: SERVER
Description:
Process MAD.EXE (PID=2676). All Global Catalog Servers in use are not
responding:
SERVER.xxx.local

---

Then nothing. Just a gap in the event log between the time when it
shuts down and starts back up. In the security audit log, strangely I
find the following at exactly the time immediately before shutdown:

Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 537
Date: 1/12/2009
Time: 3:57:30 PM
User: NT AUTHORITY\SYSTEM
Computer: SERVER
Description:
Logon Failure:
Reason: An error occurred during logon
User Name: SERVER$
Domain: xxx.LOCAL
Logon Type: 3
Logon Process: Kerberos
Authentication Package: Kerberos
Workstation Name: -
Status code: 0xC00000DC
Substatus code: 0x0
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -

---

Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 537
Date: 1/12/2009
Time: 3:57:37 PM
User: NT AUTHORITY\SYSTEM
Computer: SERVER
Description:
Logon Failure:
Reason: An error occurred during logon
User Name: TERMINAL1$
Domain: xxx.LOCAL
Logon Type: 3
Logon Process: Kerberos
Authentication Package: Kerberos
Workstation Name: -
Status code: 0xC00000DC
Substatus code: 0x0
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: 192.168.16.26
Source Port: 0

TERMINAL1 is one of the client machines joined to the domain locally.

Any assistance much appreciated.





.

Loading