FIX: VID Stops Responding When Accessing SP Under Source Control

This article was previously published under Q224945
This article has been archived. It is offered "as is" and will no longer be updated.
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
or
EXECUTE permission denied on object sp_OAMethod, database master, owner dbo
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:

MORE INFORMATION

Steps to Reproduce Behavior

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

Article ID: 224945 - Last Review: 10/20/2013 22:43:05 - Revision: 1.1

  • Microsoft Visual InterDev 6.0 Standard Edition
  • kbnosurvey kbarchive kbbug kberrmsg kbfix kbsecurity kbsqlprog kbvisid600fix kbvs600sp3fix KB224945
Feedback