Error linked server query after installing SP4 on SQL 2000

Hello
SQL 2000 SP3a run fine with an linked server query like
select * from openquery( linkedOlapServer, .. here is the MDX ...')
After installing SP4 build 2039 this query fails with error:
Server: Msg 7302, Level 16, State 1, Line 1
Could not create an instance of OLE DB provider 'MSOLAP'.
OLE DB error trace [Non-interface error: CoCreate of DSO for MSOLAP
returned 0x80040154].
Appreciate hints from experience on which hot fix do I need to install?
Nic
Does changing the "AllowInProcess" to something non zero fix this problem?
http://msdn2.microsoft.com/en-us/library/ms190918.aspx
In Object Explorer, right-click the provider name and select Properties. The
following table describes the available provider options...
thanks,
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Nic" <Nic@.discussions.microsoft.com> wrote in message
news:E4A1CCBC-331D-4C70-B83C-F1AFE5CFAA62@.microsoft.com...
> Hello
> SQL 2000 SP3a run fine with an linked server query like
> select * from openquery( linkedOlapServer, .. here is the MDX ...')
> After installing SP4 build 2039 this query fails with error:
> Server: Msg 7302, Level 16, State 1, Line 1
> Could not create an instance of OLE DB provider 'MSOLAP'.
> OLE DB error trace [Non-interface error: CoCreate of DSO for MSOLAP
> returned 0x80040154].
> Appreciate hints from experience on which hot fix do I need to install?
> Nic
>

Error in mdx querys with quotation marks

The problem:
When I try to execute a mdx with quotation mark inside, I get an error!
Why?
I know that (') is from mdx language.
Will I have to erase this characters from my databases?
I don't think it's good.
In my javascript code(asp):
var cst = new ActiveXObject("ADOMD.Cellset");
...
cst.Source = strSource + " CELL PROPERTIES FORMATTED_VALUE, BACK_COLOR,
FORE_COLOR";
cst.open();
strSource = " 'with ...'
Select {[Programa].[Sigla].[Todos os Programas].[Ajuda
r 'A INDUSTRIA],
[Programa].[Sigla].[Todos os Programas].[APOIO A PROJ SOCIAL
],[Programa].
[Sigla].[Todos os Programas].[APOIO ENSINO SUPERIO]}
on rows,{[Measures].[Libera'es]} ON COLUMNS FROM [dwe_cubo
_pird] CELL
PROPERTIES FORMATTED_VALUE, BACK_COLOR, FORE_COLOR"
The error occur when I execute cst.open()!
Microsoft? OLE DB Provider for Analysis Services error '80040e14'
Syntax error, expecting SELECT, near: 'A INDUSTRIA],[Programa].[Sigl
a].
[Todos...
Message posted via http://www.droptable.comYou need to double up quotation marks within quotes:

strSource = " 'with ...'
Select {[Programa].[Sigla].[Todos os Programas].[Ajudar
''A INDUSTRIA],
[Programa].[Sigla].[Todos os Programas].[APOIO A PROJ
SOCIAL],[Programa].
[Sigla].[Todos os Programas].[APOIO ENSINO SUPERIO]}
on rows,{[Measures].[Libera'es]} ON COLUMNS FROM [dwe_cubo
_pird] CELL
PROPERTIES FORMATTED_VALUE, BACK_COLOR, FORE_COLOR"[vbcol=seagreen]
Here's an earlier thread that discusses this:
http://groups-beta.google.com/group...erver.olap/msg/
5b1f83a30f0203eb[vbcol=seagreen]
Newsgroups: microsoft.public.sqlserver.olap
From: "George Spofford"
Date: Sat, 1 Jun 2002 07:33:16 -0700
Subject: MDX Error with Current Year's
One of those silly things: double it up inside.
With member [measures].[abc] as
'count(descendants([category]._[all Category].[current
year''s].[actuals],,leaves))'
HTH
George Spofford
Microsoft MVP
Chief Architect / OLAP Solution Provider
DSS Lab
http://www.dsslab.com
geo...@.dsslab.com
ISVs & IT organizations: Find out how DSS Lab can speed
your development!
[vbcol=seagreen]
>--Original Message--
>Hello,
>the following MDX fails:

>The error comes because the uniquename is ..year's]

>With member [measures].[abc] as
>'count(descendants([category]_.[all Category].[current
>year's].[actuals],,leaves))'

>How can i write a valid mdx?
[vbcol=seagreen]
>Thanks for reading this
>Jrg
>.
- Deepak
Deepak Puri
Microsoft MVP - SQL Server
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||There is another error!
Microsoft? OLE DB Provider for Analysis Services error '80040e14'
Formula error - cannot find dimension member ("[Programa].[Sigla].&#
91;Todos os
Programas].[APOIO ''A INDUSTRIA]") - in a name-binding function
/Server_1.asp, line 520
"Deepak Puri" wrote:

> You need to double up quotation marks within quotes:
>
> strSource = " 'with ...'
> Select {[Programa].[Sigla].[Todos os Programas].[Ajud
ar ''A INDUSTRIA],
> [Programa].[Sigla].[Todos os Programas].[APOIO A PROJ
> SOCIAL],[Programa].
> [Sigla].[Todos os Programas].[APOIO ENSINO SUPERIO]}
> on rows,{[Measures].[Libera'es]} ON COLUMNS FROM [dwe_cu
bo_pird] CELL
> PROPERTIES FORMATTED_VALUE, BACK_COLOR, FORE_COLOR"
>
> Here's an earlier thread that discusses this:
> http://groups-beta.google.com/group...erver.olap/msg/
> 5b1f83a30f0203eb
> Newsgroups: microsoft.public.sqlserver.olap
> From: "George Spofford"
> Date: Sat, 1 Jun 2002 07:33:16 -0700
> Subject: MDX Error with Current Year's
> One of those silly things: double it up inside.
> With member [measures].[abc] as
> 'count(descendants([category].-[all Category].[current
> year''s].[actuals],,leaves))'
> HTH
> --
> George Spofford
> Microsoft MVP
> Chief Architect / OLAP Solution Provider
> DSS Lab
> http://www.dsslab.com
> geo...@.dsslab.com
> ISVs & IT organizations: Find out how DSS Lab can speed
> your development!
>
>
>
>
>
>
> - Deepak
> Deepak Puri
> Microsoft MVP - SQL Server
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
>|||Maybe you used double-quote characters (Ascii 34), instead of 2
single-quote characters (Ascii 39) - that's the only way I could create
the error message you got?
- Deepak
Deepak Puri
Microsoft MVP - SQL Server
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||Did you copy your code from your application source and paste it here?
The reason I ask is that in my Internet Explorer, the so-called single
quote characters in the member names do not appear as single quotes but
rather as unicode gibberish. The single quotes surrounding calculation
value definitions appear as they should.
The fact your mdx runs on some applications and does not on others leads
me to be farely certain that the member names in your cube do not
contain regular single quote characters but other characters, and that
is what causes your problems.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Error in MDX queries

Dear all Please Help

When I am executing the following queries in MDX the error will come

'Warning 2 Query (15, 1) Parser: The syntax for 'FORMAT_STRING' is incorrect. [Line:15; Column:1] 0 0 '

Query as follows...

CALCULATE;

CREATE MEMBER CURRENTCUBE.[MEASURES].[Percentage of Profit]

AS ([Measures].[Profit],[Sales Analysis].[Group Description].CurrentMember)/([Measures].[Profit],[Sales Analysis].[Group Description].[All]),

FORMAT_STRING = "Percent",

NON_EMPTY_BEHAVIOR = { [Quantity] },

VISIBLE = 1;

CREATE MEMBER CURRENTCUBE.[MEASURES].[Parent Percent]

AS iif(IsEmpty(([Measures].[Profit],[Sales Analysis].[Area Description].Parent)),1,

([Measures].[Profit])/([Measures].[Profit],[Sales Analysis].[Area Description].Parent),

FORMAT_STRING = "Percent",

VISIBLE = 1 ;

hello,

it looks like your second calculated member (i.e. Parent Percent) is missing the closing ')' for the iif function.

hope this helps,

Error handling with MDX and Reporting Services

I have having trouble with an MDX Statement. There are some instances where the MDX statement I am passing in isn't correct or invalid. The report takes in serveral default parameters and creates an MDX statement from it. When this error happens I get an error similiar to

Formula error - cannot find dimension member ("[Time].[2005]") - in a name-binding function

on the report page. I would like to be able to handle this error in reporting services so how. Essientially, I would want to be able to just say if this error happens just take me the plain page and do not load up any defaults.You might consider this a hack, but this can be solved from outside Reporting Services with the new missing member functionality in 2005 (ie invalid member lookups wont generate errors),|||I am using RS 2005 and AS 2005 RTM.

I am having the report to accept a parameter UserUserID that accepts values such as [User].[User ID].&[1].

This is working fine when the front-end calls it with a correct/valid UserID.

When it is the calling the report with a valid UserID, two things that I observe happening:
a) when the Parameter is set to Hidden (on the Report Parameters properties), this error will be displayed "The 'UserUserID' parameter is missing a value"
b) when the Parameter is not set to Hidden, a blank page is shown with the parameter prompt <Select a Value>.

