Microsoft OLE DB Provider for SQL Server 2012 Analysis Services." Hresult: 0x80004005 Description: "Server: The operation has been cancelled

Unanswered Microsoft OLE DB Provider for SQL Server 2012 Analysis Services." Hresult: 0x80004005 Description: "Server: The operation has been cancelled

  • Tuesday, May 01, 2012 5:44 AM
     
     

    Hello:

    I have a for each loop which pulls the data from the cube by using mdx query, it is working fine for the some of the loops(iterations), after some iterations it is failing with the following error

    SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.
    An OLE DB record is available.  Source: "Microsoft OLE DB Provider for SQL Server 2012 Analysis Services."  Hresult: 0x80004005  Description: "Server: The operation has been cancelled.".

    OLE DB Source failed the pre-execute phase and returned error code 0xC0202009.

    am using SQL Server 2012

    Thanks

    Pavan


    Pavan K

All Replies

  • Tuesday, May 01, 2012 9:46 AM
     
     
    am able pull same data with SSIS 2008 

    Pavan K

  • Wednesday, May 02, 2012 9:32 AM
    Moderator
     
     

    Hi Pavan,

    It may be caused if the package is deployed in 64bit environment while the data provider is not available in 64bit. Please refer to http://blogs.msdn.com/b/debarchan/archive/2009/04/13/ssis-an-oledb-error-has-occurred.aspx with error code 0xC0202009 to further look at the package.

    Regards,
    Jerry

  • Wednesday, May 02, 2012 9:42 AM
     
     

    Hi Jerry,

    In my case both are 64 bit only, if these are different it should not pull the data at all but its worked perfectly 14 to 16 loops after its failed wih the above specified error


    Pavan K

  • Monday, June 04, 2012 12:25 PM
     
     
    As a temporary fix, I have implemented loop level Restartability (if ETL fails at particular loop, it will start from failure loop from the next run)

    Pavan K

  • Monday, June 04, 2012 8:54 PM
    Moderator
     
     

    Your temporary fix is not a bad idea.

    I would also connect to SSAS using Profiler while running your SSIS package. Then we you experience a failure, carefully read through all the errors visible in Profiler to see if maybe SSIS isn't reporting the root error message properly.


    http://artisconsulting.com/Blogs/GregGalloway