August 14, 2012 at 12:23 pm
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.
August 14, 2012 at 12:29 pm
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?
August 14, 2012 at 5:39 pm
19019Failover"[sqsrvres] CheckServiceAlive: Service is dead
19019Failover"[sqsrvres] CheckServiceAlive: Service is dead
19019Failover"[sqsrvres] OnlineThread: Error 1 bringing resource online.
19019Failover"[sqsrvres] OnlineThread: service stopped while waiting for QP.
19019Failover"[sqsrvres] CheckServiceAlive: Service is dead
19019Failover"[sqsrvres] CheckServiceAlive: Service is dead
3449ServerSQL 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.
9001ServerThe log for database 'tempdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
17053Serverfcb::close-flush: Operating system error (null) encountered.
17053ServerLogWriter: Operating system error 170(The requested resource is in use.) encountered.
9001ServerThe log for database 'msdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
9001ServerThe log for database 'msdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
17053ServerLogWriter: Operating system error 170(The requested resource is in use.) encountered.
17053ServerLogWriter: Operating system error 170(The requested resource is in use.) encountered.
nt options file)
4098NoneError Initializing TSM Api, unable to verify Registry Password, see dsierror.log.
17053Serverfcb::close-flush: Operating system error (null) encountered.
17053Serverfcb::close-flush: Operating system error (null) encountered.
9001ServerThe log for database 'BizTalkMsgBoxDb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
17053ServerLogWriter: Operating system error 170(The requested resource is in use.) encountered.
nt options file)
4098NoneError Initializing TSM Api, unable to verify Registry Password, see dsierror.log.
nt options file)
4098NoneError Initializing TSM Api, unable to verify Registry Password, see dsierror.log.
nt options file)
4098NoneError Initializing TSM Api, unable to verify Registry Password, see dsierror.log.
nt options file)
4098NoneError Initializing TSM Api, unable to verify Registry Password, see dsierror.log.
nt options file)
4098NoneError Initializing TSM Api, unable to verify Registry Password, see dsierror.log.
nt options file)
August 23, 2012 at 8:21 am
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.
June 11, 2013 at 11:17 am
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.
March 4, 2014 at 5:53 am
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!)
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply