FIX: You receive a file system error message when you try to save modifications in SSAS 2012 by using SSDT

Applies to: SQL Server 2012 Analysis ServicesSQL Server 2012 EnterpriseSQL Server 2012 Business Intelligence

Microsoft SQL Server 2012 Service Pack 1 fixes are distributed as one downloadable file. Given that the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 Service Pack 1 fix release.

Symptoms


Consider the following scenario:
  • You connect to a Microsoft SQL Server 2012 Analysis Services (SSAS 2012) database by using SQL Server Data Tools (SSDT) in online mode.
  • You modify the AttributeHierarchyEnabled, AttributeHierarchyVisible, or AttributeHierarchyOrdered property for a dimension attribute.
  • You try to save the modifications.
In this scenario, you receive a file system error message that resembles the following:

Dimension Dimension Name cannot be saved because of the following errors:
File system error: The following error occurred while the '\\?\...\....dstore' file was being copied to the '\\?\...\....dstore' file: The file exists. .
Server: The current operation was cancelled because another operation in the transaction failed.

Additionally, SSAS stops unexpectedly.

Note If you restart SSAS after you receive the error message, the database is not displayed.

Resolution


Cumulative update information

Cumulative Update 4 for SQL Server 2012 SP1

The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to go to the article in the Microsoft Knowledge Base:
2833645 Cumulative update 4 for SQL Server 2012 SP1
Note Given that 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 SP1 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 go to the article in the Microsoft Knowledge Base:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released

Status


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

Workaround


To work around this issue, use one of the following methods:
  • Use an XMLA command to modify the property in SQL Server Management Studio (SSMS).
  • Modify the property by using SSDT in project mode.
  • Modify the property when the database is in an unprocessed state. 

References


For more information about the Incremental Servicing Model for SQL Server, click the following article number to go to the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to go to the article in the Microsoft Knowledge Base:
822499 Naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to go to the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates