February 20, 2006 at 11:40 am
Just installed analysis services on a cluster. however when I log on to analysis manager and try to perform a registration i get following message
errors occurred while connecting to 'servername'
cannot open connection to analysis server 'servername'
i am trying it on the clustered node itself. also tried from a client but doesnt work. I thought it might be because MSQLServerOlapService is not running. When I try to bring up the service I get the following error message
'The MSSQLServerOlapService' service on local computer started and then stopped. Some Services stop automatically if you do not have any work to do, for example performance logs and alerts service'
any idea whats happening here?
thanks
February 20, 2006 at 4:40 pm
I know this is a generic response, but make sure you have at least SP 3a installed. This is usually one of the first recommendations you get around here, and it actually solved a lot of problems for me when I was installing/getting setup around here.
It couldn't hurt to look into SP 4 while you're at it.
Good luck!
February 21, 2006 at 7:08 am
thanks for the response. Infact we at SP 4 at this point. The error message that I get in the event viewer when starting mssqlserverolapservice service is as follows:
Cannot change the server's start directory to T:\Program Files\Microsoft Analysis Services\Data
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I wonder why is it trying to look at T drive? when I look at cluster resources in cluster admin T drive is mapped as SQL-AS Cluster Group Disk. however i dont see a T drive in windows explorer. Any thoughts?
February 21, 2006 at 7:34 am
You mentioned this is one a cluster. I assume you are using Microsoft Cluster Services (MSCS). Is this an active-active or active-passive? Is it possible that the T drive is on the other cluster member and perhaps SQLAS is trying to connect to a drive letter that may be failed over to another cluster member?
In MSCS you can fail over individual resources, I believe.
-- J.T.
"I may not always know what I'm talking about, and you may not either."
February 21, 2006 at 9:08 am
Yes its active-passive cluster. I finally got the mssqlserverolapservice service to run. however when I try to register the server within analysis manager I get same error message
cannot open connection to analysis server ''servername''
mssqlserverolapservice is running under local system account. where as SQLServer is running under a different domain user account.
whats happening?
February 21, 2006 at 9:23 am
Is the SQL server running a named instance by any chance or is it running on a different port than 1433?
-- J.T.
"I may not always know what I'm talking about, and you may not either."
February 21, 2006 at 11:06 am
well let me describe the environment. i have two clustered nodes dc01 and dc02. sql server instance name is 006-pm2-sql. i am not sure what port its running on. how do I tell that?
February 21, 2006 at 11:24 am
Well, if you don't know the port was changed then it likely wasn't. If all SQL utils connect without any additional information then you can be pretty sure it is on 1433. The are are several ways to tell. Try to telnet to port 1433 and see if you get a response or a time out. A response means it is listening, a timeout means it isn't.
Now, you are referencing the server name in SQLAS as dc01\006-pm2-sql or dc02\006-pm2-sql or by the cluster name/ip?
Whatever you are typing into the server name box in SQLAS, can you use that same name to connect to the server using SQLQA?
-- J.T.
"I may not always know what I'm talking about, and you may not either."
February 22, 2006 at 7:10 am
Well I am little confused. Perhaps someone can help me understand. I have a two node cluster. Node1 = dbacl01 node2=dbacl02 and sql server instance name = 006-pm2-dbasql .
I am unable to register the sql server instance 006-pm2-dbasql in the analysis manager. however while I was logged into active cluster node dbacl01 via remote desktop i was able to register dbacl01 in the analysis manager. i am confused how can I register dbacl01 in the analysis manager and not the actual sql server instance 006-pm2-dbasql? can someone help? i am not able to do a query analyzer session to dbacl01 so how come it got registered in analysis manager?
February 22, 2006 at 2:04 pm
The first step may be to verify the SQL instances running on each node. If active-passive, they should only be running on the active node.
Easiest way to tell that I know is to look at the services list in computer management.
Look for MSSQLSERVER entries. A default instance will appear as MSSQLSERVER and a named instance will appear with a $. For example, MSSQLSERVER$006-pm2-dbasql.
The next thing to do might be to check DNS resolution. Make sure that dbacl01 and dbacl02 are resolvable as NetBIOS names from the machine running SQLAS. You may find that dbacl01 doesn't resolve but dbal01.domainname.com does. This could be a problem.
-- J.T.
"I may not always know what I'm talking about, and you may not either."
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply