Data source name not found with XMLA 1.1 - XML SOAP

Can you describe the machine configuration? E.g. how many machines are
involved, what is the role of each machine and the authentication settings
on the virtual directories, etc.?

Also, could you include the exact error message -- even better the full XMLA
SOAP Fault? Is it "Data source name" or "DataSourceInfo"? (Because they are
two different things...)

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.

"Cristi?n Espinoza T." <cet@puc.cl> wrote in message
news:8baed07.0409060552.7c26832c@posting.google.com...
> Hi,
>
> I've been getting a "Data source name not found..." error after
> querying an ****ysis Services cube with XMLA 1.1. The strange thing is
> that this happens with an application that works fine in every
> computer I tried it with, except for my client's production server (an
> IBM eServer, if this helps).
>
> The cube is processed, and we are using an SQL Server 2000 data
> warehouse. There is no ODBC in all my application, and we have tried
> deleting all the DSN's. I found another post about a namespace
> difference, but I think this is very strange since we are using the
> default configuration, and it works everywhere. Also, the problematic
> computer is acting as an Active Directory domain controller, and all
> the Service Packs are installed.
>
> We have been checking all the possible causes we encountered before
> with XMLA, and of course the information available on the Net, with no
> luck.
>
> Any help will be deeply appreciated.
>
> Cristián Espinoza

Hello, Akshai,

My configuration is as follows:

- We are using an ****ysis Services 2000 running on the same machine
as the IIS and XMLA, so all my problem is with a

single machine.

- MSXML 4.0 is installed.

- The system is a Windows 2000 Server, wich is also acting as a domain
controller. All the test have been run using the

Administrator account.

- Nevertheless, I configured a public role on the AS database,
allowing Everyone to read the cube (also

IUSR_machine_name has been added to this role).

- I've been trying different authentication methods for the XMLA
virtual directory an my application's. Now, we are

trying removing Anonymous authenthication, thinking that it could be a
permissions problem, but with no luck.

- In the begining, I believed that the error we were getting was the
"Datasourceinfo" one, but the datasources.xml is

ok, and in fact I realized that it was the "Data source name not
found" one. I have to admit that I am hardcoding the

datasourcename in the "Properties" element of the Execute command. I
know that this is not recomended, but the strange

thing is that this exact configuration (with the same ASP programs) is
working faultless in every computer we have

tried it with, except for this IBM eServer.

- Since the AS cube is on the same machine, we have discarded the
possibility of XMLA not being able to reach the cube.

We even tried using "local", the machine name and its IP number in
datasources.xml

- Remembering another installation problem, we installed MDAC 2.8,
with no results.

- One odd thing: the error is generated before even checking the
datasources.xml file. For instance, if I manually

change the name of the datasource we are trying to use, I obtain the
same message.

- The Discover methos works ok.

-The error message is:


<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-****ysis">
<faultcode>XA:XML****ysisError.80004005</faultcode>
<faultstring>[Microsoft][ODBC Driver Manager] Data source name not
found and no default driver

specified</faultstring>
<faultactor>urn:schemas-microsoft-com:xml-****ysis</faultactor>
<detail>
<Error ErrorCode="2147500037" Description="[Microsoft][ODBC Driver
Manager] Data source

name not found and no default driver specified"

Source="urn:schemas-microsoft-com:xml-****ysis"/></detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>

Thanks,

Cristián Espinoza

I have another clue I got last night (and something I didn't mention
before): we are using the webservice behavior on a IE web page as our
SOAP messenger, and the problem only originates when we use it. For
instance, I tried one of the sample applications that are included
with XMLA, and it works ok with the faulty server. So, I'm trying to
catch the difference in the way the execute command is being carried
out.

Another thing I thought it could be was the "chunked" IIS property,
as I view that item as a difference between the good and the bad
server. I tried changing it, but with no results.

Thanks again,

Cristián.


cparce@puc.cl (Cristian Espinoza) wrote in message news:<1f59a759.0409090658.4e1e57e4@posting.google.com>...
> Hello, Akshai,
>
> My configuration is as follows:
>
> - We are using an ****ysis Services 2000 running on the same machine
> as the IIS and XMLA, so all my problem is with a
>
> single machine.
>
> - MSXML 4.0 is installed.
>
> - The system is a Windows 2000 Server, wich is also acting as a domain
> controller. All the test have been run using the
>
[Rest of the description continues]

Hello again,

I already solved the problem, but I'm still not sure about the
cause. I believe there is a chance for it to be a bug.

All the problem originates in the way the "Execute" tag is sent in
the SOAP message to the server. The WebService Behavior creates it
like:

<mswsb:Execute xmlns:mswsb="urn:schemas-microsoft-com:xml-****ysis"
xmlns="">

In fact, the "mswsb" prefix usage generates the "Data source name
not found" error in certain machines. I created a simple asp program
that sends the XMLHTTP POST message without using the behavior, and it
works ok if I use:

<Execute xmlns="urn:schemas-microsoft-com:xml-****ysis">

So, to fix the problem, I edited the webservice.htc file (available
at microsoft.com) so it didn't add the prefix( in parseWsdl() I force
the oM.fLiteral property to be "true").

Apparently the only thing in common between the two faulty servers
is the language of a certain component, since the result xml for some
errors comes in spanish in these. I tend to believe that, if there is
a bug of some kind, has some relation with this.

Hope this helps.

Cristián Espinoza


cet@puc.cl (Cristi?n Espinoza T.) wrote in message news:<8baed07.0409060552.7c26832c@posting.google.com>...
> Hi,
>
> I've been getting a "Data source name not found..." error after
> querying an ****ysis Services cube with XMLA 1.1. The strange thing is
> that this happens with an application that works fine in every
> computer I tried it with, except for my client's production server (an
> IBM eServer, if this helps).
>
> The cube is processed, and we are using an SQL Server 2000 data
> warehouse. There is no ODBC in all my application, and we have tried
> deleting all the DSN's. I found another post about a namespace
> difference, but I think this is very strange since we are using the
> default configuration, and it works everywhere. Also, the problematic
> computer is acting as an Active Directory domain controller, and all
> the Service Packs are installed.
>
> We have been checking all the possible causes we encountered before
> with XMLA, and of course the information available on the Net, with no
> luck.
>
> Any help will be deeply appreciated.
>
> Cristián Espinoza