In Microsoft SQL Server 2005 Analysis Services (SSAS 2005), you move data folders from one computer to another computer. However, the metadata files become corrupted. This problem occurs when the following conditions are true:

• One SSAS 2005 server is used to process data and another SSAS 2005 server is used to serve data.
• The StorageLocation property for at least one partition is configured to store data by using a nondefault path.
• The capitalization of the nondefault path is not the same on these two computers.

Additionally, the following issues occur:

• Some files in the data folders may appear unexpectedly on the destination computer.
• Versions of some index files may not be updated to match the version of the partition.
• The "DataFileList" tag of one or more Prt.xml files may contain a fully qualified file path that resembles the following:

  <DataFileList>C:\Olap\Data\\EF770A17-C4B1-40B5-9337-84448E2B53FD.18.0.0.0\259.agg.rigid.data;C:\Olap\Data\\EF770A17-C4B1-40B5-9337- 84448E2B53FD.18.0.0.0\259.agg.rigid.data.hdr;C:\Olap\Data\\EF770A17-C4B1-40B5-9337-84448E2B53FD.18.0.0.0\259.fact.data;C:\Olap\Data\\EF770A17-C4B1-40B5-9337 -84448E2B53FD.18.0.0.0\259.fact.data.hdr;C:\Olap\Data\\EF770A17-C4B1-40B5-9337-84448E2B53FD.18.0.0.0\259.string.data;265.agg.flex.data;

Note This issue also occurs in Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2008.

Cumulative update information

SQL Server 2005

The fix for this issue was first released in Cumulative Update 9 for SQL Server 2005 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: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. 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: Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 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 1

The fix for this issue was first released in Cumulative Update 9 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: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: Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. 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

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 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. 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:

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 2. 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: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:

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

For information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base: For more information about how to obtain SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base: For more information about new features and improvements in SQL Server 2005 Service Pack 3, visit the following Microsoft Web site: For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: