Microsoft KB Archive/839280

Knowledge Base

FIX: SQL debugging does not work in Visual Studio .NET after you install Windows XP Service Pack 2

Article ID: 839280

Article Last Modified on 11/2/2007

---

APPLIES TO

• Microsoft SQL Server 2000 Developer Edition
• Microsoft SQL Server 2000 Standard Edition
• Microsoft SQL Server 2000 Enterprise Edition
• Microsoft SQL Server 2000 Personal Edition
• Microsoft SQL Server 2000 Enterprise Edition
• Microsoft SQL Server 2000 Workgroup Edition
• Microsoft SQL Server 2000 Desktop Engine (Windows)
• Microsoft SQL Server 2000 Developer Edition
• Microsoft SQL Server 2000 Enterprise Edition 64-bit
• Microsoft Visual Studio .NET 2003 Enterprise Architect, when used with:
  • Microsoft Windows XP Professional

---

Bug #: 471127 (SQL Server 8.0)

Article contents

• Summary
• Symptoms
• Resolution

• Hotfix information

• Prerequisites

• Restart information

• Hotfix file information

• Status
• More Information

SUMMARY

This article includes the following information about this hotfix release:

• The issues that are fixed by this hotfix package.
• The prerequisites for installing the hotfix package.
• Whether you must restart your computer after you install the hotfix package.
• Whether the hotfix package is replaced by any other hotfix package.
• Whether you must make any registry changes.
• The files that are contained in the hotfix package.

back to the top

SYMPTOMS

After you install Microsoft Windows XP Service Pack 2 (SP2), the SQL debugging feature in Microsoft Visual Studio .NET 2003 (Visual Studio .NET) does not work. When you try to debug a SQL Server stored procedure by using the Step Into Stored Procedure option in the Server Explorer pane, you may receive the following error message:

Cannot debug stored procedures because the SQL Server database is not setup correctly or user does not have permission to execute master.sp_sdidebug. Run SQL Server setup or contact database administrator.

After you install Windows XP SP2, you may not be able to debug a SQL Server stored procedure in Visual Studio .NET that you were able to debug before you installed Windows XP SP2.

After you install Windows XP SP2, when you expand a SQL Server node for a registered server that is listed in the parent SQL Servers node of the Server Explorer pane in Visual Studio .NET, you receive the following error message:

Could not automatically discover any SQL Server instances.
Choose Register SQL Server instance from the shortcut menu if you know there are SQL Server instances on this machine.

When you try to debug a stored procedure in Visual Studio .NET, you may also notice an error message that is similar to the following in the Database Output pane:

Unable to connect to debugger on <SQL Server Computer Name> (Error = 0x800706ba). Ensure that client-side components, such as SQLDBREG.EXE, are installed and registered on <Client Computer Name>. Debugging disabled for connection 54.

For a list of previous hotfixes, see the "Microsoft SQL Server 2000 post-Service Pack 3 or Microsoft SQL Server 2000 post-Service Pack 3a hotfixes" section in the following Microsoft Knowledge Base article:

290211 How to obtain the most recent SQL Server 2000 service pack

back to the top

RESOLUTION

Service pack information

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

290211 How to obtain the latest SQL Server 2000 service pack

Hotfix information

back to the top

Prerequisites

To apply this hotfix, you should have SQL Server 2000 Service Pack 3 or SQL Server 7.0 and Windows XP Service Pack 2.
Note To resolve the problem, apply the hotfix on SQL Server 2000 because this problem is a server-side problem.

back to the top

Restart information

Restart SQL Server 2000 after you apply this hotfix.

back to the top

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

