Preventing connection timeouts in SQL Server Enterprise Manager

Sometimes in SQL Server Enterprise Manager, when I right-click on a SQL Server to “start” it, I get this error message:



A connection could not be established to (local).

Reason: Timeout expired.

Please verify SQL Server is running and check your SQL Server registration properties (by right-clicking on the (local) node) and try again.


But after I click “Ok”, the SQL Server actually is started even though the error message says it’s not.


The solution is simple.  In SQL Server Enterprise Manager, click the Tools menu and select Options..  In the “SQL Server Enterprise Manager Properties” window that shows up, click the Advanced tab.  Change the “Login time-out (seconds):” default from 4 to 8.  Then click OK.

SQL Server Enterprise Manager Properties window with timeout set

This entry was posted in SQL Server. Bookmark the permalink. Follow any comments here with the RSS feed for this post.

8 Responses to Preventing connection timeouts in SQL Server Enterprise Manager

  1. Darrell says:

    Phil – not sure. I haven’t messed around with Oracle in 5 years.

  2. Phil says:

    exact same problem… but the solution here doesnt work…

    Could it be that Oracle being installed on the same server could conflict with SQL?

  3. Dave says:

    Your a star thanks..!

  4. Darrell says:

    Glad to help!

  5. Herve says:

    It works. Thanx for that super simple solution

  6. Kaveendra Vithana says:

    Thanks, it really worked.

  7. Darrell says:

    Henry – excellent, glad it helped!

  8. Henry Norris says:

    Works like a charm!

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>