Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. 0x80040E21 or 0x80004005 error when a data flow task in an SSIS package runs an MDX query by using MSOLAP in SQL Server

0x80040E21 or 0x80004005 error when a data flow task in an SSIS package runs an MDX query by using MSOLAP in SQL Server

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You run a Microsoft SQL Server Integration Services (SSIS) package in SQL Server 2012, SQL Server 2008 R2, SQL Server 2008, or SQL Server 2005.
  • The SSIS package contains a data flow task.
  • The task runs a multidimensional expressions (MDX) query in SQL Server Analysis Services (SSAS) by using Microsoft Analysis Services OLE DB Provider for SQL Server (MSOLAP) in an SSIS connection manager.
In this scenario, you may receive an error message that resembles one of the following.

Error message 1
Error: 0xC0202009 at Data Flow Task, OLE DB Source [1]: An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft OLE DB Provider for Analysis Services 2005" Hresult: 0x80004005 Description: "Internal error: An unexpected error occurred (file 'pcrsstore.cpp', line 325, function 'PCRSStore::UnLock').".
Error: 0xC004701A at Data Flow Task, DTS.Pipeline: component "OLE DB Source" (1) failed the pre-execute phase and returned error code 0xC0202009.

Error message 2
Hresult: 0x80004005  Description: "Unable to connect to the Analysis server. The server name 'giclssasbau\gi' was not found. Please verify that the name you entered is correct, and then try again".

Error message 3
Error: 0xC0202009 at Data Flow Task, OLE DB Source [1]: An OLE DB error has occurred. Error code: 0x80040E21.
Error: 0xC004701A at Data Flow Task, DTS.Pipeline: component "OLE DB Source" (1) failed the pre-execute phase and returned error code 0xC0202009.

↑ Back to the top

Workaround

To work around this issue, add the following clause to the connection string of the MSOLAP provider in the connection manager:

Format=Tabular;

↑ Back to the top

Status

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

↑ Back to the top

Keywords: kb, kbsurveynew, kbtshoot, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2861775
Revision : 1
Created on : 1/7/2017
Published on : 7/22/2013
Exists online : False
Views : 1865