none
ESE Event ID 510 & ExchangeStoreDB Event ID 218

    Pregunta

  • Hi,

    We have a DELL PET110 (16GB RAM) server running Windows SBS 2011 and it is running very slowly recently especially exchange, it does also run BES Express, which I know slows down exchange but it has recently become even slower than normal.

    I have just found these events repeating in the logs:

    ESE Event ID 510

    Information Store (3676) Mailbox Database: A request to write to the file
    "D:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox
    Database\E00.log" at offset 205312 (0x0000000000032200) for 50176 (0x0000c400)
    bytes succeeded, but took an abnormally long time (31 seconds) to be serviced by
    the OS. This problem is likely due to faulty hardware. Please contact your
    hardware vendor for further assistance diagnosing the problem.

    Event 218 ExchangeStoreDB:

    At '29/03/2012 12:03:37' the copy of database
    'Mailbox Database' on this server experienced a performance problem. Failover
    returned the following error: "There is only one copy of this mailbox database
    (Mailbox Database). Automatic recovery is not available.". For more detail about
    the failure, consult the Event log on the server for other storage and
    "ExchangeStoreDb" events.

    I have run the DELL Online Diagnostics on the Storage Controller & Arrays and all tests passed OK.

    Does anybody have any ideas?


    Adam Graham

    viernes, 30 de marzo de 2012 11:08

Todas las respuestas

  • Hi,

    I suppose that you have  problems with the storage system. I came across likes problems before, and a reason was in that.


    MCTS: Microsoft Exchange Server 2007/2010 | MCSA


    viernes, 30 de marzo de 2012 11:30
  • Loads of free disk space, 100GB on C drive and 300GB on D Drive, not ahd any problems with the storage?

    Adam Graham

    viernes, 30 de marzo de 2012 11:32
  • Run Exbpa on the exchange server and if you find Disk bottle neck than you will have to talk to you the hardware vendor.

    Post the udpate.


    Gulab Prasad,
    MCITP: Exchange Server 2010 | MCITP: Exchange Server 2007
    MCITP: Lync Server 2010 | MCITP: Windows Server 2008
    My Blog | Z-Hire Employee Provisioning App

    viernes, 30 de marzo de 2012 11:37
  • Hi Gulab,

    Ran the performance test and only got a couple of warnings:

    The current processor speed on server SERVER2.sm2.local is less than the maximum possible speed. Maximum clock speed is 3100. Current clock speed is 1798.

    Circular logging for Database 'Mailbox Database' on server SERVER2 is enabled. This configuration only supports the recovery of database Mailbox Database from the last full backup.

    Network interface driver file 'c:\windows\system32\drivers\asyncmac.sys' for 'AsyncMac' on server SERVER2.sm2.local is more than two years old. Check with your vendor to find out if a newer version is available. Installed driver details: 6.1.7600.16385 - 20090714011013.139624+060

    Storage driver file 'c:\windows\system32\drivers\lsi_scsi.sys' for 'LSI Adapter, Ultra320 SCSI 2000 series, w/1020/1030' on server SERVER2.sm2.local is more than two years old. Check with your vendor to find out if a newer version is available. Installed driver details: 1.28.3.67 - 20090714024804.490463+060

    The TEMP path on server SERVER2.sm2.local is located on the same drive as the system partition. This may cause performance problems. Current TEMP path: %SystemRoot%\TEMP.

    There is only one global catalog server in the Directory Service Access (DSAccess) topology on server SERVER2. This configuration should be avoided for fault-tolerance reasons.


    Adam Graham

    viernes, 30 de marzo de 2012 12:34
  • Fix these things first, they are not looking good.
     

    The current processor speed on server SERVER2.sm2.local is less than the maximum possible speed. Maximum clock speed is 3100. Current clock speed is 1798.

    Circular logging for Database 'Mailbox Database' on server SERVER2 is enabled. This configuration only supports the recovery of database Mailbox Database from the last full backup.

    Network interface driver file 'c:\windows\system32\drivers\asyncmac.sys' for 'AsyncMac' on server SERVER2.sm2.local is more than two years old. Check with your vendor to find out if a newer version is available. Installed driver details: 6.1.7600.16385 - 20090714011013.139624+060

    Storage driver file 'c:\windows\system32\drivers\lsi_scsi.sys' for 'LSI Adapter, Ultra320 SCSI 2000 series, w/1020/1030' on server SERVER2.sm2.local is more than two years old. Check with your vendor to find out if a newer version is available. Installed driver details: 1.28.3.67 - 20090714024804.490463+060


    Gulab Prasad,
    MCITP: Exchange Server 2010 | MCITP: Exchange Server 2007
    MCITP: Lync Server 2010 | MCITP: Windows Server 2008
    My Blog | Z-Hire Employee Provisioning App

    viernes, 30 de marzo de 2012 12:39
  • OK, any idea how to fix these 2:

    The current processor speed on server SERVER2.sm2.local is less than the maximum possible speed. Maximum clock speed is 3100. Current clock speed is 1798.

    Circular logging for Database 'Mailbox Database' on server SERVER2 is enabled. This configuration only supports the recovery of database Mailbox Database from the last full backup.


    Adam Graham

    viernes, 30 de marzo de 2012 12:42
  • Also the server was only purchase and installed 9 months ago, so the drivers were fully up to date at that point? So maximum 9 months old?

    Adam Graham

    viernes, 30 de marzo de 2012 12:42
  • OK, any idea how to fix these 2:

    The current processor speed on server SERVER2.sm2.local is less than the maximum possible speed. Maximum clock speed is 3100. Current clock speed is 1798.

    Circular logging for Database 'Mailbox Database' on server SERVER2 is enabled. This configuration only supports the recovery of database Mailbox Database from the last full backup.


    Not sure about the processor, this something which is pure hardware thing.
    About the Circular logging, you can fix it by going into database properties and uncheck the Circullar logging.

    Gulab Prasad,
    MCITP: Exchange Server 2010 | MCITP: Exchange Server 2007
    MCITP: Lync Server 2010 | MCITP: Windows Server 2008
    My Blog | Z-Hire Employee Provisioning App

    viernes, 30 de marzo de 2012 12:46
  • You can check the vendor website for it.

    Gulab Prasad,
    MCITP: Exchange Server 2010 | MCITP: Exchange Server 2007
    MCITP: Lync Server 2010 | MCITP: Windows Server 2008
    My Blog | Z-Hire Employee Provisioning App

    viernes, 30 de marzo de 2012 12:46
  • Okay, disabled circular logging.

    Network Adapter is up to date: 14/06/2011        - prior to installation - ran driver update using device manager, nothing found

    Storage Controller is up to date: 26/04/2011        - prior to installation - ran driver update using device manager, nothing found

    Will speak to DELL about processor.

    When you say 'not looking good', do you mean not looking good, they should be fixed as a precaution, or not looking good your exchange server is screwed?


    Adam Graham

    viernes, 30 de marzo de 2012 12:57
  • Will speak to DELL about processor.

    Look at the BIOS setting of server to resolve it.

    MCTS: Microsoft Exchange Server 2007/2010 | MCSA

    viernes, 30 de marzo de 2012 13:03
  • Hi
       Do you have anything update on your issue?
       AS far as I know, corrupt database and hardware error will cause this kind of problem.

    Terence Yu

    TechNet Community Support

    lunes, 02 de abril de 2012 6:20
  • Hi,

    I have not been able to attend site to fix the issue with the processor yet, but I am running a full test of the storage array, as teh first completed test was OK, but the full test has now take nearly 72 hours and is only 40% complete, the HDD are only 1TB, with nearly 500GB free space, does this seem right?

    1. Do you think the processor clock running slow could cause these issues alone?

    2. Will changing the clock speed affect windows booting, drivers etc in anyway?

    3. Is there anyway i can test for a corrupt database?

    I have also noted this error:

    MSExchangeIS 10027:

    There are 5 RPC requests for the mailbox "127cd355-913c-4069-865f-b9d6d34e8022: /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=USER" on the database "08ff111b-52f1-434f-aaef-05f7aa4e3699: /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=SERVER2/cn=Microsoft Private MDB" that have taken an abnormally long time to complete. This may be indicative of performance issues with your server.


    Adam Graham

    lunes, 02 de abril de 2012 7:53
  • Facing same issue here. Cant get decent support from the storage vendor.

    Tushar.

    jueves, 05 de abril de 2012 15:46
  • For testing database corruptions, use the new-mailboxRepairRequest cmdlet against the database. Or move the mailboxes to another database and the move request will clear any corruptions.

    http://technet.microsoft.com/en-us/library/ff625226.aspx

    Tushar.

    jueves, 05 de abril de 2012 15:48