OPENQUERY and MSOLAP/.2 Providers

  • Hi,

    Don't worry about my previous posting listed below. I have used a VS.NET application instead which does the trick. (Using the oledb providers and a dataset.)

    Thanks,

    Johann

    Hi,

    I'm trying to retrieve calculated members from a virtual cube using the OPENQUERY SQL function and a OLAP linkedserver (with either the MSOLAP or MSOLAP.2 providers), the results from MDX Queries are then stored to a SQL Server DB Table.

    ***PROBLEM***:

    The MDX queries executed through the OPENQUERY function returns the following error messages for some members of the dimension used to construct them:

    Could not get the current row value of column '[MSOLAP.2]...[TheCalculatedMember]' from the OLE DB provider 'MSOLAP.2'. The provider cannot determine the value for this column.

    OLE DB error trace [OLE/DB Provider 'MSOLAP.2' IRowset::GetData returned 0x80040e21: Data status returned from the provider: [COLUMN_NAME=...[TheCalculatedMember] STATUS=DBSTATUS_E_UNAVAILABLE]].

    EVEN though...

    (1) The same MDX Queries execute without any problems through the MDX sample application. (including the [TheCalculatedMember])

    (2) The results are properly retrieved from EXCEL using either of the OleDB providers.

    (3) A VBScript using ADOMD Catalog and Cellset Objects retrieves the calculated members without any issues.

    **The only other item displaying "weird behaviour" is the OLAP Cube Browser itself with the following #ERR's:

    "Unable to display cell properties. Inifinite recursion detected during execution of calculated member [ThePrevCalculatedMember]. An error occured during attempt to get a cell value."

    (Service Pack 3a for SQLServer and Analysis Services have been applied.)

    I will really appreciate it if anybody can help me with this problem OR can suggest any other fast/reliable/convenient method of persisting calculated members to an SQL Server table (preferably through SQL commands or DTS packages).

    Thanks,

    Johann van Rensburg

    Edited by - johannvr on 10/17/2003 03:05:18 AM

  • This was removed by the editor as SPAM

  • I'd like to guess that because the calculated measure had some kind of problem, the cube browser and excel could handle it by displaying an error value, but openquery could not.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply