Symptoms
Consider the following scenario:
-
You try to use the Microsoft OLE DB provider for Analysis Services 2008 R2 or for Analysis Services 2012 to import data from an instance of Microsoft SQL Server Analysis Services to another instance of Microsoft SQL Server Analysis Services.
-
A time-out occurs when the process reaches the value of the ExternalCommandTimeout property before the data import process is completed.
In this scenario, the data import process is stopped as expected. However, a message reports that the data import process was successful, even if only some data was imported.
When you capture a trace by using SQL Server Profiler on the SSAS 2008 R2 or SSAS 2012 instance, the following error message is contained in the trace file:
XML for Analysis parser: The XML for Analysis request timed out before it was completed
Note The default value for the ExternalCommandTimeout property is 3600 seconds.
Resolution
To resolve this issue, apply the cumulative update package 10 for SQL Server 2008 R2 Service Pack 1 (SP1) or apply the cumulative update package 5 for SQL Server 2012. Both fixes are for the Microsoft OLE DB provider for Analysis Services. After you apply the cumulative update package, an incomplete data import process that is caused by a time-out will be reported as unsuccessful.
Cumulative update information
Cumulative Update 7 for SQL Server 2012
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 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2823247 Cumulative update package 7 for SQL Server 2012Note 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. 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:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
Cumulative Update 3 for SQL Server 2012 SP1
The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2812412 Cumulative update package 3 for SQL Server 2012 Service Pack 1Note 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 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 view 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
Cumulative Update 10 for SQL Server 2008 R2 SP1
The fix for this issue was first released in Cumulative Update 10. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2783135 Cumulative update package 10 for SQL Server 2008 R2 Service Pack 1Note 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 Service Pack 1 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 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released
Cumulative Update 5 for SQL Server 2012
The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2777772 Cumulative update 5 for SQL Server 2012Note 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. 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:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
Workaround
To work around this issue, do one of the following:
-
For stand-alone SSAS instances, you can increase the value of the ExternalCommandTimeout property in the advanced properties GUI in SQL Server Management Studio.
-
For a PowerPivot for Excel worksheet, there is no workaround because changing the ExternalCommandTimeout property is not supported.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
