Consider the following scenario. On a computer that is running SQL Server 2005, you perform one of the following actions:
- You use the MDX Query Designer in SQL Server Management Studio (SSMS) to design a query against Analysis Services.
- You use the MDX Query Designer in Business Intelligence Development Studio (BIDS) to design a query when you create a report.
In this scenario, the query designer may stop working. Additionally, you may receive an error message that resembles the following:
Unable to find an entry point named 'GetWindowLongPtr' in 'user32.dll'
When this problem occurs, BIDS or SSMS hangs (stops responding), and you have to force the program to close by using Task Manager.
Note This issue typically occurs when you run SQL Server 2005 on a Windows x64-based system.
The issue occurs because some assemblies are platform specific. However, the assemblies are reported as platform neutral.
Cumulative update information
SQL Server 2005 Service Pack 4
The fix for this issue was first released in Cumulative Update 1 for SQL Server 2005 Service Pack 4. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2464079Â
(http://kbalertz.com/Feedback.aspx?kbNumber=2464079/
)
Cumulative update package 1 for SQL Server 2005 Service Pack 4
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:
2485757Â
(http://kbalertz.com/Feedback.aspx?kbNumber=2485757/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 4 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 4 hotfix to an installation of SQL Server 2005 Service Pack 4. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
The fix for this issue was first released in cumulative update package 12 for SQL Server 2005 Service Pack 3. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2345449Â
(http://kbalertz.com/Feedback.aspx?kbNumber=2345449/
)
Cumulative update package 12 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 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:
981356Â
(http://kbalertz.com/Feedback.aspx?kbNumber=981356/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information, visit the following Microsoft webpages: