SSAS named instance connection problems -
11-09-2005
, 04:15 AM
Hi,
We seem to have a serious connectivity issue with all our named
instances of Analysis Services 2005 RTM.
When the SQL Browser service is running under a domain (administrator)
account, attempting to deploy a BI project to the local named SSAS
instance, deployment fails with error message "a connection cannot be
made to the redirector". Changing SQL Browser to run as the local
system account seems to resolve this particular issue, however the same
error still occurs when attempting to connect to the SSAS instance by
other means, for example as a data source in a SSIS package. We
haven't been able to find a way around this latter problem.
Reinstalling the SSAS as a default instance resolves the problem.
However, on our development machines we'd like to run AS2k and AS2k5
side-by-side, and since AS2k doesn't support named instances we have no
choice in this scenario but to name our AS2k5 instances, therefore
hitting this problem. So far we've tried installing on 3 separate
(Windows XP) desktops, experiencing this same issue in each case.
I notice there have been a number of other threads apparently on this
issue (search the group for "redirector"), however all these seem to
have petered out without much discussion, and I'm a little surprised
there hasn't been more fuss about this. Perhaps, then, it's not a
universal problem, and I'd be interested to hear if there is a known
bug in the RTM or if others are not experiencing this in the way we
are; we've been running beta copies of Yukon for the last couple of
years (with named instances) and I don't ever recall having this
problem before.
Thanks,
Jon |