Thanks for the response. All 4 are yes, and we can connect using the
users credentials fine from here in CO (where the server is). When
they try to connect across the WAN from CA they can not, however. No
firewall between the sites, so I'm curious if the Analysis Manager
uses any different protocols/ports than standar SQL connections that
may be being blocked by a router or switch.
On Fri, 25 Jul 2003 15:43:16 +0200, "Reg Besseling"
<reg.usenet.nospam (AT) epic-sc (DOT) com> wrote:
if you want to use analysis manager please make sure of the following
1. that your client has the same AS SP loaded as the server
2. that the SERVER has a share called msolaprepository$ created on
c:/program files/microsoft analysis services/bin folder
3 that the security properties on that FOLDER have olap administrators
listed for all permissions
4. that the user connecting to the server is a member of the olap
administrators group on the server
If all 4 are Yes it will work
"Darryl Carden" <darryl_carden (AT) maxtor (DOT) com> wrote in message
news:3f20510d.16431921 (AT) msnews (DOT) microsoft.com...
Server: Windows 2003 Server
SQL: SQL Server 2000 Enterprise edition + Analysis Services (sp3 on
Workstation: Win 2K
Have a user in another site trying to connect through Analysis
Services. Has no problems connecting to the server through Enterprise
Manager or Query Analizer. When trying to connect with Analysis
Services, get the "you are not a member of the OLAP Admin group" error
message. Have verified that user is a member of the group. Have
logged on at the local site using remote users credentials and had no
problems. Have tried logging on at remote site with local users
credentials and have the same problem. Have verified with security
that there is no firewall across the WAN that would block. Checked
network cores in both locations and verified no blocking of either
port 1433 or 1434. Suspect software configuration error in remote
PC's, or possible blockage somewhere in LAN, but not really sure where
to start looking. Have verified sp3 installed on workstations (both
for SQL and Analysis Services). Have also verified with DBA that
migration to SQL has been done.
Any thoughts on what else to look at would be very appreciated.