Article ID: 2638932 - Last Review: April 17, 2012 - Revision: 5.0 FIX: Error when you run the ProcessUpdate command against a cube that has partitions that use aggregation designs in SSAS 2008 or in SSAS 2008 R2
On This PageMicrosoft distributes Microsoft SQL Server 2008 SP2 or Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012 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 SP2 or SQL Server 2008 R2 or Microsoft SQL Server 2012 fix release. SYMPTOMSConsider the following scenario:
The file 'file name' could not be opened. Please check the file for permissions or see if other applications locked it. The file 'file name' could not be deleted. Please check the file for permissions.
CAUSEThis issue occurs because of problems with the flexible aggregation indexes when the ProcessUpdate command is running. RESOLUTIONCumulative update informationSQL Server 2008 R2 Service Pack 1The fix for this issue was first released in Cumulative Update 6 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:2679367
(http://support.microsoft.com/kb/2679367/
)
Cumulative Update package 6 for SQL Server 2008 R2 Service Pack 1 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:2567616
(http://support.microsoft.com/kb/2567616/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released SQL Server 2012The fix for this issue was first released in Cumulative Update 1 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:2679368
(http://support.microsoft.com/kb/2679368/LN/
)
Cumulative update package 1 for SQL Server 2012 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 2012 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: 2692828
(http://support.microsoft.com/kb/2692828/LN/
)
The SQL Server 2012 builds that were released after SQL Server 2012 was released You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.
SQL Server 2008 R2The fix for this issue was first released in Cumulative Update 12. 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:2659692
(http://support.microsoft.com/kb/2659692/
)
Cumulative Update package 12 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 SQL Server 2008 Service Pack 3The fix for this issue was first released in Cumulative Update 3 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:2648098
(http://support.microsoft.com/kb/2648098/LN/
)
Cumulative update package 3 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 Service Pack 2 (SP2) cumulative update package 7Before you apply this hotfix, SSAS 2008 builds bitmap indexes (.map files) for both the partition fact data (.fact.data files) and the aggregation data (.agg.flex.data and .agg.rigid.data files).After you apply this hotfix, bitmap indexes for the aggregation data are not created, but bitmap indexes continue to be built for the fact data files. 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 2008 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: 2617148
(http://support.microsoft.com/kb/2617148/
)
Cumulative update package 7 for SQL Server 2008 Service Pack 2 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 Service Pack 2 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:2402659
(http://support.microsoft.com/kb/2402659/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released WORKAROUNDTo work around this issue, use one of the following methods:
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
| 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