I have installed SQL Server 2005 and Analysis Services 2005 on a brand new
machine using the release version.

I created an instance "REPORTING" on both SQL Server and Analysis Services.

I am trying to connect through SQL Management Studio to Analysis Services
but I get an error message.

"A connection cannot be made to redirector. Ensure that 'SQL Browser'
service is running. (Microsoft.AnalysisServices.AdomdClient)
No connection could be made because the target machine activity refused it"

I have changed the SQL Browser and SSAS to be using Network Account and have
enabled TCP/IP on the Protocol for Reporting. But none of this helped.

What do I need to do to get this to work?

Thanks

I found a previous post that informed to change to local user account.

Does this mean that a local user account must be used to connect to AS?

I'm going to be deploying on a server and I don't want to have to link up a
specific user Account, I would like to use a system account.

"JayneK" wrote:

Are you by any chance running on a laptop that is intermittantly
connected to a domain? I am in this situation and am seeing similar
intermittent issues, in my case it only happens when I am disconnected
from the network so it should not affect a normal server.

I think in this situation it has to do with logging on using cached
domain credentials, but it also seems to depend on when the AS service
was started. I think if the AS service could contact the domain
controller when it started up it will work OK against cached domain
credentials. I suspend my laptop when I travel between home and the
office, so it is hard for me to keep track of when I last rebooted.

If I have to start up my machine away from the office I have found the
following work around.

I am running WinXP and I hold the shift key down, right click on
Management Studio or BIDS and select the "Run as..." option. This allows
me to run either of these apps using the credentials of a local user,
even though I am logged on to my machine with my cached domain
credentials.

When I can figure out a simple set of steps to reproduce this issue I
plan to log it with MS, but it is a pain to test as you have to connect,
restart, disconnect, restart and at the moment I am working off site for
the next few weeks.

--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell

In article <7D80E9EB-A8D2-4996-AD5C-03600282DDFD (AT) microsoft (DOT) com>,
JayneK (AT) discussions (DOT) microsoft.com says...

This is a known bug that impacts named instances. You should be able to
connect to default instances disconnected from the network.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Darren Gosbell" <jam (AT) newsgroups (DOT) nospam> wrote

Yeah, but I still have AS2k as my default and probably will need to keep
it for a little while yet. The "Run As" work around is not too bad, but
do you know if this bug is likely to be fixed in SP1?

--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell

In article <uh58ZpP$FHA.344 (AT) TK2MSFTNGP11 (DOT) phx.gbl>,
dwickert (AT) online (DOT) microsoft.com says...