FIX: Event ID 22 is logged in the Application log when you process an object in a database in SQL Server 2005 Analysis Services

In Microsoft SQL Server 2005 Analysis Services, the Analysis Services service stops unexpectedly when you process an object in a database. Additionally, a minidump file is generated, and an event that resembles the following is logged in the Application log:

Event ID: 22
Event Source: Analysis Service
File system error: The following error occurred during a file operation: The process cannot access the file because it is being used by another process. . (\\?\C:\Program Files\Microsoft SQL Server\MSSQL.4\OLAP\Data\Adventure Works DW.1.db\Dim Organization.0.dim\21.Organization Name.asstore).

This issue occurs when the Analysis Services service tries to delete a file during the final phase of the processing operation. However, the server cannot delete the file because the file is unexpectedly locked by another application. Frequently, the other application is antivirus software or backup software.

The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: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: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.

Warning This workaround may make a computer or a network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.

To work around this issue, do not access the files in the Analysis Services directories when you process an object. For example, avoid running backup operations on the files in the Analysis Services directories when you process an object. Additionally, we recommend that you exclude the following Analysis Services directory from real-time scanning in your antivirus software:Note MSSQL.x is a placeholder for the instance ID of the instance of Analysis Services.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: 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:For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site: 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:For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: