SSMS not opening

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2008 » SQL Server 2008 - General » SSMS not opening

11 posts, Page 1 of 2

1 2 »»

SSMS not opening

Rate Topic

Display Mode

Topic Options

Author

Message

ramyours2003

Posted Thursday, December 27, 2012 7:49 AM

Old Hand

Group: General Forum Members
Last Login: Yesterday @ 8:08 AM
Points: 358, Visits: 1,482

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 ?

Post #1400621

@SQLFRNDZ

Posted Thursday, December 27, 2012 4:09 PM

SSC-Addicted

Group: General Forum Members
Last Login: Yesterday @ 4:05 PM
Points: 412, Visits: 857

ramyours2003 (12/27/2012)

Do you mean that you don't see ssms in Icon in your windows >>programs ?

Which version of SQL server you are using ?

--SQLFRNDZ

Post #1400751

ramyours2003

Posted Thursday, December 27, 2012 11:25 PM

Old Hand

Group: General Forum Members
Last Login: Yesterday @ 8:08 AM
Points: 358, Visits: 1,482

we are using sql 2008 R2 version , when we clicked to open the SSMS , we are uiable to connect the management studio .

Post #1400798

Joie Andrew

Posted Friday, December 28, 2012 1:08 AM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Monday, May 06, 2013 5:58 AM
Points: 535, Visits: 1,010

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"

Post #1400818

ramyours2003

Posted Friday, December 28, 2012 2:16 AM

Old Hand

Group: General Forum Members
Last Login: Yesterday @ 8:08 AM
Points: 358, Visits: 1,482

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 .

Post #1400835

Joie Andrew

Posted Friday, December 28, 2012 2:20 AM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Monday, May 06, 2013 5:58 AM
Points: 535, Visits: 1,010

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"

Post #1400838

ramyours2003

Posted Friday, December 28, 2012 3:32 AM

Old Hand

Group: General Forum Members
Last Login: Yesterday @ 8:08 AM
Points: 358, Visits: 1,482

yes SQL is running on the same machine , we are giving the default instance name .

Post #1400854

Joie Andrew

Posted Friday, December 28, 2012 3:38 AM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Monday, May 06, 2013 5:58 AM
Points: 535, Visits: 1,010

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"

Post #1400855

ramyours2003

Posted Friday, December 28, 2012 4:17 AM

Old Hand

Group: General Forum Members
Last Login: Yesterday @ 8:08 AM
Points: 358, Visits: 1,482

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 ?

Post #1400864

Joie Andrew

Posted Friday, December 28, 2012 4:57 AM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Monday, May 06, 2013 5:58 AM
Points: 535, Visits: 1,010

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"

Post #1400872

« Prev Topic | Next Topic »

11 posts, Page 1 of 2

1 2 »»

Permissions