Re: VS.NET Web Control for B.I., XML/A problem

I would suggest using the sample applications instead of the VS.NET web
control to get things setup... Also, try using a HTTP Tracer utility
(downloadable from various places) to see the message traffic and hopefully
narrow down the problem.

Thanks,
Akshai

--
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=83&SiteID=1

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.


"Alexander Greiner" <AlexanderGreiner@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:7A6114C5-DDC9-4062-AEAD-681F7149F24D@xxxxxxxxxxxxxxxx
Thanks Akshai! It seems to work, but I get another error message.

It occurs later, that means not directly after entering
"http://localhost/xmla/msxisapi.dll";. After entering the "Url" the field
"Data Source" is automatically filled with "Provider=MSOLAP;Data
Source=local" and after ~1 sec. the message "SoapException: An error
occured
while processing the request." is displayed.

When I put the generated connection string into a new .udl-File I can even
test the connection successfully, but it uses "Microsoft OLE DB Provider
for
Analysis Services 9.0" although I am using MS SQL Server 2000 Desktop
Engine
Analysis Services.

Regards,
Alex

"Akshai Mirchandani [MS]" wrote:

My recollection is that the VS.NET Web Control is only supported against
XMLA 1.0...

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=83&SiteID=1

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.

"Alexander Greiner" <AlexanderGreiner@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:E74D380B-49AA-45DF-A610-C8E61D561552@xxxxxxxxxxxxxxxx
Hi @all,

I have a similar problem with XML/A - or better with the Visual Studio
.NET
Web Control for Business Intelligence.

I am running .NET 1.1 with VS.NET 2003 (and also .NET 2.0 bis VS.NET
2005),
Microsoft SQL Server Desktop Engine 2000 SP4 and Analysis Server 2000
SP1
on
my Windows XP SP2 Laptop. I have installed MSXML 4.0 Service Pack 2,
Hotfix
for MSXML 4.0 Service Pack 2 - KB832414 and XML for Analysis 1.1
Software
Development Kit. When I enter "http://localhost/xmla/msxisapi.dll"; in
my
IE I
get the same output as you posted below.

My problem is that when opening the "Create a connection" dialog of the
VS.NET Web Control for B.I. and entering
"http://localhost/xmla/msxisapi.dll";
the following error occurs: "NullReferenceException: The Discover
method
returned a null reference."

Thanks in advance for your help!
Regards
Alex

"Bob DeRemer" wrote:

AS you can see from the response below, the SDK is accessible. In
fact,
they
tried setting bad connection parameters and got a connection error.
It
seems
they are getting connected, but that they cannot run the query. Any
other
suggestions, or ways to capture debug traces from msxisapi.dll?

Thanks!

Here is the SOAP response from a URL request to
http://localhost/xmla/msxisapi.dll...

<?xml version="1.0" ?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
<SOAP-ENV:Body>
<SOAP-ENV:Fault xmlns:XA="urn:schemas-microsoft-com:xml-analysis">
<faultcode>XA:XMLAnalysisError.88BA0800</faultcode>
<faultstring>The Web service supports only the POST
operation.</faultstring>
<faultactor>urn:schemas-microsoft-com:xml-analysis</faultactor>
<detail>
<Error ErrorCode="2293893120" Description="The Web service
supports
only
the POST operation." Source="urn:schemas-microsoft-com:xml-analysis"
/>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

--
Bob DeRemer
Sr. Microsoft Architect
SAP Labs


"Bob DeRemer" wrote:

Akshai,

Thanks for the quick reply. I'll have the engineer try your
suggestions
out. In the meantime, the error that was received by the XML/A
client
was
simply "Status (500): Server Error". Is there anyplace some logging
can be
configured when running under XP to capture some detailed error
information
on what is happening inside msxisapi.dll?

Thanks,
--
Bob DeRemer
Sr. Microsoft Architect
SAP Labs


"Akshai Mirchandani [MS]" wrote:

You can't use SQL Profiler against AS 2000. But you can use a HTTP
trace
utility to sit in between the client application and IIS...

Unfortunately, the information below isn't really sufficient to
guess
what
is happening -- at least an error message would be useful.

Another debugging tip would be to see if you can use Internet
Explorer to
just browse to the URL of the XMLA SDK -- it should return a SOAP
Fault
indicating that "Only the POST operation is supported", but it
would
at
least show that the SDK is accessible through IIS.

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=83&SiteID=1

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.

"Bob DeRemer" <bderemer@xxxxxxxxxxxxxxxx> wrote in message
news:27675372-72F2-4B18-BF61-3BAD7F73426C@xxxxxxxxxxxxxxxx
I have a developer who is having a problem using XML/A against
SQL
2000 AS.
I am not really familiar with XML/A and OLAP, but am the conduit
to
MS, so
I'm posting the problem here.

They are using:

Windows XP SP2
SQL Server 2000 SP4
SQL Server 2000 Analysis Services SP4
MDAC 2.8 SP1
XML for Analysis 1.1

Their problem is they seem to be able to get connected, but
cannot
execute
the query. When they try using a native application [vs going
through
XML/A], they can connect and query fine. Also, when they used a
Java MDX
client that calls through XML/A, they got more detailed error
information
stating there was an IOException: Error (getCubeList).

I don't know if this is enough information, but this is all I
have
at this
point. I have asked him to run SQL Profiler to watch the
traffic
between
XML/A and SQL 2KAS, but haven't heard anything back.

If anyone has any suggestions, such as SP2 security changing
something in
IIS for instance, that now needs to be modified, that would be
great.

Thanks in advance for any help,

--
Bob DeRemer
Sr. Microsoft Architect
SAP Labs








.

Relevant Pages

  • Re: VS.NET Web Control for B.I., XML/A problem
    ... When I put the generated connection string into a new .udl-File I can even ... Analysis Services 9.0" although I am using MS SQL Server 2000 Desktop Engine ... I have a similar problem with XML/A - or better with the Visual Studio ... "Bob DeRemer" wrote: ...
    (microsoft.public.sqlserver.olap)
  • Re: The following system error occurred: .
    ... SQL Server 2005 Analysis Services instance. ... and the specified Analysis Services ... Test connection failed because of an error in initializing provider. ...
    (microsoft.public.sqlserver.datawarehouse)
  • Re: Connecting to Analysis Services 2000 using XMLA SDK 1.1
    ... The GET operation is *not* supported by the XMLA web ... Try out the MSDN Forums for Analysis Services at: ... Please do not send email directly to this alias. ... The download of the specified resource has failed. ...
    (microsoft.public.data.xmlanalysis)
  • Re: VS.NET Web Control for B.I., XML/A problem
    ... Try out the MSDN Forums for Analysis Services at: ... I have a similar problem with XML/A - or better with the Visual Studio ... Web Control for Business Intelligence. ... "Bob DeRemer" wrote: ...
    (microsoft.public.sqlserver.olap)
  • Re: Modem logs on, but cant be used
    ... Sep 26 20:45:53 localhost network: Setting network parameters: succeeded ... Sep 26 20:48:00 localhost pppd: Serial connection established. ... alias usb-controller1 ehci-hcd ... # Example - obey only what nisplus tells us... ...
    (linux.redhat.misc)
Quantcast