Hi Everyone,

I figured I use the newsgroups as a last attempt to get some information as
no one at Microsoft could give me a clear answer or direction to the issue.

So Here's my problem

I am trying to use ADOMD.NET v9.0 to connect to an MSAS 2000 Server. Heres
the snip it of code I am using


Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion Connection = new
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion();

Connection.ConnectionString = connectionString;
Connection.Open();
Connection.Close();


The connectionString is
Integrated Security=SSPI;SSPI=Kerberos;data source=server_name;ConnectTo=8.0;

This code is part of a web service which in turn connects to the MSAS 2000
Server. I have Windows Authentication turned on, I have Kerberos working
properly as well. Here is the error message I receive when I try to Open()
the connection

Microsoft.AnalysisServices.AdomdClient.AdomdConnec tionException: The
connection either timed out or was lost. --->
System.Runtime.InteropServices.COMException: Class not registered (Exception
from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))
at
Microsoft.AnalysisServices.AdomdClient.XASC.Micros oft.AnalysisServices.AdomdClient.IXASC.ProcessRequ est(Object RequestStream)
at
Microsoft.AnalysisServices.AdomdClient.StreamInter opHelper.ProcessRequest(XASC comClass, Stream requestStream)
at Microsoft.AnalysisServices.AdomdClient.IXMLAStream .WriteEndOfMessage()
--- End of inner exception stack trace ---
at Microsoft.AnalysisServices.AdomdClient.XmlaClient. EndRequest()
at Microsoft.AnalysisServices.AdomdClient.XmlaClient. SendMessage(Boolean
endReceivalIfException, Boolean readSession, Boolean
readNamespaceCompatibility)
at
Microsoft.AnalysisServices.AdomdClient.XmlaClient. DiscoverWithCreateSession(String
discoverType, ListDictionary properties, Boolean sendNamespacesCompatibility)
at
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.XmlaClientProvider.Microsoft.AnalysisServices .AdomdClient.AdomdConnection+IXmlaClientProviderEx .DiscoverWithCreateSession(String requestType, Boolean sendNamespaceCompatibility)
at
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.RetrieveSchemaRowsets(Boolean createSession)
at
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.ConnectToIXMLA(Boolean
createSession)
at Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.Open()
at Service.Connect(String connectionString)



If you look closely, it cannot find a COM object, which one? I tried to
install MSXML 6.0, Pivot Table Services, as well as the OLEDB Provider 9.0.

If I change the reference of the ADOMD.NET v.9.0 dll to v8.0, the code works
fine and it can connect to the MSAS 2000 server, but cannot establish a
connection to a 2005 server.

Can anyone shed some light on this.

Thanks

The 9.0 provider does not connect to 8.0.
You need to install the PTS 8.0 provider (ptslite.exe) from your SQL2K SP4
distribution.
What happens is that if the 9.0 provider fails, it will try to do COM
delegation to the 8.0 provider if it is installed
--
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.


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

Just to clarify,

I can reference AdoMd.NET 9.0 in my application , but I need to install both
the 9.0 and ptslite.exe(can I install adomd.net 8.0 instead).
The 9.0 library will autoatically determine the MSAS version and use the
apporiate libraries.

Can you confirm this?

"Dave Wickert [MSFT]" wrote:

Alright Everyone,

After some more investigation and Dave's help, I was able to get things
going heres what you need to do

1. Install ADOMD.NET v8.0 (PTSLite.exe from SQL SP4)
2. Install ADOMD.NET v9.0
3. Install XML 6.0 (this was the missing link thats why I was getting the
below error)
4. Install .NET Framework

Your .NET application should be referencing 9.0 instance of ADOMD.NET.
Heres a sample Connection String

provider=msolap.3;Integrated Security=SSPI;ConnectTo=8.0;SSPI=Kerberos;data
source=server_name

One thing I did I notice is that if you don't specify the ConnectTo
attribute, there is a 1-2 sec delay because ADOMD.NET is trying to figure out
what version of AS its trying to connect to

I hope this helps everyone

Thanks for your Dave



"Massimo Galati" wrote:

Ref: 1-2 second delay trying to detect.

That doesn't surprise me since the 8.0 connection attempt is the second
attempt. We need to make sure that a 9.0 server doesn't exist first.
--
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.


"Massimo Galati" <MassimoGalati (AT) discussions (DOT) microsoft.com> wrote