File in Use

  • Hi Experts,

    Found this error in SQL log and Windows Event Viewer.

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

    The log for database 'tempdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

    How can i find the application that was holding the file?

    Failover occured and tempDB is workinng fine now.

  • After the fact, you don't. At the time it occurs, you could use something like Process Explorer to identify what has the file handle open.

    Make sure your antivirus is correctly configured, it's a common cause of this kind of problem.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • GilaMonster (3/11/2016)


    After the fact, you don't. At the time it occurs, you could use something like Process Explorer to identify what has the file handle open.

    Make sure your antivirus is correctly configured, it's a common cause of this kind of problem.

    Thanks Gail,

    We have given the below list for InfraStructure Team for Anti-Virus excclusion.

    SQL Server data files

    These files usually have one of the following file-name extensions:

    .mdf

    .ldf

    .ndf

    SQL Server backup files

    These files frequently have one of the following file-name extensions:

    .bak

    .trn

    Full-Text catalog files

    S1 instance: E:\System\MSSQL12.S1\MSSQL\FTData

    S2 instance: F:\System\MSSQL12.S2\MSSQL\FTData

    S3 instance: G:\System\MSSQL12.S3\MSSQL\FTData

    Trace files

    These files usually have the .trc file-name extension.

    SQL audit files

    These files have the .sqlaudit file-name extension.

    SQL query files

    These files typically have the .sql file-name extension .

    Processes to exclude from virus scanning

    SQL Server 2014

    C:\Program Files\Microsoft SQL Server\MSSQL12.S1\MSSQL\Binn\SQLServr.exe

    C:\Program Files\Microsoft SQL Server\MSSQL12.S2\MSSQL\Binn \SQLServr.exe

    C:\Program Files\Microsoft SQL Server\MSSQL12.S3\MSSQL\Binn \SQLServr.exe

    Considerations for clustering

    Please make sure Anti-Virus software is cluster aware.

    If you are running antivirus software on a cluster, make sure that you also exclude these locations from virus scanning:

    •Q:\ (Quorum drive)

    •C:\Windows\Cluster

  • GilaMonster (3/11/2016)


    After the fact, you don't. At the time it occurs, you could use something like Process Explorer to identify what has the file handle open.

    Make sure your antivirus is correctly configured, it's a common cause of this kind of problem.

    Thanks Gail.

    How to you process explorer to find the task using the file?

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply