Connection question

I am running through a tutorial book to learn the basics on Cubes and OLAP, however I am at a part where I have to add some calculations and I get the error: 'A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running.'. The cube must be queried for you to browse data or meta data.'

And then I have tried to Deploy the project and I get this same error.

I am a beginner at this, but not really SQL Server 2005 overall. What did I miss here? I have a data source that is connecting to the SQL Server database just fine.

Thanks for the information

Hello! I have never experienced the same problem but I tried www.live.com with the same error message:

Some information about this problem can be found here:

http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/CISQL2005ASCS.mspx

Dou you have SSAS2005 and SQL Server 2005 on the same machine?

Kind regards

Thomas Ivarsson

|||I do have it on the same machine. But when I tried to connect to an Analysis Services instance, I don't find any. So I take it that has to be part of the SQL Server setup.|||

Hello again. Have you deployed a cube succesfully before this error?

If not, what kind of impersonation mode are you using for the data connection?

Regards

Thomas Ivarsson

|||

This is my first "example" cube so no, I have not yet deployed a cube to the server. This is only a development machine so it is "safe" to use. I do have a local instance of SQL Server 2005 SP2 running.

I am using the credentials of the current user for impersonation.

|||

If you go to the top level in the solution explorer in BI-Dev studio, right click, choose properties and check the deployment option in the tree(lowest level).

If you enter localhost or your computer name there and the deploy the project?

HTH

Thomas Ivarsson

|||I've always used "current service account" to deploy test cubes on my local machine.|||

I really think this has something to do with the way that this SQL Server instance is set up. I am going to work with our network guys on this. I realized that my local verion of SQL server is 2000, not 2005 as I have been developing on.

But thanks for the information.