Post reply

Backup plan failing intermittently - The process cannot access file...while attempting CreateFile

  • April 12, 2006 at 8:54 am

    #168630

    I have a maintenance plan set up to do a full backup on a daily schedule. The plan has been failing intermittently. Looking at the event log I see this error which seems related to a full text catalog "KBase" in the database:

    The operating system returned the error

    '32(The process cannot access the file because it is being used by another process.)'

    while attempting 'CreateFile' on 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\FTData\KBASE0000\SQL.HDR'

    at 'fulltext.cpp'(529).

    Any ideas what's causing this and how to resolve?

    -Phil

  • April 13, 2006 at 12:09 pm

    #632484

    The only time I see that error is when our tape backup is running on a disk file that SQL Server is trying to write a backup to.  I usually add a few "re-tries" to the SQL job step.  Other than that, if you have Anti-Virus software, it's possible that the backup file is being scanned.  You may want to look at the NT Event logs to see what is going on.

  • May 24, 2006 at 7:00 am

    #639748

    I am currently having the same problem. Out of curiosity, are you using Full Text Search? The problem started happening once I started using FTS.

  • May 24, 2006 at 7:50 am

    #639772

    Yes, we are using full text search.

  • August 7, 2006 at 1:34 pm

    #653720

    Yes were are having the same exact problem too... the problem seem to show itself when we moved to SQL 2005.  In SQL 2000... we used FTS with no issues.  Here we are getting intermittant successes on the database backups with no apparent reason for failure other than what has been stated.  Nothing is scheduled even remotely close to this backup job.

     

  • November 17, 2007 at 9:47 am

    #752063

    I am seeing the same error on my system. I am pretty sure it is because I have a full backup (every evening starting at 8:00 PM) and a log backup (Every 3 hours) running at the same time.

    It seems to be related to this: http://support.microsoft.com/kb/929404

    I will try this hotfix next week on my system.

  • February 7, 2008 at 3:49 am

    #775926

    Am getting the same problem, where it says that the backup file can not be accessed as it is been used by another process.....does anyone know how i can find what process is causing the lock? the NT event log does not say anything.

  • February 7, 2008 at 5:36 am

    #775956

    Look up the Processmon utility from Microsoft (it's free) and it will help determine file usage.

    http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

    Toni

  • September 25, 2008 at 8:52 am

    #877069

    I'm getting the same problem too:

    The operating system returned the error '32(The process cannot access the file because it is being used by another process.)' while attempting 'CreateFile' on 'T:\MSSQL\MSSQL.5\MSSQL\USERDATA\Data\monitor.mdf'.

    The strange thing is that the file that is referenced to in the message, is a file belonging to a different database than the database that I'm trying to backup.

  • September 25, 2008 at 12:18 pm

    #877258

    if you are not using Microsoft Indexing Service then stop it from the services panel

  • September 26, 2008 at 12:56 am

    #877449

    Indexing service was not it.

    Could it be that SQL Server is thrown off by the fact that the files for the full-text catalog are in the same folder as the data-file of the database?

  • September 26, 2008 at 5:25 am

    #877556

    Found the problem !!!!!

    If the files of your full-text catalog are in the same folder as your database's primary data file, this error occurs.

    To solve it, move the location of your full-text catalog.

Viewing 12 posts - 1 through 11 (of 11 total)

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