Hi

We've recently upgraded our dev environments to .net V2 and am getting a
constant error from XMLA when I try to connect.

"The Namespace XA:Session could not be found"

This only happens when we try to connect to a local MSAS2000 server, it can
connect to remote MSAS2000 server or remote 2005 servers.

Am I missing a pre-requisite install? I have run adomd v9, xmla sdk and soap
sdk in my attempts to access the server and also configured xmla on IIS.

Connection string is
sConStr = "Data Source=http://" + sDataSrc + "/xmla/msxisapi.dll;";

where sDataSrc is the name of the local server

TIA

sometimes a local HTTP access doesn't works if the URL is not localhost but
http://<server>
I have this type of issue.
A loopback network card could help you

but you can also use http://localhost
or use a direct connection (not HTTP) to your server. The performance is
better.

"Graham Lloyd" <gilly1409 (AT) hotmail (DOT) com> wrote

thanks Jeje

I will alter our code to be configuarable to use TCP or HTTP. I had used
only HTTP as the performance of remote TCP connections was really bad (20
odd seconds to open a connection on a remote MSAS server)

thanks for the info

Any ideas on the Ordinal issue I posted earlier?

Cheers


"Jeje" <willgart (AT) hotmail (DOT) com> wrote

Hi Jeje

I now get the same problem when I try to retieve catalogs from a remote
machine using the following line

dsCatlogs = mcnADOMD.GetSchemaDataSet(AdomdSchemaGuid.Catalogs , oRest);

the stack trace is as follows

StackTrace " at
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.XmlaClientProvider.Microsoft.AnalysisServices .AdomdClient.AdomdConnection.IXmlaClientProviderEx .Discover(String
requestType, IDictionary restrictions, InlineErrorHandlingType
inlineErrorHandling, Boolean sendNamespaceCompatibility)\r\n at
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.RetrieveSchemaRowsets(Boolean
createSession)\r\n at
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.GetSchemaDataSet(Guid
schema, Object[] restrictions, Boolean throwOnInlineErrors)\r\n at
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.GetSchemaDataSet(Guid
schema, Object[] restrictions)\r\n at spfData.Web.getCatalogs(String
sDataSrc) in D:\\Development\\Calumo
Projects\\CalumoWeb\\calDAL\\msOlap.cs:line 1250" string

when I connect to the box remotely using xmla. It all works fine if I use
TCP but rmote TCP connection takes roughly 20 seconds. It is only that box,
so something is not installed or not runing correctly. It also appears the
same issue occurs when trying to connect on the local box using TCP or using
localhost rather than the machine name

I've tried

reinstall XMLA, SOAP, .NET v2, ADOMD9


any other ideas?

cheers

"Graham Lloyd" <gilly1409 (AT) hotmail (DOT) com> wrote

Can you run a trace on the HTTP messages? There are several tools there that
let you do this...

Also, can you verify which version of ADOMD.NET you are using? There are two
of them -- the original web release and the new one that became available
with AS 2005 (and is also available as a web download).

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.

"Graham Lloyd" <gilly1409 (AT) hotmail (DOT) com> wrote

Hi Akshai

Sorry for dumb question but I have never 'traced' a SOAP call before. Can
you send me a link to a tool with a 'how to' ?

We are using ADOMD.net V9 to connect to MSAS2000 on the local machine. The
box can connect to remote MSAS2000 servers via xmla and retrieve the
catalogs. We have also discovered that if the local user tries to connect
via TCP rather than XMLA, at the connection open he gets a 'Could not
connect to server, please check the server is running', in xmla he can
connect, just not get any metadata via the schema rowset.

thanks

"Akshai Mirchandani [MS]" <akshaim (AT) online (DOT) microsoft.com> wrote

There used to be one with the SOAP Toolkit. I think that IIS Diagnostics has
one
(http://www.microsoft.com/windowsserv...s/default.mspx)
but I haven't tried it out.

You can just search for tools to trace HTTP requests on the net and you
should find a bunch. Essentially what they do is listen on another port
(e.g. 8080). You point your client application to
http://server:8080/xmla/msxisapi.dll and the tool will trace your request,
forward it to the actual HTTP server and then trace the response and forward
it back to you. It acts like a proxy and shows you the actual traffic.


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.

"Graham Lloyd" <gilly1409 (AT) hotmail (DOT) com> wrote