DOC: T-SQL Debugger Server Setup Provides Incorrect Location

This article was previously published under Q166280
This article has been archived. It is offered "as is" and will no longer be updated.
The documentation for setting up Server-Side T-SQL Debugging incorrectlystates that you can find Sdi_nt4.exe and Readme.txt in the\CliSrv\Tsql\SrvSetup directory of your Visual Basic Enterpriseinstallation.

The documentation should that the Readme.txt file can be foundin the \Tools\Tsql\Srvsetup directory of your Visual Basic EnterpriseCD-ROM.

Sdi_nt4.exe is located in the CliSrv\Tsql\SrvSetup directory of your Visual Basic Enterprise Edition version 5.0 CD and under the sqdbg_ss\ directory on the Visual Basic Enterprise Edition version 6.0 CD Two. For Visual Basic 6.0, run the setup.exe found under the sqdbg_ss\ directory. For Visual Basic 5.0, on Windows NT 4.0, run the Sdi_nt4.exe setup program.
Following is the corrected version of the documentation:

Server-Side Setup

With SQL Server version 6.5 and Service Pack 1 installed, you can installand register the SQL Debugger interface and Remote Automation component onthe server. These components are located in the \Tools\Tsql\Srvsetupdirectory of your Visual Basic Enterprise CD-ROM. On Windows NT 4.0,run the setup program Sdi_nt4.exe.

NOTE: For set up on Windows NT Server 3.51, you must manually copy and register the necessary files. Complete instructions for this process are included in the Readme.txt file in the \Tools\Tsql\Srvsetup directory of your Visual Basic Enterprise CD-ROM.

(c) Microsoft Corporation 1997, All Rights Reserved. Contributions by Jon Fowler, Microsoft Corporation.


Article ID: 166280 - Last Review: 02/28/2014 08:06:09 - Revision: 1.1

Microsoft Visual Basic 5.0 Enterprise Edition, Microsoft Visual Basic 6.0 Enterprise Edition

  • kbnosurvey kbarchive kbinfo kbdocfix kbdocerr KB166280
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)