MS SQL Server OLAP - XMLA SDK - Japanese Locks up

Author

XMLA SDK - Japanese Locks up

Tony M

2005-11-25, 8:23 pm

Hi,

I was wondering if anyone has either successfully used the XMLA 1.1 SDK w/
Analysis Services 2000 on a Japanese 2000 Advanced Server setup. An
MDSCHEMA_CUBES request locks XMLA provider, causing processing running
msxisapi.dll to goto 100% CPU utilitization. This happens for cube names that
are either English or Japanese.

The Setup is :
OS: Japanese Win2K SP4
SQL AS: Japanese SQL AS 2K SP4
Microsoft XML Core Services (MSXML) 4.0 SP2
XML for Analysis SDK 1.1

Provider responds successfully to http://localhost/xmla/msxisapi.dll access
through browser. Part of message is returned in Japanese

DISCOVER_DATASOURCES
request type for Discover method works fine.
MDSCHEMA_DIMENSIONS request works. When MDSCHEMA_CUBES is run, the provider
locks up as described.

Setup of similar configuration on Windows 2003 works without issue.

Thanks for any info.

Immy

2005-11-26, 7:23 am

Hi tony,

I'm afraid i'm not offering a solution here, however I am going to be
speaking to MS next week about a problem I am having related Japanese
characters and AS2000.

I experince lock ups too when cubing data if i have English and Japanese
characters returned together in a dimension.

Maybe there is some relation here???
If anyone is able to provide and answer to your problem, i will certainly
try to implement any of the possible solutions to solve my problem too.

Immy
"Tony M" <TonyM@discussions.microsoft.com> wrote in message
news:43878995-508B-4BEA-8378- CD31B069F919@microso
ft.com...
> Hi,
>
> I was wondering if anyone has either successfully used the XMLA 1.1 SDK w/
> Analysis Services 2000 on a Japanese 2000 Advanced Server setup. An
> MDSCHEMA_CUBES request locks XMLA provider, causing processing running
> msxisapi.dll to goto 100% CPU utilitization. This happens for cube names
> that
> are either English or Japanese.
>
> The Setup is :
> OS: Japanese Win2K SP4
> SQL AS: Japanese SQL AS 2K SP4
> Microsoft XML Core Services (MSXML) 4.0 SP2
> XML for Analysis SDK 1.1
>
> Provider responds successfully to http://localhost/xmla/msxisapi.dll
> access
> through browser. Part of message is returned in Japanese
>
> DISCOVER_DATASOURCES
request type for Discover method works fine.
> MDSCHEMA_DIMENSIONS request works. When MDSCHEMA_CUBES is run, the
> provider
> locks up as described.
>
> Setup of similar configuration on Windows 2003 works without issue.
>
> Thanks for any info.
>

Akshai Mirchandani [MS]

2005-11-29, 8:24 pm

Sorry Tony, I haven't heard of any such issue and the behavior is quite
unexpected... Also, if MDSCHEMA_DIMENSIONS succeeds, then my guess is that
the cube name isn't the issue -- it could be some other data type conversion
issue or column causing the problem. Are you able to connect with MDX Sample
on that same machine and view the list of cubes in the database?

Thanks,
Akshai
--
This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Tony M" <TonyM@discussions.microsoft.com> wrote in message
news:43878995-508B-4BEA-8378- CD31B069F919@microso
ft.com...
> Hi,
>
> I was wondering if anyone has either successfully used the XMLA 1.1 SDK w/
> Analysis Services 2000 on a Japanese 2000 Advanced Server setup. An
> MDSCHEMA_CUBES request locks XMLA provider, causing processing running
> msxisapi.dll to goto 100% CPU utilitization. This happens for cube names
> that
> are either English or Japanese.
>
> The Setup is :
> OS: Japanese Win2K SP4
> SQL AS: Japanese SQL AS 2K SP4
> Microsoft XML Core Services (MSXML) 4.0 SP2
> XML for Analysis SDK 1.1
>
> Provider responds successfully to http://localhost/xmla/msxisapi.dll
> access
> through browser. Part of message is returned in Japanese
>
> DISCOVER_DATASOURCES
request type for Discover method works fine.
> MDSCHEMA_DIMENSIONS request works. When MDSCHEMA_CUBES is run, the
> provider
> locks up as described.
>
> Setup of similar configuration on Windows 2003 works without issue.
>
> Thanks for any info.
>

Sponsored Links