Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium


SQL Server 2005 Analysis Services connection problem

Posted on 2006-03-28
Medium Priority
Last Modified: 2008-01-09
I am trying to connect to an analysis services 2005 database via a pivot table in MS Excel 2003 (so through MS Query).

I select <new data source> under the "OLAP Cubes" tab, select "Microsoft OLE DB Provider for Analysis Services 9.0" in the olap provider dropdown box, and click the "Connect" button.  In the new dialog window I select the "Analysis Server" radio button, put in the name of my specific instance in the Server text box ("MyServ\MyServ") and click next.

I get a dialog box with the following error:

Errors in the OLE DB provider. Could not connect to the redirector. Ensure that the SQLBrowser service is running on the 'MyServ' server

I checked on the server and the service's status is "started".

So I tried to specify the local admin account in the username and password fields of that dialog box containing the "Server" textbox (referred to above).  Username: "MyServ\admin", Password: "***"

And I get the same error message.

I tried a username of just "admin" and got the same error message

I tried changing the string in the textbox to "MyServ" and a new dialog box pops up that says "The following system error occurred: No connection could be made because the target machine actively refused it. ."

Can someone please tell me what setting(s) on the MS Analysis Services computer need to be in place for this to work?

By the way, I am trying to follow the tutorial at http://msdn2.microsoft.com/en-US/library/ms244699(VS.80).aspx

Please ask for any clarification you need

Question by:dave4dl
  • 2
LVL 10

Expert Comment

ID: 16317771
What is the name of your instance? What service pack are you running?
LVL 15

Author Comment

ID: 16323502
The name of my instance is MyServ\MyServ and there havent been any service packs released for SQL Server 2005 (so no service pack).
LVL 15

Author Comment

ID: 16336040
I believe this root of this problem was the root of a couple other problems i had after migrating to 2005.  It seems the msmdpump.dll file that went out with the version of SQL Server 2005 we have (Enterprise i believe) had some problems.  MS provides an "untested" fix if you call them (see http://support.microsoft.com/kb/912459/).

Accepted Solution

GranMod earned 0 total points
ID: 16368813
Closed, 500 points refunded.
The Experts Exchange
Community Support Moderator of all Ages

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Windocks is an independent port of Docker's open source to Windows.   This article introduces the use of SQL Server in containers, with integrated support of SQL Server database cloning.
MSSQL DB-maintenance also needs implementation of multiple activities. However, unprecedented errors can hamper the database management. In that case, deploying Stellar SQL Database Toolkit ensures fast and accurate database and backup repair as wel…
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function
Suggested Courses

572 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question