May 10, 2011 at 9:19 pm
I'm supporting a SQL 2008 SSIS Package which is getting the error below intermittently when executing a dimension processing step. Is there any timeout setting I can increase to keep this from timing out? I am complete unfamiliar with this and the developer is waist deep in another project to examine this.
Thanks for any help.
Executed as user: xxxx. Microsoft (R) SQL Server Execute Package Utility Version 10.0.2531.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 3:16:19 PM Error: 2011-05-09 16:20:14.43 Code: 0xC113000A Source: Incremental Dimension Processing [22] Description: Parser: An error occurred during pipeline processing. End Error Error: 2011-05-09 16:20:14.44 Code: 0xC113000A Source: Incremental Dimension Processing [22] Description: XML for Analysis parser: The XML for Analysis request timed out before it was completed. End Error Error: 2011-05-09 16:20:14.45 Code: 0xC0047022 Source: Perform Incremental ProcessAdd SSIS.Pipeline Description: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Dimension Processing" (22) failed with error code 0x80004005 while processing input "AnalysisServicesServerInput" (23). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure. End Error Error: 2011-05-09 16:20:14.48 Code: 0xC113000A Source: Perform Incremental ProcessAdd Dimension Processing [22] Description: XML for Analysis parser: The commit or rollback request cannot be completed because there is no active transaction in this session. End Error Error: 2011-05-09 16:20:14.50 Code: 0xC0047018 Source: Perform Incremental ProcessAdd SSIS.Pipeline Description: component "Dimension Processing" (22) failed the post-execute phase and returned error code 0x80004005. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 3:16:19 PM Finished: 5:43:53 PM Elapsed: 8854.08 seconds. The package execution failed. The step failed.
June 10, 2015 at 8:48 am
I ran into the same issue when executing a MDX query against an SSAS 2014 database via an SSIS 2008.
The SSIS package is for cache-warming purpose.
The Profile Trace shows that the query stops at exactly 30 seconds. To go around the error, I re-ran the package a couple times and the MDX finally went through. My guess is that, the subsequent run was successful due to a warm cache created by the initial query run.
I can certainly create a Re-try loop to fix the issue. But I wonder whether there is a better way.
On the SSIS side, the connection manager time out and the "Execute SQL Query" task timeout are both 0, which indicates no timout limit.
On the SSAS side, the ServerTimeout is 3600, which is default value by seconds.
Any advice?
July 10, 2015 at 1:12 am
Hi Guys
Did you ever manage to fix this as i am having a similar issue, but on SQL 2012.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply