Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

corruption of writing log buffer Expand / Collapse
Author
Message
Posted Tuesday, August 14, 2012 12:23 PM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 1:13 PM
Points: 774, Visits: 1,734
Hi All,

What is this error ? any idea why do we see such kind of errors?

LogWriter: Operating system error 170(The requested resource is in use.) encountered.

Error: 17053, Severity: 16, State: 1.
LogWriter: Operating system error 170(The requested resource is in use.) encountered.
Write error during log flush.
Error: 9001, Severity: 21, State: 4.
The log for database 'msdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
Database msdb was shutdown due to error 9001 in routine 'XdesRMFull::Commit'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.


Thanks in Advance.


Post #1344952
Posted Tuesday, August 14, 2012 12:29 PM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Yesterday @ 8:19 PM
Points: 23,286, Visits: 32,012
Oracle_91 (8/14/2012)
Hi All,

What is this error ? any idea why do we see such kind of errors?

LogWriter: Operating system error 170(The requested resource is in use.) encountered.

Error: 17053, Severity: 16, State: 1.
LogWriter: Operating system error 170(The requested resource is in use.) encountered.
Write error during log flush.
Error: 9001, Severity: 21, State: 4.
The log for database 'msdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
Database msdb was shutdown due to error 9001 in routine 'XdesRMFull::Commit'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.


Thanks in Advance.





And what error(s) are shown in the event log?



Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Post #1344957
Posted Tuesday, August 14, 2012 5:39 PM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 1:13 PM
Points: 774, Visits: 1,734
19019 Failover "[sqsrvres] CheckServiceAlive: Service is dead
19019 Failover "[sqsrvres] CheckServiceAlive: Service is dead
19019 Failover "[sqsrvres] OnlineThread: Error 1 bringing resource online.
19019 Failover "[sqsrvres] OnlineThread: service stopped while waiting for QP.
19019 Failover "[sqsrvres] CheckServiceAlive: Service is dead
19019 Failover "[sqsrvres] CheckServiceAlive: Service is dead
3449 Server SQL Server must shut down in order to recover a database (database ID 2). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.
9001 Server The log for database 'tempdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
17053 Server fcb::close-flush: Operating system error (null) encountered.
17053 Server LogWriter: Operating system error 170(The requested resource is in use.) encountered.
9001 Server The log for database 'msdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
9001 Server The log for database 'msdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
17053 Server LogWriter: Operating system error 170(The requested resource is in use.) encountered.
17053 Server LogWriter: Operating system error 170(The requested resource is in use.) encountered.
nt options file)
4098 None Error Initializing TSM Api, unable to verify Registry Password, see dsierror.log.
17053 Server fcb::close-flush: Operating system error (null) encountered.
17053 Server fcb::close-flush: Operating system error (null) encountered.
9001 Server The log for database 'BizTalkMsgBoxDb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
17053 Server LogWriter: Operating system error 170(The requested resource is in use.) encountered.
nt options file)
4098 None Error Initializing TSM Api, unable to verify Registry Password, see dsierror.log.
nt options file)
4098 None Error Initializing TSM Api, unable to verify Registry Password, see dsierror.log.
nt options file)
4098 None Error Initializing TSM Api, unable to verify Registry Password, see dsierror.log.
nt options file)
4098 None Error Initializing TSM Api, unable to verify Registry Password, see dsierror.log.
nt options file)
4098 None Error Initializing TSM Api, unable to verify Registry Password, see dsierror.log.
nt options file)
Post #1345089
Posted Thursday, August 23, 2012 8:21 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, July 29, 2014 9:40 AM
Points: 201, Visits: 811
From the error posted looks like you have .ldf files for tempdb, msdb and BizTalkMsgBozDB. Is the drive which held these files still online?

Got backups off those databases?

The tempdb and msdb are system databases and worse case scenario can be rebuilt, however the BizTalk DB may need some extra work but a restore would be the quickest and safest way.
Post #1349137
Posted Tuesday, June 11, 2013 11:17 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, July 16, 2014 6:25 PM
Points: 60, Visits: 248
I don't have a solution (still looking), but I do have some advice. Before you start anything as drastic as database restores, try simply restarting the server. When I've encountered this error, a restart has been sufficient--it clears whatever file handle was preventing SQL Server's access to the file.

I have not yet been able to figure out what was causing the error in the first place. Process Explorer seemed to be saying that SQL Server had the only handle to the file.



Post #1462281
Posted Tuesday, March 4, 2014 5:53 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, August 26, 2014 5:04 AM
Points: 2, Visits: 66
Investigate your SAN performance. We have experienced this exact situation on a Virtualized SQL Server where it appeared that Data, Log, TempDb and Backups were on separate LUNs, but the associated virtual disks (VMDKs) had all been placed on a single VMWare DataStore, which was actually a single LUN presented from the SAN, due to usage of EMC Storage Pools. All IO was actually going thru 1 path at VMWare Host level. Every time we'd get the OS 170 Error, without associated Disk Errors in the System Event Log (suspect due to disk.sys timeout values Registry being increased by VMWare vSCSI drivers). Fix was Storage vMotion to faster Storage Pool on SAN. (Still not happy with single DataStore though!)
Post #1547273
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse