CodeBetter.Com
CodeBetter.Com
RSS 2.0 via Feedburner
           Do you Twitter? Follow us @CodeBetter

Darrell Norton's Blog [MVP]

Fill in description here...

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


Published Mar 24 2004, 07:56 AM by darrell
Filed under:

Comments

Darrell said:

Henry - excellent, glad it helped!
# April 10, 2004 6:14 AM

Kaveendra Vithana said:

Thanks, it really worked.
# July 4, 2004 5:07 PM

Herve said:

It works. Thanx for that super simple solution
# September 17, 2004 5:54 AM

Darrell said:

Glad to help!
# September 17, 2004 7:05 AM

Dave said:

Your a star thanks..!
# November 16, 2004 3:24 AM

Phil said:

exact same problem... but the solution here doesnt work...
Could it be that Oracle being installed on the same server could conflict with SQL?
# December 15, 2004 7:09 AM

Darrell said:

Phil - not sure. I haven't messed around with Oracle in 5 years.
# December 15, 2004 7:22 AM
Check out Devlicio.us!