FIX: You receive an error message that the file is being used by another process when you try to rename or move an output file from a job in SQL Server Agent in SQL Server 2005

Article ID: 957357 - View products that this article applies to.
Bug #: 50003375 (SQL Hotfix)
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.
Expand all | Collapse all

On This Page

SYMPTOMS

In Microsoft SQL Server 2005, you configure SQL Server Agent (SQLAgent90.exe) by using a job that has an output file. When you try to rename or move the output file, the file cannot be moved or renamed. Additionally, you receive an error message that the file is being used by another process.
Back to the top | Give Feedback

CAUSE

This problem may occur when another job in SQL Server Agent has a file handle that is open to the output file. This option is set on the Advanced tab of a job step. Jobs that create child processes, such as Distrib.exe or Dtexec.exe, can hold a file handle open to the output file for the other job that has the output file. When you try to rename the output file, the file cannot be renamed because the output file is being used by a child process.
Back to the top | Give Feedback

RESOLUTION

Cumulative update information

SQL Server 2005 Service Pack 2

Important You must use this fix if you are running SQL Server 2005 Service Pack 2.

The fix for this issue was first released in Cumulative Update 10 for SQL Server 2005 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
956854
(http://support.microsoft.com/kb/956854/LN/ )
Cumulative update package 10 for SQL Server 2005 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
937137
(http://support.microsoft.com/kb/937137/LN/ )
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2005 Service Pack 3

Important You must use this fix if you are running SQL Server 2005 Service Pack 3.

The fix for this issue was also later released in Cumulative Update 1 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
959195
(http://support.microsoft.com/kb/959195/LN/ )
Cumulative update package 1 for SQL Server 2005 Service Pack 3
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
960598
(http://support.microsoft.com/kb/960598/LN/ )
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Back to the top | Give Feedback

WORKAROUND

To work around this problem, use a tool such as Process Explorer to determine the process or job that has a file handle to the output file. Then, stop the process or job to release the file handle to the output file. After you rename the output file, restart the job.
Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

MORE INFORMATION

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756
(http://support.microsoft.com/kb/322756/ )
How to back up and restore the registry in Windows
If you have to restore the previous behavior that is mentioned in the "Symptoms" section, add the ChildProcessesInheritAgentLogFileHandles DWORD value to the registry, and then set the value to 0. To do this, follow these steps:
  1. Click Start, click Run, type regedit in the Open box, and then click OK.
  2. Locate and then click to select the following registry key:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\MSSQL.1\SQLServerAgent
  3. After you select the key in step 2, point to New on the Edit menu, and then click DWORD Value.
  4. Type ChildProcessesInheritAgentLogFileHandles, and then press ENTER.
  5. Right-click ChildProcessesInheritAgentLogFileHandles, and then click Modify.
  6. In the Value data box, type 0, and then click OK.
  7. On the File menu, click Exit to exit Registry Editor.
Back to the top | Give Feedback

REFERENCES

For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897
(http://support.microsoft.com/kb/935897/ )
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499
(http://support.microsoft.com/kb/822499/ )
New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/ )
Description of the standard terminology that is used to describe Microsoft software updates
Back to the top | Give Feedback

Properties

Article ID: 957357 - Last Review: December 20, 2008 - Revision: 6.0
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Workgroup Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
Keywords: 
kbautohotfix kbbug kbexpertiseadvanced kbqfe kbfix KB957357
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top