December 24, 2008 at 3:42 am
Hi all
I have some problems with one environment..
It was a virtual cluster active/passive with 2 virtual nodes and virtual disk in procution and onde node is offline(i know te very inadvisable but ....)
Yesterday i see this error in SQLERRORLOG
DESCRIPTION: Error: 823, Severity: 24, State: 2
I/O error 170(The requested resource is in use.) detected during read at offset 0x00000017420000 in file 'S:\Microsoft SQL Server\MSSQL\Data\XXXXXX_Data.MDF'.
I think in a first moment is anti virus .i think it was try to read de mdf so I suggest disabling it.
But searching in web i think some articles about error cluster.
is this happening one failover ? and because th other node is offline this message shows up ? or can be another problem....i really think it was related to resources in cluster but i dont know where i begin to search
Thanks all
December 28, 2008 at 11:30 am
This link may be helpful for you.
December 28, 2008 at 6:04 pm
December 28, 2008 at 11:21 pm
Laerte POltronieri Junior (12/24/2008)
Hi allI have some problems with one environment..
It was a virtual cluster active/passive with 2 virtual nodes and virtual disk in procution and onde node is offline(i know te very inadvisable but ....)
Yesterday i see this error in SQLERRORLOG
DESCRIPTION: Error: 823, Severity: 24, State: 2
I/O error 170(The requested resource is in use.) detected during read at offset 0x00000017420000 in file 'S:\Microsoft SQL Server\MSSQL\Data\XXXXXX_Data.MDF'.
I think in a first moment is anti virus .i think it was try to read de mdf so I suggest disabling it.
But searching in web i think some articles about error cluster.
is this happening one failover ? and because th other node is offline this message shows up ? or can be another problem....i really think it was related to resources in cluster but i dont know where i begin to search
Thanks all
[font="Verdana"]We have had a similar problem with one of our clusters.
Let's just take the error message and start from there:
If you receive 823 error message, it might indicate that Microsoft SQL Server 2000 has detected hardware or system problems when it was reading from or writing to database files and could lead database to inconsistent state. Data Corruption could occur if Write Caching is enabled without Battery Backups on server. For more information on 823 error messages, please refer >> http://support.microsoft.com/kb/828339.
Now, I/O error 170 (requested resource is in use): For this, if you feel that the mdf file is in use; download handle >>http://technet.microsoft.com/en-us/sysinternals/bb896655.aspx and search for handles on the mdf. You, can do this in one of two ways:
1. Handle -U [partial filename or search pattern] -> Shows the owning user name when searching for handles. ex: Handle -U dbname.mdf
2. Handle -P [partial Process name or search pattern]-> Instead of examining all the handles in the system, this parameter narrows Handle's scan to those processes that begin with the name process. Thus: handle -p explorer
If you find that it is the aniti-virus; that is one holding the resources then:
1. Make sure that all the folders that SQl Server uses are in the Antivirus's exclusion list.
2. Make sure that antivirus, does not scan any of the cluster resources.
For more information, refer to the following KB articles:
Article1:
http://support.microsoft.com/kb/250355
Here is a quote from the above KB article:
Antivirus software may cause problems with Cluster services, including issues with failing over resources such as physical disks.
Article2:
http://support.microsoft.com/kb/309422
Hope This Helps 🙂
Regards,
[/font]
December 29, 2008 at 3:46 am
February 7, 2018 at 9:03 am
I too have gotten this error
August 20, 2018 at 12:08 am
Hi,
This usually happens due to some of the reasons: if there is a problem in hardware or if there is filter driver intervention in the IO process. In order to fix it read more: https://blogs.msdn.microsoft.com/sqlblog/2006/09/17/sql-io-error-message-and-its-resolution/
http://www.databasefilerecovery.com/ms-sql-database-recovery.html
Thanks
December 19, 2018 at 12:09 am
The error occurs due to many reasons like defects in hardware, virus attack, or re-installation in SQL Server. You can run DBCC CHECKDB to determine the cause of the error. This will help you out:
https://www.sqlrecoverytool.com/fix-sql-server-fatal-error-823.html
June 14, 2021 at 9:04 am
this error means that some other process put a lock on a database file (or other related SQL Server files as well, i.e. log files, etc.) and SQL Server cannot access it in order to write in it. This is an unpleasant situation because many times, at a first look, you don’t identify something wrong but the problem persists!
Here’s what you can try for resolving the error:
– Check via Windows Resource Monitor – overview – disk activity to see if any database/log files are used by any other activity than SQL Server
– Use Sysinternals “Handle” tool to see if there are any other handles on the file rather than SQL Server itself
– Check if antivirus is using the specific file thus keeping it locked
SQL Database Recovery Expert 🙂
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply