We help IT Professionals succeed at work.

SQL Server 2005 Analysis Services connection problem

dave4dl
dave4dl asked
on
Medium Priority
1,957 Views
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

Thanks
Comment
Watch Question

What is the name of your instance? What service pack are you running?
CERTIFIED EXPERT

Author

Commented:
The name of my instance is MyServ\MyServ and there havent been any service packs released for SQL Server 2005 (so no service pack).
CERTIFIED EXPERT

Author

Commented:
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/).
Commented:
Closed, 500 points refunded.
GranMod
The Experts Exchange
Community Support Moderator of all Ages

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.