September 14, 2009 at 3:15 pm
Hi,
We have K2 databases on SQL server 2005. I found below dump in error log. Could you please tell me what this error referring to?
2009-09-02 20:59:05.36spid2s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\EventBusScheduler_log.LDF] in database [EventBusScheduler] (11). The OS file handle is 0x000000000000080C. The offset of the latest long I/O is: 0x000000000ae000
2009-09-02 20:59:15.36 spid2s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\K2Server_log.LDF] in database [K2Server] (12). The OS file handle is 0x000000000000083C. The offset of the latest long I/O is: 0x0000000023ac00
2009-09-02 21:00:53.22 Server Using 'dbghelp.dll' version '4.0.5'
2009-09-02 21:00:53.32 Server ***Unable to get thread context - no pss
2009-09-02 21:00:53.32 Server * *******************************************************************************
2009-09-02 21:00:53.32 Server *
2009-09-02 21:00:53.32 Server * BEGIN STACK DUMP:
2009-09-02 21:00:53.32 Server * 08/12/09 21:00:53 spid 0
2009-09-02 21:00:53.32 Server *
2009-09-02 21:00:53.32 Server * Non-yielding Scheduler
2009-09-02 21:00:53.33 Server *
2009-09-02 21:00:53.33 Server * *******************************************************************************
2009-09-02 21:00:53.33 Server Stack Signature for the dump is 0x000000000000038A
2009-09-02 21:00:55.78 Server External dump process return code 0x20000001.
External dump process returned no errors.
September 14, 2009 at 3:28 pm
Could be memory and it could be because the databases are on C:
Can you move the log files to another drive? What is your total server memory? Also how much memory is allocated to SQL Server?
September 15, 2009 at 1:03 am
Its completely a development server & we just have 2GB of RAM.
We have SQL Server 2005, X64 developer edition.
Please advice me
September 15, 2009 at 1:28 am
gmamata7 (9/14/2009)
Hi,We have K2 databases on SQL server 2005. I found below dump in error log. Could you please tell me what this error referring to?
2009-09-02 20:59:05.36spid2s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\EventBusScheduler_log.LDF] in database [EventBusScheduler] (11). The OS file handle is 0x000000000000080C. The offset of the latest long I/O is: 0x000000000ae000
2009-09-02 20:59:15.36 spid2s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\K2Server_log.LDF] in database [K2Server] (12). The OS file handle is 0x000000000000083C. The offset of the latest long I/O is: 0x0000000023ac00
2009-09-02 21:00:53.22 Server Using 'dbghelp.dll' version '4.0.5'
2009-09-02 21:00:53.32 Server ***Unable to get thread context - no pss
2009-09-02 21:00:53.32 Server * *******************************************************************************
2009-09-02 21:00:53.32 Server *
2009-09-02 21:00:53.32 Server * BEGIN STACK DUMP:
2009-09-02 21:00:53.32 Server * 08/12/09 21:00:53 spid 0
2009-09-02 21:00:53.32 Server *
2009-09-02 21:00:53.32 Server * Non-yielding Scheduler
2009-09-02 21:00:53.33 Server *
2009-09-02 21:00:53.33 Server * *******************************************************************************
2009-09-02 21:00:53.33 Server Stack Signature for the dump is 0x000000000000038A
2009-09-02 21:00:55.78 Server External dump process return code 0x20000001.
External dump process returned no errors.
It means that a request for I/O took longer than 15 seconds to complete, if you get this constantly, this can mean you need to look at what is causing it, and make changes. index maintenance jobs can generate this error, if they are on big tables and they are taking a long time to complete. if this only happens once in a blue moon, you can ignore it. Network glitches can also generate this error. you could always try moving the files on to dedicated drive, in theory you shouldnt have database files on your local c: drive, the local subsystem might be not be good enough to handle the I/O throughput.
--------------------------------------------------------------------------------------
[highlight]Recommended Articles on How to help us help you and[/highlight]
[highlight]solve commonly asked questions[/highlight]
Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
Managing Transaction Logs by Gail Shaw[/url]
How to post Performance problems by Gail Shaw[/url]
Help, my database is corrupt. Now what? by Gail Shaw[/url]
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply