Article ID: 2504524 - Last Review: May 21, 2012 - Revision: 2.0 FIX: "Bad variable type" or "Type mismatch" error when you run an UPDATE CUBE statement that has a custom weighted allocation formula in SSAS 2008 R2 or in SSAS 2008
Microsoft distributes Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2008 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 2008 R2 or SQL Server 2008 fix release. On This PageSYMPTOMSWhen you create an UPDATE CUBE statement that has a custom weighted allocation formula in Microsoft SQL Server 2008 R2 Analysis Services (SSAS 2008 R2) or in Microsoft SQL Server 2008 Analysis Services (SSAS 2008), you receive one of the following error messages:
CAUSEThis issue occurs because the SSAS 2008 R2 or SSAS 2008 engine tries to read the data type from an invalid memory location after SSAS 2008 R2 or SSAS 2008 releases memory used in the custom formula for weighted allocation. RESOLUTIONCumulative update informationSQL Server 2008 Service Pack 3The fix for this issue was first released in Cumulative Update 5 for SQL Server 2008 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:2696626
(http://support.microsoft.com/kb/2696626/LN/
)
Cumulative update package 5 for SQL Server 2008 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 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: 2629969
(http://support.microsoft.com/kb/2629969/LN/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 3 hotfix to an installation of SQL Server 2008 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.
SQL Server 2008 R2The fix for this issue was first released in Cumulative Update 6. 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:2489376
(http://support.microsoft.com/kb/2489376/
)
Cumulative Update package 6 for SQL Server 2008 R2 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, click the following article number to view the article in the Microsoft Knowledge Base:981356
(http://support.microsoft.com/kb/981356/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about the UPDATE CUBE statement for MDX, visit the following Microsoft Developer Network (MSDN) website: General information about the UPDATE CUBE statement for MDX
(http://msdn.microsoft.com/en-us/library/ms145488.aspx)
For more information about how to use a cube writeback for MDX, visit the following MSDN website:General information about how to use cube writebacks for MDX
(http://msdn.microsoft.com/en-us/library/ms145568.aspx)
| Other Resources Other Support Sites
CommunityArticle Translations |






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top