Hello,

I am just starting out with Decision Support Objects for Analysis Services.
In a VB6 app I try to run some sample code but am getting an error when I try
to connect to my Olap Server -- which exists and runs fine (Sql Server 2000
Personal Edition SP4 on a winXP service Pack 2). I can create, process,
browse cubes, etc from the Analysis server, and I am using Mixed Mode
Security UID=sa;PWD=xyz;

Here is my sample VB6 code

Private Sub ListServerProps()
Dim dsoServer As DSO.Server
Dim enuClassType As DSO.ClassTypes

' Create instance of server and connect.
' "LocalHost" will default to the
' local Windows NT Server 4.0 where the
' Analysis server is installed.
Set dsoServer = New DSO.Server
dsoServer.Connect "LocalHost" <---- Error out here!

' Show the server's information to the user.
If dsoServer.ClassType = clsServer Then
Debug.Print "Server Properties:"
Debug.Print " Name: " & dsoServer.Name
Debug.Print "Description: " & dsoServer.Description
End If

End Sub

--and here is there error I am getting when I run it:

************************************************** ****
Run-time error '-2147221453 (80040033)':

Cannot connect to the repository

OLAP server: myServer

Error:
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified
************************************************** ****

I can connect to the Sql Server no problem with ADO, ODBC, etc. But I can't
seem to connect to the Analysis server.

Do I need to download an ODBC driver for this? Or do I need to configure
something? Set up a DSN? Linked server? Any suggestions greatly
appreciated.

Thanks,
Rich

A couple of points/suggestions:

DSO will use NT authentication exclusively, mixed mode is a SQL
authentication mechanism and not relevant to AS.

You mention you have SQL2k Personal Ed on WinXP, but your code comments
refer to an NT 4.0 server. Localhost normally only refer to the local
machine.

Instead of "LocalHost" in your code, try using the name that the AS
server is registered as in Analysis Manager.

Analysis Manager uses DSO under the covers, so if it is working there
should be no extra drivers, etc that you need to setup.

--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell

In article <5BA9C41A-6977-42B5-881E-9E56BDB8425E (AT) microsoft (DOT) com>,
Rich (AT) discussions (DOT) microsoft.com says...

Hi Darren,

Thank you for replying to my post. The name of my Analysis server is the
exact same name as Sql Server. One thing that I did do is I went to
C:\Program Files\
Microsoft Analysis Services\Bin\msmdrep.mdb and opened up this mdb to
examine it since it is supposed to be the repository file (that can't be
found). I did not modify anything. But after I closed it, I could not open
Analysis Services (man, I was stressing for a minute). So I re-ran Analysis
Services SP4. Now I can re-open Analysis Services, and I can also run my DSO
code.

So now I have a new question. Is it possible to migrate the repository mdb
to sql server? There are only two tables in this repository file. An
article I read on Google on DSO stuff said that you could migrate these 2
tables to a DB in Sql Server and delete the mdb file. My question is this:
if I migrate these two tables to a DB in Sql Server, how do I reference
Analysis Services to look at the Sql Server DB for these tables?

Actually, I went back to the article, and it explains how to do the
repository migration

http://msdn.microsoft.com/library/de...erver_23hv.asp

Anyway, everything is working fine. Thanks again for your response. It gave
me the kick I need to fix this thing.

Rich

"Darren Gosbell" wrote:

The only suggestion I would make if you are going to migrate the
repository to SQL Server is to create a new database just for the
repository. It makes things a lot easier if you ever need to do disaster
recovery not to have the repository in msdb (which I have seen some
people do)

--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell

In article <9040AABD-4B06-40BA-B19D-C4215CC4D56D (AT) microsoft (DOT) com>,
Rich (AT) discussions (DOT) microsoft.com says...

Thanks for that tip. And Yes, I was thinking about creating a DB just for
the repository tables. Keep things simpler.

Rich

"Darren Gosbell" wrote: