Error when connecting to Instance in Management Studio

Question

Post reply

Error when connecting to Instance in Management Studio

Viewing 7 posts - 16 through 21 (of 21 total)

You must be logged in to reply to this topic. Login to reply

SQLRNNR SSC Guru Points: 281324 More actions · Answer 1

Other than Steve's suggestion there is the possibility that somebody removed the "Builtin\Administrators" from this Instances Security.

Are there other instances on this server? Are they properly functioning?

Also, could you paste the screenshot of the error (is it truly just a timeout, or is it an SSPI error message)?

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

SQLRNNR SSC Guru Points: 281324 More actions · Answer 2

pbyrum (1/18/2010)

I can use Remote Desktop to this same server and use SSMS to connect and see other instances on the SQL Server, while having full admin rights to the database. No problems with those, except this SSEE instance.

Can I run any command line commands to access the database? I don't know what commands I would use, though.

I didn't see this post prior to posting my last comment.

Do you have a SQL account that does not rely on AD that you can use?

If yes, try to login with that account.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

SQLRNNR SSC Guru Points: 281324 More actions · Answer 3

As for the command line option...

There is the DAC.

http://msdn.microsoft.com/en-us/library/ms178068(SQL.90).aspx

If you can login with a SQL account though, then you would not need the DAC.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

pbyrum SSCrazy Points: 2785 More actions · Answer 4

pbyrum

SSCrazy

Points: 2785

January 18, 2010 at 1:48 pm

#1105125

Here is the error message. See attachment.

pbyrum SSCrazy Points: 2785 More actions · Answer 5

I tried connecting as:

Admin:HERMES\MICROSOFT##SSEE

And that failed. Error message:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 43 - An error occurred while obtaining the dedicated administrator connection (DAC) port. Make sure that SQL Browser is running, or check the error log for the port number) (.Net SqlClient Data Provider)

SQLRNNR SSC Guru Points: 281324 More actions · Answer 6

SQLRNNR

SSC Guru

Points: 281324

January 18, 2010 at 3:14 pm

#1105163

One last one to try - have you tried connecting as 'SA'?

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

Ignacio A. Salom Rangel SSC-Insane Points: 20443 More actions · Answer 7

you can try to connect by making are rdp connection to the server and then going to the command line and using SQLCMD -Sservername. It wil use the windows login to make a connection. If you want to know more options for SQLCMD you can type SQLCMD /?

Hope it helps.

I think you should try to connect with the SA account as Jason already suggested you.

Good luck!

My blog