January 20, 2010 at 4:25 pm
I have SSAS running on one node of a two node SQL cluster (SSAS isn't clustered though). SSAS was originally running under LocalSystem. As such it was unable to communicate with the database on the other node. I changed SSAS to run as the domain account that the other database runs under so SSAS would have the proper permissions. Once I made this change I couldn't log on to SSAS via SSMS while logged on to the node it was running on. I got the errror message, "...no connection could be made because the target machine actively refused". When I changed it back to LocalSystem I can log on, but I think I'll be back to the old problem.
The design here was by an external consultant who, of course, isn't around anymore. Any suggestions on how I can get this working and what I'm doing wrong here?
Thanks, Tim
February 10, 2010 at 12:26 pm
I had the same problem. It turned out that the SQL server browser wasn't loging on under the same account. I changed the account by going to the configuration manager ( Al programs>>SQL Server 2008>>Configuration Tools>>SQL Server Configuration Manager) double clicked on the account and changed it (in my case I changed the sql server browser to log on as localSystem). This solved my problem. Hope it helps. Please note that (I believe) this will cause your service to restart (and if it doesn't you will need to restart it for the changes to take affect.)
February 10, 2010 at 1:01 pm
Didn't read your post close enough. It looks like you already knew about changing the log on account. Sorry about that.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply