![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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 |
#3
| |||
| |||
|
|
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/Sho...ID=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 (AT) newgroups (DOT) nospam> wrote in message news:27675372-72F2-4B18-BF61-3BAD7F73426C (AT) microsoft (DOT) com... 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 |
#4
| |||
| |||
|
|
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/Sho...ID=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 (AT) newgroups (DOT) nospam> wrote in message news:27675372-72F2-4B18-BF61-3BAD7F73426C (AT) microsoft (DOT) com... 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 |
#5
| |||
| |||
|
|
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/Sho...ID=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 (AT) newgroups (DOT) nospam> wrote in message news:27675372-72F2-4B18-BF61-3BAD7F73426C (AT) microsoft (DOT) com... 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 |
#6
| |||
| |||
|
|
The 500 status is the standard HTTP code for a SOAP Fault -- you need to look at the content of the SOAP Fault to figure out what the failure is... As I mentioned earlier, you can download various HTTP trace utilities which sit in between the client and the web server and trace out all requests and responses. But really speaking the client application should be exposing more information about the error too -- it should be looking into the SOAP Fault and displaying the errors from there. Thanks, Akshai -- Try out the MSDN Forums for Analysis Services at: http://forums.microsoft.com/MSDN/Sho...ID=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 (AT) newgroups (DOT) nospam> wrote in message news:EF63B666-5932-463B-B498-07376E35C615 (AT) microsoft (DOT) com... 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/Sho...ID=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 (AT) newgroups (DOT) nospam> wrote in message news:27675372-72F2-4B18-BF61-3BAD7F73426C (AT) microsoft (DOT) com... 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 |
#7
| |||
| |||
|
|
Below is a snapshot of what they captured using TcpTrace - both the request and response. They said they googled for the XMLAnalysisError value, but didn't find anything that helped them determine what the problem was. In addition to the http tracing, you never mentioned if the msxisapi.dll dumps any detailed log information that we can turn on. Can you comment on whether there is anything we can turn on in MS XML/A to log more details to file? Thanks [REQUEST] POST /xmla/msxisapi.dll HTTP/1.1 Content-Type: text/xml SOAPAction: "urn:schemas-microsoft-com:xml-analysis iscover"User-Agent: Jakarta Commons-HttpClient/2.0.2 Host: localhost:8080 Content-Length: 741 ?xml version="1.0" encoding="utf-8" ?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><SOAP-ENV:Body><Discover xmlns="urn:schemas-microsoft-com:xml-analysis" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><RequestTyp e>MDSCHEMA_CUBES</RequestType><Restrictions><RestrictionList><CATALO G_NAME>Foo dMart2000</CATALOG_NAME></RestrictionList></Restrictions><Properties><Property List><DataSourceInfo>Local Analysis Server</DataSourceInfo><Catalog>FoodMart2000</Catalog><Format>Tabular</Format Content>SchemaData</Content></PropertyList></Properties></Discover></SOAP-ENV :Body></SOAP-ENV:Envelope [RESPONSE] HTTP/1.1 100 Continue Server: Microsoft-IIS/5.1 Date: Thu, 03 Aug 2006 20:10:59 GMT X-Powered-By: ASP.NET HTTP/1.1 500 Server Error Server: Microsoft-IIS/5.1 Date: Thu, 03 Aug 2006 20:10:59 GMT X-Powered-By: ASP.NET Content-Type: text/xml; charset="utf-8" Transfer-encoding: chunked 267 ?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.80020009</faultcode faultstring>An error occurred while processing the request.</faultstring faultactor>urn:schemas-microsoft-com:xml-analysis</faultactor detail Error ErrorCode="2147614729" Description="" Source="urn:schemas-microsoft-com:xml-analysis"/></detail></SOAP-ENV:Fault></S OAP-ENV:Body></SOAP-ENV:Envelope 0 |
#8
| |||
| |||
|
|
Usually the "real" error is hidden in the Event Viewer for errors in the IIS<->XMLA portion of the call. Not sure if its related but FoodMart is usually named 'FoodMart 2000' not 'FoodMart2000'. Make sure you have the latest MSXML installed on the server too. http://www.microsoft.com/downloads/d...bcf-3bcf-4009- be21-27e85e1857b1&displaylang=en On 8/3/06 1:48 PM, in article 5FCA0C39-4DA4-4BE9-A895-C52A5AD01205...soft (DOT) com, "Bob DeRemer" bderemer (AT) newgroups (DOT) nospam> wrote: Below is a snapshot of what they captured using TcpTrace - both the request and response. They said they googled for the XMLAnalysisError value, but didn't find anything that helped them determine what the problem was. In addition to the http tracing, you never mentioned if the msxisapi.dll dumps any detailed log information that we can turn on. Can you comment on whether there is anything we can turn on in MS XML/A to log more details to file? Thanks [REQUEST] POST /xmla/msxisapi.dll HTTP/1.1 Content-Type: text/xml SOAPAction: "urn:schemas-microsoft-com:xml-analysis iscover"User-Agent: Jakarta Commons-HttpClient/2.0.2 Host: localhost:8080 Content-Length: 741 ?xml version="1.0" encoding="utf-8" ?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><SOAP-ENV:Body><Discover xmlns="urn:schemas-microsoft-com:xml-analysis" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><RequestTyp e>MDSCHEMA_CUBES</RequestType><Restrictions><RestrictionList><CATALO G_NAME>Foo dMart2000</CATALOG_NAME></RestrictionList></Restrictions><Properties><Property List><DataSourceInfo>Local Analysis Server</DataSourceInfo><Catalog>FoodMart2000</Catalog><Format>Tabular</Format Content>SchemaData</Content></PropertyList></Properties></Discover></SOAP-ENV :Body></SOAP-ENV:Envelope [RESPONSE] HTTP/1.1 100 Continue Server: Microsoft-IIS/5.1 Date: Thu, 03 Aug 2006 20:10:59 GMT X-Powered-By: ASP.NET HTTP/1.1 500 Server Error Server: Microsoft-IIS/5.1 Date: Thu, 03 Aug 2006 20:10:59 GMT X-Powered-By: ASP.NET Content-Type: text/xml; charset="utf-8" Transfer-encoding: chunked 267 ?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.80020009</faultcode faultstring>An error occurred while processing the request.</faultstring faultactor>urn:schemas-microsoft-com:xml-analysis</faultactor detail Error ErrorCode="2147614729" Description="" Source="urn:schemas-microsoft-com:xml-analysis"/></detail></SOAP-ENV:Fault></S OAP-ENV:Body></SOAP-ENV:Envelope 0 |
#9
| |||
| |||
|
|
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/Sho...ID=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 (AT) newgroups (DOT) nospam> wrote in message news:27675372-72F2-4B18-BF61-3BAD7F73426C (AT) microsoft (DOT) com... 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 |
#10
| |||
| |||
|
|
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/Sho...ID=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 (AT) newgroups (DOT) nospam> wrote in message news:27675372-72F2-4B18-BF61-3BAD7F73426C (AT) microsoft (DOT) com... 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 |
![]() |
| Thread Tools | |
| Display Modes | |
| |