FIX: Error message when you execute an MDX query that calls a VBA function in SQL Server 2005 Service Pack 1: "PFE_ASSEMBLY_NOT_SAFETOPREPARE" (919956)


The information in this article applies to:

  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium Based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems Community Technology Preview
Bug #: 783 (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.

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by this hotfix package
  • The prerequisites for installing the hotfix package
  • Information about whether you must restart the computer after you install the hotfix package
  • Information about whether you must make any registry changes
  • The files that are contained in the hotfix package

SYMPTOMS

When you execute a Multidimensional Expressions (MDX) query that calls a Microsoft Visual Basic for Applications (VBA) function in Microsoft SQL Server 2005 Service Pack 1 (SP1), the query may fail, and you may receive a "PFE_ASSEMBLY_NOT_SAFETOPREPARE" error message. This problem occurs when the MDX query calls a VBA function from a linked server query.

The query executes correctly if the following conditions are true:
  • You execute the same query directly.
  • You are connected to SQL Server 2005 Analysis Services (SSAS).

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2005 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have Microsoft SQL Server 2005 Service Pack 1 (SP1) installed to apply this hotfix.

For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005

Restart information

You must restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
File nameFile versionFile sizeDateTimePlatformLCID
microsoft.sqlserver.mgdsqldumper.dll2005.90.2164.07555214-Jun-200620:29x861033
microsoft.sqlserver.sqlenum.dll9.0.2164.090806414-Jun-200620:32x860
msadomdx.dll9.0.2164.050256014-Jun-200620:31x861033
msmdlocal.dll9.0.2164.01566185614-Jun-200620:33x861033
msmdsrv.exe9.0.2164.01463478414-Jun-200620:33x861033
msmgdsrv.dll9.0.2164.0594819214-Jun-200620:33x861033

STATUS

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

MORE INFORMATION

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

REFERENCES

For more information about how to use MDX, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn2.microsoft.com/en-us/library/ms145506.aspx

For more information about how to use SSAS, visit the following MSDN Web site:

http://msdn2.microsoft.com/en-us/library/ms175609.aspx

Modification Type:MajorLast Reviewed:9/14/2006
Keywords:kberrmsg kbQFE kbhotfixserver kbpubtypekc KB919956 kbAudDeveloper kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.