Microsoft KB Archive/312935

= FIX: SQL Server fails to bind TCP/IP port at startup =

Article ID: 312935

Article Last Modified on 4/7/2006

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 7.0 Standard Edition

-



This article was previously published under Q312935



BUG #: 76752 (MDAC Bugs)

BUG #: 76801 (MDAC Bugs)



SYMPTOMS
SQL Server unsuccessfully binds its server-side TCP/IP port at startup. If this occurs:


 * Clients cannot make TCP/IP connections.

-or-

 When a client computer tries to make a connection to SQL Server, the connection may fail and you receive this error message:

SQL Server Does Not Exist or Access Denied.



This article discusses one possible cause of this message. Applying the fix that is referenced in this article only helps if you are experiencing this exact same scenario. For other possible causes, see the following articles in the Microsoft Knowledge Base:

293107 PRB: TCP\IP Port in Use by Another Application

319578 PRB: Error Message:&quot;Bind Failed&quot; Occurs After IP Address Changes on a Cluster



CAUSE
Processes that are started from the SQL Server process space can hold a resource which prevents the server from being able to bind its TCP/IP port at startup. There are two scenarios that are currently known to expose this problem:
 * The execution of database maintenance plans by way of SQLAgent jobs which execute the SQLMaint utility by using the xp_sqlmaint extended stored procedure.

NOTE: This includes SQLAgent jobs that facilitate log shipping.
 * The execution of commands by way of the xp_cmdshell extended stored procedure.

To encounter this problem, the SQL Server process must terminate after the child process begins execution and must be restarted before the child process terminates.



RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix for SQL Server 2000 SP1 should have the following file attributes or later:   Date         Time   Version             Size   File name --  30-Nov-2001  12:45  2000.80.472.0      86,588  Ssnetlib.dll The English version of this fix for SQL Server 2000 SP2 should have the following file attributes or later:   Date         Time   Version             Size   File name --  14-Oct-2002  18:27  2000.80.692.0      82,492  Ssnetlib.dll The English version of this fix for SQL Server 7.0 should have the following file attributes or later:   Date         Version         Size     File name --

30-Nov-2001 2001.11.26.0    45,328   Ssmsso70.dll NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.



WORKAROUND
If you determine that the SQLMaint utility is preventing SQL Server from binding its TCP/IP listen-on port at startup, the properties of each SQLAgent job that executes the SQLMaint utility can be modified to work around the problem.

The essence of the workaround is to execute the SQLMaint executable in an operating system command shell, as opposed to executing the utility by using a call to the xp_sqlmaint extended stored procedure.

Two changes are required to each job step that executes the SQLMaint utility by using the xp_sqlmaint extended stored procedure.  Modify the job step &quot;Type&quot; from &quot;Transact-SQL Script (TSQL)&quot; to &quot;Operating System Command (CmdExec)&quot;. Change the &quot;Command&quot; associated with the job step from an extended stored procedure call to the direct execution of the SQLMaint executable as described above. <ol style="list-style-type: lower-alpha;"> Replace the string &quot;EXECUTE master.dbo.xp_sqlmaint&quot; with &quot;SQLMaint&quot; (without the quotes).</li> Remove the single quotes which encapsulate the parameter list. You must delete the opening single quote, N', and the closing single quote, ', at the end of the parameter list.</li></ol> </li></ol>

The required changes are most easily demonstrated by way of an example. Note the changes made to the following sample command.

Before Required Changes: <pre class="fixed_text">EXECUTE master.dbo.xp_sqlmaint N'-PlanID 917F24D5-D71E-41B2-A2FB-FA538954F33E -WriteHistory -BkUpMedia DISK -BkUpDB  -UseDefDir  -BkExt &quot;BAK&quot;' After Required Changes: <pre class="fixed_text">SQLMaint -PlanID 917F24D5-D71E-41B2-A2FB-FA538954F33E -WriteHistory -BkUpMedia DISK -BkUpDB  -UseDefDir  -BkExt &quot;BAK&quot;

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbbug kbfix kbsqlserv700presp4fix kbqfe kbsqlserv2000presp2fix kbhotfixserver KB312935

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.