What type of error could be this?

Hi... I have a Proliant DL 380 server with 2GB of rams. Most common configured mailbox server with 500 mailboxes divided to two databases. The problem is that this is the second time, when it performs and unexpected reboot...
Fortunatley or not these reboots were during off the working hours at the weekend, and not database maintenance time...

Strange that it seems that the databases were not corrupted... (if there would be a power outage, or a blue death, it should something happens with the databases, or nor?)

And there is nothing on the events what might help me to figure out if there is the problem with the hardware or the software...

Here are the events what I found:

System>

System Information Agent: Health: Post Errors were detected.  One or more Power-On-Self-Test errors were detected during server startup.
[SNMP TRAP: 6027 in CPQHLTH.MIB]

--

The previous system shutdown at 7:50:58 PM on 5/13/2006 was unexpected.

Application>

The MTA is running recovery on the internal message database because the MTA was not shut down cleanly. This operation may take some time.  Status updates will be written to the Windows 2000 Event Log. [DB Server MAIN BASE 1 0] (14)

Information Store (2628) SG1-XXXXXXC05: The database engine started a new instance (0).

Information Store (2628) SG1-XXXXXXC05: The database engine is initiating recovery steps.

Information Store (2628) SG1-XXXXXXC05: The database engine has begun replaying logfile E:\Program Files\Exchsrvr\mdbdata\E003FE70.log.
The MTA database recovery operation has completed successfully. Recovery details can be found in the file: G:\Program Files\Exchsrvr\mtadata\.\MTACHECK.OUT\MTACHECK.LOG. [DB Server MAIN BASE 1 67] (14)

MTACHECK.LOG>


Checking queue XAPIWRKQ (id 01000020)

Checking queue OOFINFOQ (id 01000025)

Checking queue REFDATQ (id 01000026)

Checking queue MTAWORKQ (id 01000028)

Checking queue /O=KPMG/OU=HU/CN=CONFIGURATION/CN=CONNECTIONS/CN=SMTP (XXXXXXC05)/CN={B20718ED-856F-4B28-AF75-8C688033C6C5} (id 0100002B)

Checking queue /O=KPMG/OU=HU/CN=CONFIGURATION/CN=CONNECTIONS/CN=SMTP (XXXXXXC05)/CN={C1E9553F-A247-4D35-B74B-A6E40D413A26} (id 01000031)

Starting object integrity checks
  Checking object 03000002 - OK, on queue 01000026
  Checking object 0A000003 - OK, on queue 01000020
  Checking object 0B000004 - OK, on queue 01000020
  Checking object 0B000005 - OK, on queue 01000020
  Checking object 0C000006 - OK, on queue 01000020
  Checking object 0C000007 - OK, on queue 01000020
  Checking object 06000008 - OK, on queue 01000020
  Checking object 06000009 - OK, on queue 01000020
  Checking object 0600000A - OK, on queue 01000020
  Checking object 0600000B - OK, on queue 01000020
  Checking object 0600000C - OK, on queue 01000020
  Checking object 0600000D - OK, on queue 01000020
  Checking object 0600000E - OK, on queue 01000020
  Checking object 0600000F - OK, on queue 01000020
  Checking object 06000010 - OK, on queue 01000020
  Checking object 06000011 - OK, on queue 01000020
  Checking object 06000012 - OK, on queue 01000020
  Checking object 06000013 - OK, on queue 01000020
  Checking object 06000014 - OK, on queue 01000020
  Checking object 06000015 - OK, on queue 01000020
  Checking object 09000016 - OK, on queue 01000020
  Checking object 09000017 - OK, on queue 01000020
  Checking object 09000018 - OK, on queue 01000020
  Checking object 09000019 - OK, on queue 01000020
  Checking object 0900001A - OK, on queue 01000020
  Checking object 0900001B - OK, on queue 01000020
  Checking object 0600001C - OK, on queue 01000020
  Checking object 0600001D - OK, on queue 01000020
  Checking object 0600001E - OK, on queue 01000020
  Checking object 0600001F - OK, on queue 01000020
  Checking object 06000021 - OK, on queue 01000020
  Checking object 06000022 - OK, on queue 01000020
  Checking object 06000023 - OK, on queue 01000025
  Checking object 09000024 - OK, on queue 01000025


Starting garbage collection of orphaned objects
Deleted G:\Program Files\Exchsrvr\mtadata\.\DB000027.DAT successfully.

Database clean, no errors detected.


The Microsoft Exchange Information Store has started. Service startup complete, version 6.5 (build 7226.3).

Sooo... Is there any ideas? There were no memory leak, there were no additional hardware added...

Thank you...

Domokos
domokosvargaSenior IT ManagerAsked:
Who is Participating?
 
rhandelsCommented:
Hi,

Microsoft really worked hard on finding a solution for corrupted databases and they found one.. ;) With Exchange 2003, the database is not necesarrily corrupted.. The chekc though is quite common and nothing to worry about..

The thing you nee to worry about is why this server is shutting down unexpectedly.. Do you have the error code for the BSOD?? Normally you can find some extra info inthere..

By the looks of it, i woul say you're having a hardware issue.. If you have a testlab, i would suggest creating an image of the server and "reïnstall" the image on another DL380 testserver. This way you can count out the possibly of a hardware error (or actually find out it is a hardware error).

These problems are always very difficult to tackle... But to conclude things, i would go for the hardware error...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.