SQL Server 2000

   Date         Time   Version             Size   File name
   --------------------------------------------------------------------
   20-May-2004  14:55  2000.80.944.0     664,128  Autoplt.dll      
   20-May-2004  14:55  2000.80.944.0      78,400  Console.exe      
   20-May-2004  14:55  2000.80.944.0     315,968  Custtask.dll     
   20-May-2004  14:55  2000.80.944.0      33,340  Dbmslpcn.dll     
   08-Apr-2004  18:42                    786,432  Distmdl.ldf
   08-Apr-2004  18:42                  2,359,296  Distmdl.mdf
   10-Oct-2003  15:48                        180  Drop_repl_hotfix.sql
   20-May-2004  14:55  2000.80.944.0   1,905,216  Dtspkg.dll       
   20-May-2004  14:55  2000.80.944.0     528,960  Dtspump.dll      
   20-May-2004  14:55  2000.80.944.0   1,557,052  Dtsui.dll        
   20-May-2004  14:55  2000.80.944.0     639,552  Dtswiz.dll       
   10-Oct-2003  15:48                    747,927  Instdist.sql
   10-Oct-2003  15:48                      1,581  Inst_repl_hotfix.sql
   20-May-2004  14:55  2000.80.944.0     352,828  Isqlw.exe        
   20-May-2004  14:55  2000.80.944.0      82,492  Itwiz.exe        
   20-May-2004  14:55  2000.80.944.0      90,692  Msgprox.dll      
   19-May-2004  20:43  8.11.40209.0      209,408  Mssdi98.dll      
   20-May-2004  14:55  2000.80.944.0      62,024  Odsole70.dll     
   20-May-2004  14:56  2000.80.944.0      25,144  Opends60.dll     
   20-May-2004  14:56                     82,944  Opends60.pdb
   20-May-2004  14:55  2000.80.944.0      57,904  Osql.exe         
   20-May-2004  14:55  2000.80.944.0     279,104  Pfutil80.dll     
   10-Oct-2003  15:37                    550,780  Procsyst.sql
   08-Apr-2004  18:42                     12,305  Qfe469315.sql
   08-Apr-2004  18:42                     19,195  Qfe469571.sql
   19-May-2004  22:26                  1,104,848  Replmerg.sql
   20-May-2004  14:55  2000.80.944.0     221,768  Replprov.dll     
   20-May-2004  14:55  2000.80.944.0     307,784  Replrec.dll      
   19-May-2004  22:37  2000.80.944.0     159,813  Replres.rll
   10-Oct-2003  15:48                  1,087,150  Replsys.sql
   10-Oct-2003  15:48                    986,603  Repltran.sql
   20-May-2004  14:55  2000.80.944.0     287,304  Rinitcom.dll     
   20-May-2004  14:55  2000.80.944.0      78,416  Sdiclnt.dll      
   20-May-2004  14:55  2000.80.944.0      66,112  Semmap.dll       
   20-May-2004  14:55  2000.80.944.0      57,916  Semnt.dll        
   20-May-2004  14:55  2000.80.944.0     492,096  Semobj.dll       
   19-May-2004  23:13  2000.80.944.0     172,032  Semobj.rll
   20-May-2004  14:55  2000.80.944.0      53,832  Snapshot.exe     
   12-Mar-2004  00:10                    117,834  Sp3_serv_uni.sql
   20-May-2004  14:54  2000.80.944.0      28,672  Sqlagent.dll     
   20-May-2004  14:55  2000.80.944.0     311,872  Sqlagent.exe     
   20-May-2004  14:54  2000.80.944.0     168,001  Sqlakw32.dll     
   20-May-2004  14:55  2000.80.944.0      33,344  Sqlctr80.dll     
   20-May-2004  14:55  2000.80.944.0   4,215,360  Sqldmo.dll       
   20-May-2004  14:55                     25,172  Sqldumper.exe    
   19-May-2004  22:23  2000.80.944.0      28,672  Sqlevn70.rll
   20-May-2004  14:55  2000.80.944.0     180,792  Sqlmap70.dll     
   20-May-2004  14:55  2000.80.944.0     188,992  Sqlmmc.dll       
   19-May-2004  23:20  2000.80.944.0     479,232  Sqlmmc.rll
   20-May-2004  14:55  2000.80.944.0     401,984  Sqlqry.dll       
   20-May-2004  14:55  2000.80.944.0      57,920  Sqlrepss.dll     
   20-May-2004  14:56  2000.80.944.0   7,553,105  Sqlservr.exe     
   20-May-2004  14:56                 13,026,304  Sqlservr.pdb
   20-May-2004  14:55  2000.80.944.0     590,396  Sqlsort.dll      
   20-May-2004  14:55  2000.80.944.0      45,644  Sqlvdi.dll       
   20-May-2004  14:55  2000.80.944.0     106,588  Sqsrvres.dll     
   20-May-2004  14:55  2000.80.944.0      33,340  Ssmslpcn.dll     
   20-May-2004  14:55  2000.80.944.0      82,492  Ssnetlib.dll     
   20-May-2004  14:55  2000.80.944.0      25,148  Ssnmpn70.dll     
   20-May-2004  14:55  2000.80.944.0     123,456  Stardds.dll      
   20-May-2004  14:55  2000.80.944.0     158,240  Svrnetcn.dll     
   20-May-2004  14:55  2000.80.944.0      76,416  Svrnetcn.exe     
   20-May-2004  14:56  2000.80.944.0      49,228  Ums.dll          
   20-May-2004  14:56                    132,096  Ums.pdb
   20-May-2004  14:56  2000.80.944.0      98,872  Xpweb70.dll      

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

back to the top

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

back to the top

MORE INFORMATION

Steps to reproduce the problem

1. On a computer that is running Microsoft Windows XP or Microsoft Windows Service Pack 1 and that has Visual Studio .NET installed, start Visual Studio .NET.
2. Configure the computer to perform SQL debugging.
   
   For more information about how to set up SQL debugging, visit the following Microsoft Web site:

   http://msdn2.microsoft.com/en-us/library/s4sszxst(vs.71).aspx

3. In Visual Studio .NET, debug a SQL Server stored procedure by using the SQL debugging feature. Make sure that you can debug the SQL Server stored procedure successfully.
4. Install Windows XP SP2 on the computer, and then restart the computer.
5. Start Visual Studio .NET.
6. On the View menu, click Server Explorer.
7. In the Server Explorer pane, expand Servers, and then expand the name of the computer that is running SQL Server.
8. In the Server Explorer pane, expand SQL Servers.
   
   Note You receive the error message that is mentioned in the "Symptoms" section.
9. In the Server Explorer pane, right-click Data Connections, and then click Add Connection.
10. In the Data Link Properties dialog box, specify the details to connect to your SQL Server database, and then click OK.
11. In the Server Explorer pane, expand SQL Server name.Database name.User name.
12. If the SQL Server Login dialog box appears, enter the connection details, and then click OK.
13. In the Server Explorer pane, expand Stored Procedures.
14. Right-click CustOrderHist, and then click Step Into Stored Procedure.
15. If the SQL Server Login dialog box appears, enter the connection details, and then click OK.
    
    Note You receive the error messages that are mentioned in the "Symptoms" section.

For more information about performing SQL debugging, click the following article number to view the article in the Microsoft Knowledge Base:

316549 How to debug stored procedures in Visual Studio .NET

For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages

For more information about the terminology that Microsoft uses when orrecting software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

back to the top

Additional query words: springboard

REFERENCES

Keywords: kberrmsg kbbug kbfix kbstoredproc kbtsql kbqfe kbserver kbdatabase kbsqlserv2000presp4fix kbhotfixserver KB839280

---

Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.