December 27, 2012 at 7:49 am
we are unable to open SSMS from the windows box ,however we are connecting to the server from the other server, we checked in the event viewr we did not find any error on sql ,but in system log
Component: Software Version Agent
Error: Could not read from the registry sub-key.
Cause: This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error.
how to connect to ssms from local ?
December 27, 2012 at 4:10 pm
ramyours2003 (12/27/2012)
we are unable to open SSMS from the windows box ,however we are connecting to the server from the other server, we checked in the event viewr we did not find any error on sql ,but in system logComponent: Software Version Agent
Error: Could not read from the registry sub-key.
Cause: This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error.
how to connect to ssms from local ?
Do you mean that you don't see ssms in Icon in your windows >>programs ?
Which version of SQL server you are using ?
December 27, 2012 at 11:25 pm
we are using sql 2008 R2 version , when we clicked to open the SSMS , we are uiable to connect the management studio .
December 28, 2012 at 1:08 am
SSMS fails to open, or it fails to connect to a database function, like Database Engine, Reporting Services, etc? I ask because these are two very different things.
If it opens but fails to connect, what are you trying to connect to? A database engine? Reporting Services instance? Analysis Services?
Is what you are trying to connect to on the same machine where SSMS is installed?
Does what you are trying to connect to have a named instanced?
Joie Andrew
"Since 1982"
December 28, 2012 at 2:16 am
SSMS is opening but failed to connect to database engine , it's taking long time to connect still not able to connect to any services. services are running fine .
December 28, 2012 at 2:20 am
Is SQL running on the same machine that SSMS is installed on?
What are you typing in the Server Name field when trying to connect?
Joie Andrew
"Since 1982"
December 28, 2012 at 3:32 am
yes SQL is running on the same machine , we are giving the default instance name .
December 28, 2012 at 3:38 am
Can you post a screenshot of the error that you are getting? Also, is anything listed in the SQL error log or Windows Application Event Log? You can access the SQL error log from the LOG directory where SQL was installed (ex: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG, open in Notepad).
Joie Andrew
"Since 1982"
December 28, 2012 at 4:17 am
we are unable to open the log file as it is too large , checked the memory of the sql .it is configured 65 GB and is using 69 gb . i think due to the memory it is behaving like this . is reboot solved this problem ?
December 28, 2012 at 4:57 am
A lot of memory showing up being used by SQL is normal. SQL will reserve what it can and show that memory as being used in Task Manager. If your operations allow you to restart SQL during the day you can try that. Before trying that though can you post a snapshot of the error that you are receiving when you are trying to connect?
Also, have you tried connecting via a different tool, such as sqlcmd? Just curious if it is giving you a similar error. If so, can you post that as well?
Joie Andrew
"Since 1982"
December 28, 2012 at 7:57 am
NOt showing any error in log file , when we tried to open the SSMS its showing in hung state and not opening .
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply