a70a0688   
   From: esquel@sommarskog.se   
      
   Admin Matt (admin.matthew@gmail.com) writes:   
   > The error logs show that the LDF file can't be accessed because it is   
   > being used by another process (event id: 17207). This process is no   
   > longer using the file by the time we can check out the problem. The   
   > event id always appears at night. We are now having the antivirus   
   > avoid scanning the LDF and MDF files and also we are turning off the   
   > Backup Exec software for now with the Data folder even though the   
   > errors normally appear before the backup even starts. Finally we are   
   > setting the problem database Auto Close option to False. I will post   
   > the results. It will probably take more than a week to know if the   
   > issue is actually fixed.   
      
   I've no idea what might be looking at your log file, but turning off   
   autoclose should learn them to keep out.   
      
   Not that it is relevant to your, but I had some crappy backup software   
   running on my machine at home; it was something I got with the NAS. Fairly   
   often I would get errors about locked files. And this happened even in   
   directories that were not included in the backup scheme. Eventually I   
   got myself together and uninstalled.   
      
   --   
   Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
      
   Links for SQL Server Books Online:   
   SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx   
   SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)