Hi

I am trying to connect to a database located on an Analysis Services
2005 server running on a Windows 2003 SP1 box using a client program I
had written.
The program uses ADO MD and is running on a Windows XP SP2 box.

My provider string is Provider=MSOLAP.3;Data Source=9.30.168.131

When I try to connect, I get

Error number: 80004005 The following system error occurred: The
system cannot find the file specified.
Error number: 80004005 Provider could not set DATASOURCE, USERID, or
PASSWORD property.
Source : ADODB.Connection
Description : Provider could not set DATASOURCE, USERID, or PASSWORD
property.

I never needed to provide the USERID or PASSWORD property before since
I always just pass the userid and password value to the corresponding
optional parameters of the ADO Connection Open method.

I installed Microsoft SQL Server 20005 Analysis Services 9.0 OLEDB
Provider on the Windows XP SP2 box.
Is there something else that I need to install?

When I run my client program on the machine with Analysis Services 2005
server installed using the above provider string, it works fine.

When I changed my provider string to
Provider=MSOLAP.3;DATASOURCE=9.30.168.131;USERID=a dmin;PASSWORD=password;
and I get a different error.

Error number: 80004005 The following system error occurred: The
system cannot find the file specified.
Error number: 80004005 Unspecified error
Source : Microsoft OLE DB Provider for Analysis Services 2005
Description : The following system error occurred: The system cannot
find the file specified.

Does anyone know how to fix this?

Hi,

Are AS Box and XP box in the same domain? Has user account, which is logged
in on the XP, sufficient rights to access AS?

Vladimir Chtepa

<joshkpeng (AT) hotmail (DOT) com> schrieb im Newsbeitrag
news:1136854211.504387.181900 (AT) g49g2000cwa (DOT) googlegroups.com...

have you try to use the netbios name of the server instead-of the IP
address?
Data Source=MyServer

does your 2 computers are on the same domain?
does your user has access to the AS server?

<joshkpeng (AT) hotmail (DOT) com> wrote

Hi, using the name of the server causes a different error in my case

Error number: 80004005 The peer prematurely closed the connection.
Error number: 80004005 An error was encountered in the transport
layer.
Source : Microsoft OLE DB Provider for Analysis Services 2005
Description : The peer prematurely closed the connection.

I haven't investigated why I am getting this error since using the IP
address was a viable workaround.

Hi

Thanks for your reply it put me on the right track. The computers in my
lab are not on a domain. Instead each machine is a workgroup, but all
the machines are on the same subnet so they can see each other.
Back in the day when I was testing Analysis Services 2000, I would
install my client program on machineA and try and connect using userA
to machineB which had MSAS 2000 installed on it. I would only get a
successful connection if userA was created on machineB. At that time I
realized I couldn't test MSAS 2000 security with my configuration since
I wasn't really connecting with the correct userA, but it was an
acceptable workaround.

It looks like I am experiencing a similar issue when testing with
Analysis Services 2005. Once I changed the user name to machineB\userA,
I was able to connect.

I don't know if my lab configuration is a supported deployment scenario
for Analysis Services 2005. Maybe I should just build myself a small
domain and forget about all these headaches.

Vladimir Chtepa wrote: