Article ID: 319690
Article Last Modified on 10/30/2003
APPLIES TO
- Microsoft SQL Server 7.0 Standard Edition, when used with:
- Microsoft Windows 2000 Standard Edition
This article was previously published under Q319690
BUG #: 57651 (SQLBUG_70)
SYMPTOMS
SQL Server 7.0 includes the Sqldiag.exe utility that gathers and stores diagnostic information that is intended for product support. However, if you run Sqldiag.exe on Windows 2000, you cannot gather system information that is related to the operating system (Winmsd information). Sqldiag.exe only starts the Msinfo32 interface and it does not write the information to the Sqldiag.txt file or to the output file that you specify in Windows 2000.
RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 7.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301511 INF: How to Obtain the Latest SQL Server 7.0 Service Pack
WORKAROUND
To gather the system diagnostics, execute the following command from a command prompt:
start msinfo32.exe /report c:\msinfo32.txt /categories +SystemSummary+ResourcesConflicts+ResourcesIRQS+ComponentsNetwork+ComponentsStorage+ComponentsProblemDevices+SWEnvEnvVars+SWEnvNetConn+SWEnvServices+SWEnvProgramGroup+SWEnvStartupPrograms
This command creates the output file C:\msinfo32.txt, which contains the system diagnostics.
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 7.0 Service Pack 4.
MORE INFORMATION
Microsoft recommends that you apply SQL Server 7.0 Service Pack 4 (SP4) as soon as possible if you schedule Sqldiag.exe to repeatedly run under the SQL Server Agent CmdExec subsystem, or under the SQL Server service by using the xp_cmdshell extended stored procedure.
Additional query words: sqldiag diagnostics
Keywords: kbbug kbfix kbsqlserv700presp4fix KB319690
