FIX: An access violation may occur when you configure SQL Server 2005 Analysis Services to use query logging

You configure Microsoft SQL Server 2005 Analysis Services to use query logging. When SQL Server 2005 Analysis Services cannot connect to the SQL Server database that you configured for query logging, an access violation may occur. Additionally, a minidump file is generated in the SQL Server 2005 Analysis Services log folder.

This problem occurs because of behavior that occurs when SQL Server 2005 Analysis Services writes query logs to the query log table. In this case, the subscriber object that is used to write the query log is null if the connection to the SQL Server database is not available.

The fix for this issue was first released in Cumulative Update 7. 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.

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

Critical information for SQL Server 2005 Analysis Services

A known issue in Cumulative Update 7 for SQL Server 2005 Analysis Services

Consider the following scenario. You install Cumulative Update 7 for SQL Server 2005 Service Pack 2 (SP2). In SQL Server Profiler, you start or stop a trace. You run a query whose execution time exceeds the value in the ForceCommitTimeout server setting. In this scenario, all the running queries on the server are cancelled.

To work around this issue, do not execute MDX queries before you start or stop a trace. 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: