SQL Server 2005 Analysis Services connection problem

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

LVL 15
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

What is the name of your instance? What service pack are you running?
dave4dlAuthor 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).
dave4dlAuthor 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/).
Closed, 500 points refunded.
The Experts Exchange
Community Support Moderator of all Ages

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.