Registered users    
MembershipMembership:
Latest New UserLatest:Andrew Stott
New TodayNew Today:10
New YesterdayNew Yesterday:9
User CountOverall:22876
Private messaging    
You must be logged in to use this module.
Top 10 posters    
NamePosts
Mariette Knap12481
Marina Roos11720
Eriq Neale2071
Michael Patrick1901
Stan Guinn1806
Robert Pearman1717
Nick Pieters1425
Stewart Brown609
Kevin D.563
Eddie Kerr534
Welcome unauthorized visitor    
If you want to join us in the discussions on this forum you need to register first. Registration is free! If you are already a registered user please login to join the forum.
Small Business Server Support Forum    
Forums > Microsoft Smallbusiness Server > SQL Server 2000
Subject: ODBC SQL Server Driver Invalid connection
Prev Next
You are not authorized to post a reply.

Author Messages
Paul Williams User is Offline
United Kingdom
Member since
9/20/2006

Registered Users
Posts: 2
7/17/2007 10:17 AM  
Hi,
 
I am having a problem with my SQL Server 2000, Since last wednesday whenever i try to connect to a database instance from a client PC i keep getting the following error message "ODBC SQL Server Driver Invalid connection". I can connect to the database from the server it's self but not from any of the clients.
Any help would be greatly appreciated.
 
Regards
 
Paul
Riaan de Wet User is Offline
South Africa
Member since
4/4/2005

Platinum Membership
Posts: 55
7/18/2007 11:35 PM  
Hi,

I'm getting the exact same error. I can connect to anoter SQL server 2000 on another Windows 2003 server on my network, but workstations cannot connect to my SBS SQL2000 linstance..

I've even tried setting up a named pipe and TCP/IP alisa using the Client Network Utility, but to no avail.

Just for interest sake, when you stop and start your SQL Server instance, do you get the following error message in your application event log?:
 
============================
Event Type:      Error
Event Source:      MSSQLSERVER
Event Category:      (2)
Event ID:      17055
Date:            2007/07/18
Time:            22:45:58
User:            N/A
Computer:      TTSBS03
Description:
19012 :
SuperSocket Info: Bind failed on TCP port 1433.
============================

If I may ask, do you have WSUS3.0 installed? Or an SQL2005 Express instance somehwere?

Cheers,

Riaan
Paul Williams User is Offline
United Kingdom
Member since
9/20/2006

Registered Users
Posts: 2
7/19/2007 12:17 PM  
Hi,
 
Yes i am getting exactly the same error message and i have also tried setting up a named pipe and tcp/ip alias but again to no avail.
I am still running WSUS2.0 at the moment and i don't have any 2005 Express Instances.
 
Cheers
 
Paul
Edwin Sarmiento User is Offline
Singapore
Member since
2/13/2007

Microsoft MVP
Posts: 128
7/21/2007 06:43 AM  
I'd look at the SQL Server logs and check the port number specified during SQL Server service startup. Do you guys have IM?
MCP MCDBA MCAD MCSD MCT MCTS MCITP : DBA MCSA
http://bassplayerdoc.blogspot.com
Need a remote SQL Server DBA?
Riaan de Wet User is Offline
South Africa
Member since
4/4/2005

Platinum Membership
Posts: 55
7/21/2007 10:42 AM  
Hi Edwin,
 
Herewith my ERROR log in The Logs folder of my main SQL Server instance (MSSQL):
 
2007-07-21 10:34:48.66 server    Microsoft SQL Server  2000 - 8.00.2039 (Intel X86)
      May  3 2005 23:18:38
      Copyright (c) 1988-2003 Microsoft Corporation
      Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
2007-07-21 10:34:48.66 server    Copyright (C) 1988-2002 Microsoft Corporation.
2007-07-21 10:34:48.66 server    All rights reserved.
2007-07-21 10:34:48.66 server    Server Process ID is 10500.
2007-07-21 10:34:48.66 server    Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2007-07-21 10:34:48.66 server    SQL Server is starting at priority class 'normal'(2 CPUs detected).
2007-07-21 10:34:49.13 server    SQL Server configured for thread mode processing.
2007-07-21 10:34:49.15 server    Using dynamic lock allocation. 󞱴] Lock Blocks, 󟘸] Lock Owner Blocks.
2007-07-21 10:34:49.21 server    Attempting to initialize Distributed Transaction Coordinator.
2007-07-21 10:34:51.37 spid2     Starting up database 'master'.
2007-07-21 10:34:51.52 server    Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-07-21 10:34:51.52 spid5     Starting up database 'model'.
2007-07-21 10:34:51.56 spid2     Server name is 'TTSBS03'.
2007-07-21 10:34:51.60 spid9     Starting up database 'pubs'.
2007-07-21 10:34:51.60 spid8     Starting up database 'msdb'.
2007-07-21 10:34:51.60 spid10    Starting up database 'Northwind'.
2007-07-21 10:34:51.60 spid11    Starting up database 'db_ControlManager'.
2007-07-21 10:34:51.60 spid12    Starting up database 'InfrasTructure'.
2007-07-21 10:34:51.60 spid13    Starting up database 'Ctrack'.
2007-07-21 10:34:51.60 spid14    Starting up database 'CtrackGazet'.
2007-07-21 10:34:51.60 spid15    Starting up database 'sqlbpa'.
2007-07-21 10:34:52.68 server    SuperSocket Info: Bind failed on TCP port 1433.
2007-07-21 10:34:52.93 spid5     Clearing tempdb database.
2007-07-21 10:34:53.04 server    SQL server listening on Shared Memory, Named Pipes.
2007-07-21 10:34:53.04 server    SQL Server is ready for client connections
2007-07-21 10:34:53.27 spid11    Recovery is checkpointing database 'db_ControlManager' (7)
2007-07-21 10:34:53.40 spid5     Starting up database 'tempdb'.
2007-07-21 10:34:53.46 spid2     Recovery complete.
2007-07-21 10:34:53.46 spid2     SQL global counter collection task is created.
2007-07-21 10:36:26.91 spid51    Using 'xpsqlbot.dll' version '2000.80.2039' to execute extended stored procedure 'xp_qv'.
 