Is there any way to better handle situation a)? Since I need to hide the parameters from the end-users....

Thanks.

Error handling with MDX and Reporting Services

I have having trouble with an MDX Statement. There are some instances where the MDX statement I am passing in isn't correct or invalid. The report takes in serveral default parameters and creates an MDX statement from it. When this error happens I get an error similiar to

Formula error - cannot find dimension member ("[Time].[2005]") - in a name-binding function

on the report page. I would like to be able to handle this error in reporting services so how. Essientially, I would want to be able to just say if this error happens just take me the plain page and do not load up any defaults.

You might consider this a hack, but this can be solved from outside Reporting Services with the new missing member functionality in 2005 (ie invalid member lookups wont generate errors),|||I am using RS 2005 and AS 2005 RTM.

I am having the report to accept a parameter UserUserID that accepts values such as [User].[User ID].&[1].

This is working fine when the front-end calls it with a correct/valid UserID.

When it is the calling the report with a valid UserID, two things that I observe happening:
a) when the Parameter is set to Hidden (on the Report Parameters properties), this error will be displayed "The 'UserUserID' parameter is missing a value"
b) when the Parameter is not set to Hidden, a blank page is shown with the parameter prompt <Select a Value>.

Is there any way to better handle situation a)? Since I need to hide the parameters from the end-users....

Thanks.