Exchange 2010 - Event ID 118&510
Hi I am hoping someone can help me with the below issue I am having on Exchange 2010. Every day at 6pm I am getting Event IDs 118 & 510, we have staff who work at 6pm plus and they are experiencing severe performance issues and disconnections around these times. There are TWO Exchange 2010 servers in a Clustered environment running on a Windows Server 2008 R2 Enterprise, each server has 6.00GB RAM and has a Intel Xeon 3.10 Ghz processor and is running in a Virtual Environment on Hyper-V. Please find the below Events: Log Name: Application Source: ExchangeStoreDB Date: 01/10/2012 18:09:31 Event ID: 118 Task Category: Database recovery Level: Error Keywords: Classic User: N/A Computer: XXXXXX.XXXXXXX.local Description: At '01/10/2012 18:09:29' the copy of database 'XXXXXXX' on this server appears to be experiencing performance issues, possibly as a result of storage failure. Consult the event log on the server for other storage and "ExchangeStoreDb" events for more specific information about the failure. Recovery was not attempted. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="ExchangeStoreDB" /> <EventID Qualifiers="49156">118</EventID> <Level>2</Level> <Task>1</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2012-10-01T17:09:31.000000000Z" /> <EventRecordID>80752</EventRecordID> <Channel>Application</Channel> <Computer>XXXXXX.XXXXXXX.local</Computer> <Security /> </System> <EventData> <Data>XXXXXXXX</Data> <Data>fb4892ed-ea02-4677-a22f-37db285aab2b</Data> <Data>Ese</Data> <Data>Performance</Data> <Data>XXXXXX-02</Data> <Data> </Data> <Data> </Data> <Data>01/10/2012 18:09:29</Data> <Data>Write</Data> <Data>L:\XXXXXXXX\E00.log</Data> <Data>691712</Data> <Data>512</Data> </EventData> </Event> Log Name: Application Source: ESE Date: 01/10/2012 18:09:30 Event ID: 510 Task Category: Performance Level: Warning Keywords: Classic User: N/A Computer: XXXXXX.XXXXXX.local Description: Information Store (3556) XXXXXXXX: A request to write to the file "E:\Databases\XXXXXXX.edb" at offset 40205582336 (0x000000095c708000) for 393216 (0x00060000) bytes succeeded, but took an abnormally long time (46 seconds) to be serviced by the OS. In addition, 1 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 86544 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. For more information, click http://www.microsoft.com/contentredirect.asp. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="ESE" /> <EventID Qualifiers="0">510</EventID> <Level>3</Level> <Task>7</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2012-10-01T17:09:30.000000000Z" /> <EventRecordID>80750</EventRecordID> <Channel>Application</Channel> <Computer>XXXXXXX.XXXXXXX.local</Computer> <Security /> </System> <EventData> <Data>Information Store</Data> <Data>3556</Data> <Data>XXXXXXX: </Data> <Data>E:\Databases\XXXXXXXX.edb</Data> <Data>40205582336 (0x000000095c708000)</Data> <Data>393216 (0x00060000)</Data> <Data>46</Data> <Data>1</Data> <Data>86544</Data> </EventData> </Event> We have already increased the memory, rebooted the server, checked the status of the Databases (they don't appear to be corrupt). If you require any further info then please don't hesitate to ask and any help provide would be greatly appreciated, this has been a long outstanding issue and needs resolving. Many Thanks David Harrison
October 2nd, 2012 5:13am

Hello, For event id 510, this problem may be caused by faulty hardware. This problem may also be caused if the server or disk subsystem is not correctly configuration. There are few information on the event id 510. I search an article on the description for event id 510 for your reference. Event 507 Have you used Performance Troubleshooter in the Toolbox to seek the performance related issue? Understanding Database and Log Performance Factors Here is the similar thread for your reference. http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/9072ccef-b2d8-45f2-a40d-cb3ebf188a0c Cara Chen TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
October 11th, 2012 3:23am

Hi, This does sound as if you have a storage issue. Is the Exchange storage SAN based? If yes what else is using the same SAN (and doing something special at that time)? Are you running backup at 6 pm ? Leif
October 26th, 2012 6:57am

Hi Leif Thanks for replying so quick. Running in a Hyper-V environment the servers are all running with external storage with other VM servers running on it, but the Exchange DBs are running on a virtual hard disk rather than directly on the SAN......hope that makes sense. The SAN has already been checked and isn't running any tasks around that time. Many Thanks David
Free Windows Admin Tool Kit Click here and download it now
October 26th, 2012 7:15am

Hi Cara Thanks for the response. We have decided to build a new VM with a new DB and migrate the users to that server. Thanks for your help. Thanks David
October 27th, 2012 3:15am

Hello, For event id 510, this problem may be caused by faulty hardware. This problem may also be caused if the server or disk subsystem is not correctly configuration. There are few information on the event id 510. I search an article on the description for event id 510 for your reference. Event 507 Have you used Performance Troubleshooter in the Toolbox to seek the performance related issue? Understanding Database and Log Performance Factors Here is the similar thread for your reference. http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/9072ccef-b2d8-45f2-a40d-cb3ebf188a0c Cara Chen TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
October 27th, 2012 3:22am

Any help that anyone can provide would very useful. Many Thanks David Harrison
October 27th, 2012 6:23am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics