Help and Support

BUG: Transact-SQL Debugger is not Available Through Terminal Server Session

View products that this article applies to.
Article ID:280100
Last Review:October 3, 2003
Revision:3.0
This article was previously published under Q280100
BUG #: 350977 (Shiloh_bugs)
On This Page

SYMPTOMS

If a terminal server client connects to a terminal server that has SQL Server 2000 installed, the Transact-SQL debugger debugging options are not available. Debugging a stored procedure from this terminal client computer through a terminal server session is not available.

The following error message from the Microsoft Windows NT application event log on terminal server is similar to:
Unable to connect to debugger on %SQLSERVER_MACHINENAME%(Error = 0x80070057 The parameter is incorrect. ). Ensure that client side components such as SQLLE.DLL are installed and registered on %SQLSERVER_MACHINENAME%. Debugging disabled for connection 54.

Back to the top

WORKAROUND

Use Microsoft NetMeeting for remote desktop access. For additional information about how to use NetMeeting, click the article number below to view the article in the Microsoft Knowledge Base:
233175 (http://support.microsoft.com/kb/233175/EN-US/) How to Use Remote Desktop Sharing in NetMeeting

Back to the top

STATUS

Microsoft has confirmed this to be a problem in SQL Server 2000.

Back to the top

MORE INFORMATION

Steps to Reproduce Behavior

1.Install the Terminal Server service Microsoft Windows NT component by adding the Windows NT component service from Control Panel. To add the component, open Control Panel. In the Control Panel dialog box, double-click Add/Remove Programs. In the Add/Remove Programs dialog box, in the left-hand pane, click Add/Remove Windows Components. In the Windows Component Wizard dialog box, select the Terminal Service check box.
2.Install the SQL Server 2000 default instance or named instance server and client components on that terminal server.
3.In Terminal Server, click Start, point to Programs, point to Administrative Tools, and then click Terminal Services Client Creator to create terminal client files on two floppy disks.
4.Install Terminal Client on another computer by using the floppy disks you created in step 3.
5.Connect to Terminal Server by using the terminal service client tool.
6.Start SQL Server 2000 Query Analyzer, and then connect with a domain account that has administrative rights or by using a system administrator (sa) account.
7.Debug the Byroyalty stored procedure that is in the Pubs database.
8.Set the input parameter to 40, which should return 3 records; however, all the debug options such as Step Over (F10), Step Into (F11) and so forth, are dimmed.

Back to the top

APPLIES TO
•Microsoft SQL Server 2000 Standard Edition

Back to the top

Keywords: 
kbbug kbpending KB280100

Back to the top

Article Translations

 

Related Support Centers

Other Support Options

  • Contact Microsoft
    Phone Numbers, Support Options and Pricing, Online Help, and more.
  • Customer Service
    For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
  • Newsgroups
    Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.