BUG: Expanding Stored Procedures in Data View Window Causes GPF (237869)

The information in this article applies to:

Microsoft Visual InterDev 6.0
Microsoft Visual J++ 6.0
Microsoft SQL Server 6.5
Microsoft Visual Basic Learning Edition for Windows 6.0
Microsoft Visual Basic Professional Edition for Windows 6.0
Microsoft Visual Basic Enterprise Edition for Windows 6.0

This article was previously published under Q237869

SYMPTOMS

Clicking the plus sign to expand a stored procedure in the Data View window in either Visual Basic, Visual InterDev, or Visual J++ generates the following error message if the stored procedure contains calls to extended stored procedures that return something other than 0 or 1, such as xp_cmdshell:

Devenv.exe - Application Error The instruction at "0x412406f3" referenced memory at "0x00000006". The memory could not be "read".

CAUSE

Clicking the plus sign executes the stored procedure to enumerate the parameters and tables for the stored procedure. When the data environment tries to execute xp_cmdshell it generates an error.

NOTE: This problem does not occur with SQL Server 7.0 or later. It also does not occur under a Microsoft Windows 2000 environment.

RESOLUTION

To work around this problem, upgrade your database to SQL Server 7.0, or connect to your SQL Server 6.5 database from a Windows 2000-based computer.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce Behavior

Open a Visual InterDev project that connects to a SQL Server 6.5 database.
Create a new stored procedure with the following command:
```
EXEC Master..xp_cmdshell 'dir *.exe'
					
```
Save the stored procedure.
Click on the plus sign by the stored procedure to view its parameters and tables.

Modification Type:	Major	Last Reviewed:	11/26/2003
Keywords:	kbBug kbpending kbStoredProc KB237869