I can only see the Bond Failed to port 1433.
 
I'm certain this is related.
 
Cheers,
 
Riaan
 
BTW, yes I do have IM, can use Skype or MSN.
Edwin Sarmiento User is Offline
Singapore
Member since
2/13/2007

Microsoft MVP
Posts: 128
7/30/2007 06:11 AM  
If you're comfortable with your registry, try this out

Add a SuperSocketNetlib\Tcp\TcpAbortiveClose value in the registry key for the MSSQLServer for the particular instance.

1. Locate, and then click the following key in the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetlib\Tcp
2. On the Edit menu, point to New, and then click DWORD Value.
3. Type TcpAbortiveClose, and then press ENTER.
4. On the Edit menu, click Modify.
5. Click Decimal, and then type 1 in the Value data field.
MCP MCDBA MCAD MCSD MCT MCTS MCITP : DBA MCSA
http://bassplayerdoc.blogspot.com
Need a remote SQL Server DBA?
Riaan de Wet User is Offline
South Africa
Member since
4/4/2005

Platinum Membership
Posts: 55
7/30/2007 10:09 PM  
Hi Edwin,
 
Yes, I'm confortable with the registry. Before I make the changes as specified I would just like to know why I'm doing this and what it is supposed to do?
 
Cheers.
 
Riaan
Edwin Sarmiento User is Offline
Singapore
Member since
2/13/2007

Microsoft MVP
Posts: 128
7/31/2007 07:15 AM  
Complete explanation is found here
http://support.microsoft.com/kb/307197

When SQL Server tries to bind back to the original port number it was using during a service restart, the port may be in use. See my blog entry regarding this at http://bassplayerdoc.spaces.live.com
MCP MCDBA MCAD MCSD MCT MCTS MCITP : DBA MCSA
http://bassplayerdoc.blogspot.com
Need a remote SQL Server DBA?
Riaan de Wet User is Offline
South Africa
Member since
4/4/2005

Platinum Membership
Posts: 55
8/07/2007 12:57 AM  
Hi,

Thanks for al that assisted. Marina's reply on my post on SuporSocket Info: Bind failed (http://www.smallbizserver.net/Default.aspx?tabid=53&forumid=14&postid=69646&view=topic) has resolved the issue.

I've liearned quite a lot from the posts to this particular (OBDC) forum.

Thanx again,

Riaan
Marina Roos User is Offline
The Netherlands
Member since
3/24/2005

Forum Admins
Posts: 11720
8/07/2007 02:11 AM  
Hi Riaan,
 
That is great. Actually it has been Edwin who gave me the idea to check those instances as we were both remoted into a server of a client of mine to look at something in SQL and we checked out this too.
Marina Roos Smallbizserver.Net AdministratorMission accomplished. We have joined the branch office to our SBS 2003 Headquarters and have the same user experience on the branch office as we have on our local  network at the Headquarters. Want to know how? Signup up for a subscription and get instant access to the article series 'How to add an additional Domain Controller from a remote office to the SBS domain'
You are not authorized to post a reply.
Forums > Microsoft Smallbusiness Server > SQL Server 2000 > ODBC SQL Server Driver Invalid connection


ActiveForums 3.7
Forum policy    
These Discussion Forums are dedicated to the discussion of the Small Business Server and related server and client software. For the benefit of the community please observe the following posting guidelines:
  1. No Advertising. This includes promotion of commercial products and non-commercial products which are not directly related to Small Business Server and related server and client software.
  2. No Flaming or Trolling.
  3. No Profanity, Racism, or Prejudice.
  4. Site Moderators have the final word on approving/removing a thread or post or comment.
Copyright 2002-2008 Concentrix b.v.    :   Page generated in 0.2656267 seconds.   :   Terms Of Use   :   Privacy Statement