Microsoft KB Archive/279080

= FIX: Sqldiag Utility Exits if SQL Server Service Is Not Started =

Article ID: 279080

Article Last Modified on 10/17/2003

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition

-



This article was previously published under Q279080



BUG #: 236743 (SHILOH_BUGS)



SYMPTOMS
The Sqldiag utility gathers and stores diagnostic information related to SQL Server, as well as the output of Microsoft Windows NT Diagnostic Report (Winmsd.exe) or Microsoft Windows 2000 System Information (Msinfo32.exe). Sqldiag is intended to expedite and simplify information gathering by Microsoft Product Support Services.

There is a change in behavior in the Sqldiag utility that ships with SQL Server 2000. If the SQL Server service is not started when Sqldiag is executed, the utility exits without collecting SQL Server errorlogs and Windows diagnostic reports. The resulting Sqldiag.txt output file contains the following line: Unable to connect to server This problem exists with both default and named instances of SQL Server 2000.



RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack



WORKAROUND
The only workaround is to manually collect SQL Server errorlogs and Windows diagnostic reports.

For additional information on the location of SQL Server errorlogs, see the &quot;Locating Directories and Files&quot; topic in SQL Server Books Online.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.

Keywords: kbbug kbfix KB279080

-

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

© Microsoft Corporation. All rights reserved.