SQL Server Developer Center > SQL Server Forums > SQL Server Data Access > Problems with connections to SQL server 2008 with windows 7 client
Ask a questionAsk a question
 

QuestionProblems with connections to SQL server 2008 with windows 7 client

  • Thursday, October 29, 2009 10:49 AMPeter Rutishauser Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I have installed windows 7 professional with sql server 2008 client tools (sql server management studio) on a client.
    If i connect to a local sql instance, the connection works correct. If i wish to connect with a remote sql server instance the connection runs into timeout if i try to connect the first time. If i try to connect the second time, third time, ...., the connection works without any problem.
    The same problem i have with visual studio 2008 solutions in the development environment. If i try to test a web application, the first time i start the debugger, the connection runs into timeout. The second time, the connection works correct.
    With windows applications, the solution cannot be started (also with connection timeout).
    The same applications and the sql server management studio work fine on a vista client.
    What is the source of this problem?
    the sql server 2008 instances are updated to SP1. 

All Replies

  • Friday, October 30, 2009 4:55 PMDan BenediktsonMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Can you paste in the full, exact error message you get on the client, when the first connection times out? And, is there anything in the SQL Server ERRORLOG (by default at c:\program files\Microsoft SQL Server\!INSTANCEID!\MSSQL\Log\ERRORLOG) that might indicate a reason for connectivity failure at the time you tried to connect?
    This post is provided 'as is' and confers no express or implied warranties or rights.
  • Saturday, October 31, 2009 10:59 AMPeter Rutishauser Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    On SQL Server, i have no error messages. On the same server, connections with a vista client work properly.
    The error message on the client:

    Cannot connect to sv-rutishauser\sqldb.

    ------------------------------

    ADDITIONAL INFORMATION:

     Timeout ist abgelaufen. Das Zeitlimit wurde vor dem Beenden des Vorgangs überschritten oder der Server reagiert nicht. (Microsoft SQL Server, Error: -2)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476

  • Monday, November 02, 2009 6:11 PMPapy NormandModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello,

    What is the edition of your SQL Server ?
    If Express, it is a well-known problem : Express is going to "sleep" after a slice of inactivity time ( about 10 minutes ) , so the 1st time, you may have a problem of connection timeout ( 30 seconds is the default i think ). Change it to 90 seconds ( especially when you are connecting remotely )

    This problem may occur for Express Edition, when the database is set to AutoClose = ON : the database is automatically closed when the last connection to it is closed. This is a feature specific to the Express Edition. You may change it to  OFF and many connection problems are disappearing ( with Sql Server Management Studio right-click on the name of the database click on properties....)

    Don't hesitate to post again for more help or explanations

    Have a nice day 
    Mark Post as helpful if it provides any help.Otherwise,leave it as it is.
  • Tuesday, November 03, 2009 7:58 AMPeter Rutishauser Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello

    Thank you for your answer.
    As you see in the title, my sql server is a 2008 server instance. I have sql server 2008 standard edition with build 10.0.2531.
    I do not understand why i have this problem only with a windows 7 client and a vista client works properly.
    Kind regards
    Peter
  • Wednesday, November 04, 2009 4:28 AMNai-dong Jin - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi,

    Please try to ping the remote instance, try to check if there's any error in the connection between the client and server.

    Besides, have you started a trace in profiler to see which steps it throw the timeout exception on while you first connect to the instance.

    Thanks.
    Microsoft Online Community Support Please remember to mark the replies as answers if they help and unmark them if they provide no help.