RE: Unable to connect to SQL Server 2005, the service is running..



"Joko" wrote:

the service is still running, i can telnet to port 1433 so the port is not
being blocked
i am getting the following error when try to connect using oSQL
Unable to complete login process due to delay in prelogin Response
Thanks
Joko

"Saleem Hakani" wrote:

Can you check to make sure that SQL Server services are not shutting down
during that time? The next time this happens, can you log in using SQLCMD -A
from the command prompt and query SP_Who and see what's going on? Can you
also make sure that the default port 1433 is not being blocked by something?


HTH
Thank you,
Saleem Hakani
WWW.SQLCOMMUNITY.COM (World Wide Microsoft SQL server Community)
SQLTips, SQL Articles, SQL Forums, SQL Automation Tools/Scripts, SQL Blogs
and much more..

"Joko" wrote:

The network is OK, i couldn't even connect to sQL from the server itself.

the protocol that are enabled is TCP/IP and named pipes.

Currently i only have one server at this time

Thanks
Joko

"Saleem Hakani" wrote:

Did you check the network connection? I've heard many customers complaining
the same and upon investigation it's found that their network admin resets
the network router. If the above is not the issue then it would be helpful to
know what netlib are you using? TCP/IP, Named Pipes? Are you experiencing
this on only one SQL Server on the same switch or other SQL Servers as well?

HTH

Thank you,
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (World Wide SQL Server Community)
SQLTips, SQL Automation Tools/Scripts, SQL Articles, SQL Blogs, SQL Forums,
etc


"Joko" wrote:

Every morning, i have been experiencing this problem with my test server.
i unable to connect to SQL using Management Studio, oSQL, ODBC, Query
Analyzer from other computer at all.

I migrated SQl server from sql 2000 into SQL 2005 two weeks ago
i have iinstalled service pack 2, change the remote connection enabled.
i looked at the SQL log and i don't see anything related why the server is
not responding.

Currently the only way to be able to connect to sQL is by rebooting the
server.

Any information?
Thank you very much for your help

.

Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)
  • Re: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS
    ... I'm not seeing performance issues with the full enchilada installed, and 25 users busy hitting SQL. ... WSUS isn't difficult to uninstall - if you have WSUS v2 (installed with SBS R2) uninstall R2 from add/remove programs. ... How can anyone work with 4 instances of SQL Server on the same box? ...
    (microsoft.public.windows.server.sbs)
  • Re: SQL Resets
    ... If it were SQL that was falling short, ... The default backlog for SQL Server is 5. ... System.InvalidOperationException: Internal connection fatal error. ... From time to time, under heavy loads, we are getting resets at ...
    (microsoft.public.sqlserver.connect)
Loading