OLAP cube builds fail after changing db 'sa' password

[Zyxt]

We had to change the 'sa' password on SQL server which houses our Project
databases, and now our OLAP cube builds fail saying authentication failed
using the 'sa' account. I also noticed that the Analysis Server Manager
tool can no longer connect, as it is still attempting to use the old 'sa'
password.

This makes sense to me, of course, as these tools are configured to use the
old 'sa' password. However, how do I reconfigure these things to use the
new password? I've been digging everywhere I can think of, and can't find
anywhere to set them. Can anyone point me in the right direction?

Thanks.
-j

 

[ecc1213]

Try running the PSComPlus.exe on the host server
If your Sharepoint access is working ok, be sure to uncheck that box.

 

[Zyxt]

Anyone have any ideas on this one?
-j

 

[Zyxt]

I did try using PSComPlus to make sure the password were okay, but that
didn't solve the problem. The actual error message I receive in the web
client when trying to run an OLAP cube build is:

-----
The cube scheduled to be built on 5/1/2006 at 09:24 failed.
(-2147221453) Cannot connect to the repository. Analysis server:
projectdb Error: Login failed for user 'sa'.
-----

The PSComPlus utility only allows usernames in the 'domain\user' format,
while Analysis Services is trying to use the 'sa' user. Doh! Must be
set somewhere else. Any other possibilities where I might look?
-j

 

[Rick Roszko]

(a) Open Analysis Manager (not Enterprise Manager).

(b) Delete the cube.

(c) After the new one is created, if users cannot access the cube, you will
need to go into Analysis Manager and drill down and locate "DataBase Roles".

(d) Click on new, type in 'group_name' (can be anything

(e) Under membership tab click on 'Add'.

(f) Under add names, pick group 'Everyone' and click on 'OK'

(g) Click on 'Cubes' tab. Click on 'Check All'.

(h) Click on 'OK' then 'Close' and Exit.

That should do it...

 

[Rick Roszko]

Oh, the Analysis Manager Problem where you can't log on. Make sure you are
signing on the server with the user in "Administrators" and "OLAP
Administrators" on both the IIS and SQL server...

I am sure I am missing something else but it escapes me at the moment...