Cannot connect to 2000 analysis services from SSMS for 2005

I am not able to connect to SQL Server 2000 analysis services from the SSMS for SQL Server 2005.

I have both domain admin and sql server 2000 admin permissions for the sql server 2000 box in question.

The error message I get is as follows:

A connection cannot be made. Ensure the server is running.

Microsoft.AnalysisServices.AdomdClient

No connection could be made because the target machine actively refused it ( system)

This is a Standard Edition install of both SQL Server 2005 and of SQL Server 2000 on separate servers.

I can connect to database engine just fine.

Any ideas about what permissions I need that I've screwed up on setting?

Thanks

S Wells

I do not believe you can connect to AS 2000 from Management Studio 2005. I think you still need the Analysis Services 2000 Manager.

Hope I'm wrong or this is fixed in SP1.

|||

I hope you are wrong too because what I need to do is to migrate the SQL server 2000 Analysis services to 2005 while leaving the 2000 intact for current production.

Thanks,

S Wells

|||

Well, what I settled for doing was to migrate the analysis services from the SQL Server 2000 instance to a SQL Server 2005 instance. It did not come over in working order (there were some issues with dimension names being changed) and now the cubes cannot be processed. Since I cannot connect to the old SQL Server 2000 analysis services using analysis manager for SQL Server 2000 on the server where SQL Server 2000 is installed (something is hosed up) and since I cannot install SQL Server 2000 Analysis services manager on my development machine while SQL Server 2005 Analysis Services is installed (via BIDS and SSMS) I can't examine the old Analysis services set up to see exactly what is going on.

So, I'm back to my original issue. Does anyone know what could cause me to get a message telling me that Analysis Services Manager on the SQL Server 2000 server cannot access the registry or that I'm not part of the OLAP administrators group?

I am in the OLAD administrators group, I am a domain admin, and I am admin on the SQL Server 2000 server itself. SQL server 2000 is at Service Pack 4. The machine it is on is running Windows Server 2003 Standard Edition at Service Pack 1.

|||

Hi Swells and others,

Did you ever resolve this issue? I am also trying to connect to Analysis Services 2000 via Business Scorecard Manager 2005 and also SQL Server Management Studio. I cannot connect via either though.

I am not getting an error message from BSM. I am simply getting a blank "Database Name" list after entering the "Server Name" with creating a new datasource.

The message I am getting from MSSMS is telling me that "the server actively refused the connection".

I can connect to my SQL2K database via the "Database Engine" connection in SQL2K5, but cannot connect via an ODBC data source in BSM.

SQL2K SP4 and AS SP4 arei nstalled on an XP machine with ADOMD.Net, MSXML4 and SQLXML 3.0.

My domain account is a member of domain admins and also a member of administrators and OLAP admins on the XP machine.

SQL 2K5 is installed on a Win2K3 virtual server with BSM Server.

Both machines are members of our domain.

Please help me resolve this problem :)

Jeremy

|||

hello,

connecting to AS2000 is not supported in SSMS.

hope this clarifies.

|||

Hi all,

Then how we will migrate AS2000 database to AS2005?

Regards,

Vinod

|||

Hi Swell,

I am also facing the same issue.. Kindly help me to sort out this issue.

Send me mail to chris_asir@.hotmail.com

regards,

Anand

|||

Gentlemen,

For step-by-step example, wherein MSSQL2k a sample database is migrated to MSSQL2k5, see my article at:

http://www.databasejournal.com/features/mssql/article.php/3564291

In this article, I address different migration scenarios with regard to MSSQL server versions (side-by-side, “straight upgrade,” and migration of existing Analysis Services 2000 databases from within the SQL Server 2005 Analysis Services platform), mentioning the fact that this provides a host of flexible opportunities for staging partial and full cutovers, simultaneous operations of different versions within other strategies, and so forth.

The approach I take in the article is, of course, a simple one, of many possible approaches. However, this will probably be useful to you in that this procedure leaves the original Analysis Services 2000 databases intact as Analysis Services 2000 databases, working with automatically created copies of the original databases in reconstructing them on the desired instance of Analysis Services 2005.

Good Luck!

Bill

William E. Pearson III
CPA, CMA, CIA, MCSE, MCDBA
Island Technologies Inc.
931 Monroe Drive
Suite 102-321
Atlanta, GA 30308

404.872.5972 Office

wep3@.islandtechnologies.com

wep3@.ssas-architect.com
www.ssas-architect.com
-- -- --

Publisher Sites:

http://www.databasejournal.com/article.php/1459531

http://www.sql-server-performance.com/bill_pearson.asp

http://www.informit.com/authors/bio.asp?a=862acd62-4662-49ae-879d-541c8b4d656f

http://www.2000trainers.com/section.aspx?sectionID=17