FIX: VID Stops Responding When Accessing SP Under Source Control

View products that this article applies to.

This article was previously published under Q224945

SYMPTOMS

With Security on the SQL server set to either Standard or Mixed, logging into SQL from Visual InterDev using a SQL user will cause Visual InterDev to stop responding when you try to access the source controlled stored procedures.

Visual InterDev works fine when logged in as the SA account.

When logged in as a non-dbo user, you see the following errors:

EXECUTE permission denied on object sp_OACreate, database master, owner dbo

EXECUTE permission denied on object sp_OAMethod, database master, owner dbo

Back to the top

STATUS

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

This bug was corrected in Visual Studio 6.0 Service Pack 3. For more information about Visual Studio service packs, please see the following articles in the Microsoft Knowledge Base:

194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why (http://support.microsoft.com/kb/194022/EN-US/ )

194295 HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed (http://support.microsoft.com/kb/194295/EN-US/ )

Back to the top

MORE INFORMATION

Steps to Reproduce Behavior

Make sure SQL security is set to Standard or Mixed.
From Visual InterDev, add a data connection to the PUBS database.
Add the stored procs to source control.
Refresh the DataEnvironment in the Project Explorer.
Access the data objects in the Data View (you should get the SQL Server Login dialog box).
Login with a SQL account.
Try expanding the Stored Proc node.

Visual InterDev stops responding.

Back to the top