I have an ASP.NET application which connects to a remote SQL Server Analysis
Services (2000) server. The application connects to Analysis Services just
fine when run from my test machine (Win XP Pro sp2, ADOMD.NET 8.0.0, MSXML4,
IIS5, .NET 1.1). However, the same application just won't connect to the
same remote Analysis Services server from the production machine (Windows
Server 2003, ADOMD.NET 8.0.0, MSXML4, IIS6, .NET 1.1). The connection
string for the application is as follows:

<add key="sOLAPConnString" value="Data Source=DBServer;Initial
Catalog=myOlapDB; Provider=MSOLAP.2; ConnectTo=8.0;"/>
The error that I get is:
Microsoft.AnalysisServices.AdomdClient.AdomdErrorR esponseException: Class
not registered

I've tried removing the Provider=MSOLAP.2 and changing it to MSOLAP. That
doesn't work. However, if I remove the ConnectTo=8.0, I get the following
error: System.Net.Sockets.SocketException: No connection could be made
because the target machine actively refused it. The XP machine is using the
same IIS domain login for the application as the 2003 Server IIS application
pool login. The 2003 Server is also able to connect just fine to the SQL
Server relational database.

Any suggestions?

does the clear/text authentication works fine?
does your AS server is on the samebox?
(if not, you have to configure to use Kerberos authentication if you don't
want to use clear/text)


"Mark G" <Mark (AT) no-spam (DOT) .com> a écrit dans le message de news:
Olor7Lj3EHA.2788 (AT) TK2MSFTNGP15 (DOT) phx.gbl...

There is a dedicated newsgroup for XMLA and ADOMD.NET. I would repost to
microsoft.public.data.xmlanalysis
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Mark G" <Mark (AT) no-spam (DOT) .com> wrote

Thank you and JeJe for the responses. I found what I was looking for in the
XMLA/ADOMD.NET newsgroup. I needed to install PTS to go along with MSXML4
and ADOMD.NET.

"Dave Wickert [MSFT]" <dwickert (AT) online (DOT) microsoft.com> wrote

yep... sometimes we omit the base ;-)
no driver... no access ;-)


"Mark G" <Mark (AT) no-spam (DOT) .com> a écrit dans le message de news:
uaG0Khu3EHA.2192 (AT) TK2MSFTNGP14 (DOT) phx.gbl...

However, in Yukon there will be no need to install OLEDB drivers in order to
connect from ADOMD.NET to Yukon server, ADOMD.NET has all the code to do it
itself !

--
==================================================
Mosha Pasumansky - http://www.mosha.com/msolap
Analysis Services blog at http://www.sqljunkies.com/WebLog/mosha
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================

"Jéjé" <willgart (AT) BBBhotmailAAA (DOT) com> wrote