Operating System Error 170(Requested Resource is in use)
It might happen at some point, under certain circumstances, to get the above error message on your SQL Server environment.
Explaining the Error Message
The above 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!
So, what you can do? You have a situation where SQL Server reports as a critical error that it cannot write on one or more of its hosted databases.
You hope that you can resolve this issue fast and without any downtime.
It did happen to me in the past as well, so I would like to share some tips with you, which you might find useful for resolving this issue.
How to Resolve the Requested Resource is in Use Error
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
Example of using Handle.exe:
Hope this helps!
Learn more tips like this! Get the Online Course!
Check our online course titled “Essential SQL Server Administration Tips” (special limited-time discount included in link).
Learn essential hands-on SQL Server Administration tips on SQL Server maintenance, security, performance, integration, error handling and more. Many live demonstrations and downloadable resources included!
Featured Online Courses:
- Boost SQL Server Database Performance with In-Memory OLTP
- Essential SQL Server Administration Tips
- SQL Server Fundamentals (SQL Database for Beginners)
- The Philosophy and Fundamentals of Computer Programming
- Introduction to Data Science and SQL Server Machine Learning
- Introduction to Azure SQL Database
- SQL Server 2019: What’s New
- Entity Framework: Getting Started (Ultimate Beginners Guide)
- How to Import and Export Data in SQL Server
- Get Started with SQL Server in 30 Minutes
- A Guide on How to Start and Monetize a Successful Blog
Here are some other SQL Server troubleshooting articles which you can check out for finding solutions to related technical issues you might encounter:
- An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database
- A network-related or instance-specific error occurred while establishing a connection to SQL Server
- SQLServerAgent could not be started (reason: Unable to connect to server ‘(local)’; SQLServerAgent cannot start)
- There is no SQL Server Failover Cluster Available to Join
- Resolving the Error Message: Rule “KB2919355 Installation” failed
Reference: SQLNetHub.com (https://www.sqlnethub.com)
Rate this article:
Subscribe to our newsletter and never miss a thing!
Artemakis Artemiou is a Senior SQL Server Architect, Author, and a 9 Times Microsoft Data Platform MVP (2009-2018). He has over 15 years of experience in the IT industry in various roles. Artemakis is the founder of SQLNetHub and TechHowTos.com. Artemakis is the creator of the well-known software tools Snippets Generator and DBA Security Advisor. Also, he is the author of many eBooks on SQL Server. Artemakis currently serves as the President of the Cyprus .NET User Group (CDNUG) and the International .NET Association Country Leader for Cyprus (INETA).