All

Sql 2000 sp4, Windows 2000 sp4 Analysis Services 8.00.194

When trying to register a server from the Analysis Manager, I get an error,
'Cannot connect to the Repository'. Anyone have any ideas on this. I can
register other servers in the Analysis Manager, just not the one I need to
work on now.

--

Thanks,

Snyper

does it a remote server?
if yes, are you a member of the olap administrators group on this server?
does the repository is in the access database or in msdb?
for access database: verify that the $repository shared folder is accessible
on the target server.


"snyper" <snyper (AT) discussions (DOT) microsoft.com> wrote

You have SP4 of SQL, but version 8.0.194 is the RTM version of AS. (ie.
no service packs applied)

Are you sure that all your AS servers are at the same SP level? You need
to have all your AS servers and the machines with analysis manager on
the same service pack.

If you try to connect using Analysis Manager to a server that is on an
different SP you can get this error. You also sometimes get the "User is
not an OLAP Administrator" error, even though they are in the correct
group.

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

In article <BBBB9968-94AA-4071-B0E5-F392FAB3B6CD (AT) microsoft (DOT) com>,
snyper (AT) discussions (DOT) microsoft.com says...

You might look at the AS Operations Guide. It tells you how to determine
what SP is installed (there are different ones between the RDBMS and AS);
and how to examine the error message you are describing.
http://www.microsoft.com/technet/pro.../anservog.mspx

--
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.


"snyper" <snyper (AT) discussions (DOT) microsoft.com> wrote

All

I did upgrade all the machines to sp4 for Analysis Manager, they were out of
synch. That was not the true problem. I had first thought it may have been a
time out issue, so I bumped that up to 240 seconds. That wasn't it. I then
thought to look at the Repository Connection String. I had attempted to
register the server and it failed, but it let me look at this information. I
noticed that the Data Source was localhost, I then changed it to my target
server, and it worked perfectly after that. I don't know if anyone else had
run into this before, but it was fun.
Before:
Provider=SQLOLEDB.1;Integrated Security=SSPI;Initial
Catalog=ASrepository;Data Source=localhost;Use Procedure for Prepare=1;Auto
Translate=True;Packet Size=4096;Workstation ID=ESHSQL02;Use Encryption for
Data=False;Tag with column collation when possible=False
After:
Provider=SQLOLEDB.1;Integrated Security=SSPI;Initial
Catalog=ASrepository;Data Source=ESHSQL02;Use Procedure for Prepare=1;Auto
Translate=True;Packet Size=4096;Workstation ID=ESHSQL02;Use Encryption for
Data=False;Tag with column collation when possible=False

Thanks for all of your help.
--

Thanks,

Snyper


"Dave Wickert [MSFT]" wrote: