dbTalk Databases Forums  

Failed to open a connection to AS 2005 using ADOMD

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss Failed to open a connection to AS 2005 using ADOMD in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Amar
 
Posts: n/a

Default Failed to open a connection to AS 2005 using ADOMD - 09-11-2005 , 09:46 PM






Hi,
I have an old thin client windows applicaiton that is failing to connect to
AS 2005 cubes. upon investigation I found that it is failing to open the
connection. The connection string is as follows

Provider=msolap;Integrated Security=SSPI;Persist Security Info=False;Initial
Catalog=<database Name>;Data Source=<server name>;

I get the following error....
"Cannot connect to the server <server Name>. The server is either not
started or too busy."
Does the connection string is wrong? Or Do I need to install any drivers on
the client/server side inorder to ADOMD to be able to open the conneciton to
AS 2005 database?
Your help is greatly appreciated


Reply With Quote
  #2  
Old   
Dave Wickert [MSFT]
 
Posts: n/a

Default Re: Failed to open a connection to AS 2005 using ADOMD - 09-11-2005 , 11:22 PM






Yes, you need to do two (possible three) things:
1) your connectstring must reference msolap.3 (depending on what order you
have registered the components -- the last one is always registered as
msolap -- .3 referes specifically to the 2005 version of the OLEDB provider
for OLAP -- .2 is the AS2K version)
2) you need to install pts9.msi (the equivalent of ptslite.exe in AS2K) for
AS2K5.
3) depending on the version of msxml, you might need to upgrade it.
Both the pts9.msi and the msxml install kit is on the June CTP distribution.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Amar" <Amar (AT) discussions (DOT) microsoft.com> wrote

Quote:
Hi,
I have an old thin client windows applicaiton that is failing to connect
to
AS 2005 cubes. upon investigation I found that it is failing to open the
connection. The connection string is as follows

Provider=msolap;Integrated Security=SSPI;Persist Security
Info=False;Initial
Catalog=<database Name>;Data Source=<server name>;

I get the following error....
"Cannot connect to the server <server Name>. The server is either not
started or too busy."
Does the connection string is wrong? Or Do I need to install any drivers
on
the client/server side inorder to ADOMD to be able to open the conneciton
to
AS 2005 database?
Your help is greatly appreciated




Reply With Quote
  #3  
Old   
Amar
 
Posts: n/a

Default Re: Failed to open a connection to AS 2005 using ADOMD - 09-12-2005 , 11:56 AM



Hi Dave,
Thank you for the quick response. It means that all the clients who needs
to connect to AS 2005 cube must install PTS9.msi and potentially MSXML. Is
this correct?

"Dave Wickert [MSFT]" wrote:

Quote:
Yes, you need to do two (possible three) things:
1) your connectstring must reference msolap.3 (depending on what order you
have registered the components -- the last one is always registered as
msolap -- .3 referes specifically to the 2005 version of the OLEDB provider
for OLAP -- .2 is the AS2K version)
2) you need to install pts9.msi (the equivalent of ptslite.exe in AS2K) for
AS2K5.
3) depending on the version of msxml, you might need to upgrade it.
Both the pts9.msi and the msxml install kit is on the June CTP distribution.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Amar" <Amar (AT) discussions (DOT) microsoft.com> wrote in message
news:61818BBD-3C71-4FFD-8BAD-F861278A72BB (AT) microsoft (DOT) com...
Hi,
I have an old thin client windows applicaiton that is failing to connect
to
AS 2005 cubes. upon investigation I found that it is failing to open the
connection. The connection string is as follows

Provider=msolap;Integrated Security=SSPI;Persist Security
Info=False;Initial
Catalog=<database Name>;Data Source=<server name>;

I get the following error....
"Cannot connect to the server <server Name>. The server is either not
started or too busy."
Does the connection string is wrong? Or Do I need to install any drivers
on
the client/server side inorder to ADOMD to be able to open the conneciton
to
AS 2005 database?
Your help is greatly appreciated





Reply With Quote
  #4  
Old   
Dave Wickert [MSFT]
 
Posts: n/a

Default Re: Failed to open a connection to AS 2005 using ADOMD - 09-13-2005 , 01:31 AM



Unfortunately that is true.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Amar" <Amar (AT) discussions (DOT) microsoft.com> wrote

Quote:
Hi Dave,
Thank you for the quick response. It means that all the clients who needs
to connect to AS 2005 cube must install PTS9.msi and potentially MSXML. Is
this correct?

"Dave Wickert [MSFT]" wrote:

Yes, you need to do two (possible three) things:
1) your connectstring must reference msolap.3 (depending on what order
you
have registered the components -- the last one is always registered as
msolap -- .3 referes specifically to the 2005 version of the OLEDB
provider
for OLAP -- .2 is the AS2K version)
2) you need to install pts9.msi (the equivalent of ptslite.exe in AS2K)
for
AS2K5.
3) depending on the version of msxml, you might need to upgrade it.
Both the pts9.msi and the msxml install kit is on the June CTP
distribution.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no
rights.


"Amar" <Amar (AT) discussions (DOT) microsoft.com> wrote in message
news:61818BBD-3C71-4FFD-8BAD-F861278A72BB (AT) microsoft (DOT) com...
Hi,
I have an old thin client windows applicaiton that is failing to
connect
to
AS 2005 cubes. upon investigation I found that it is failing to open
the
connection. The connection string is as follows

Provider=msolap;Integrated Security=SSPI;Persist Security
Info=False;Initial
Catalog=<database Name>;Data Source=<server name>;

I get the following error....
"Cannot connect to the server <server Name>. The server is either not
started or too busy."
Does the connection string is wrong? Or Do I need to install any
drivers
on
the client/server side inorder to ADOMD to be able to open the
conneciton
to
AS 2005 database?
Your help is greatly appreciated







Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.