Microsoft OLE DB Provider for Analysis Services error 80004005

Hello

I get the following error message in one of my ASP applications:
--------------------------
Microsoft OLE DB Provider for Analysis Services error '80004005'
Cannot connect to the server '172.16.103.14'. The server is either not started or too busy.
--------------------------
The IIS server is on a different machine to the MSOLAP server.

When I change the ASP code to point the 'localhost' it runs fine so Im fairly confident the necessary db conn libraries are installed on the IIS server.

There does not appear to be any traffic between the IIS/MSOLAP servers. Although all TCP ports are open. Interestingly, there are other pages on the same site that access a SQL Server resident on the MSOLAP servers & there are no issues.

Any assistance on this matter would be greatly appreciated. (I am a relative novice re: ASP/MSOLAP/IIS etc)Howdy

Talk to your networking guys & check the Default Gateway setting for TCPIP on the server. Sounds like it cant find the server.

Can you ping the IP address from a dos window on the server?

Cheers

SG|||You should check client-library/server-library settings. You prolly have named pipes only and no TCP-IP connection set-up.|||Originally posted by sqlguy7777
Howdy

Talk to your networking guys & check the Default Gateway setting for TCPIP on the server. Sounds like it cant find the server.

Can you ping the IP address from a dos window on the server?

Cheers

SG

Everything seems to be in order on this front. You will note that connectivity to a SQL Server database on the application/database server from the ASP pages on the web server function OK.|||Originally posted by beyond cool
You should check client-library/server-library settings. You prolly have named pipes only and no TCP-IP connection set-up.

Everything seems to be in order on this front. Note that connectivity to a SQL Server database on the application/database server from the ASP pages on the web server function OK...unless im missing something here....|||Howdy kalaa,

Can you confirm you can do these things :

(1) Ping the SQL box by name from the web server from a dos window on the web server e.g. ping <SQL_Server_name>. This will test if you have connectivity to the SQL box from the web server and more importantly confirm the SQL box is recognised in DNS.

(2) you have a valid SQL user ID set up on the SQL box, and that user ID has at least read access in the required database on the SQL box.
This is the user ID that the web application will use to talk to the SQL box.

Cheers,

SG