Home Dashboard Directory Help
Search

Cannot access a disposed object. Object name: 'ModelStore'. by g4j


Status: 

Active


20
0
Sign in
to vote
Type: Bug
ID: 769514
Opened: 11/1/2012 2:59:24 PM
Access Restriction: Public
2
Workaround(s)
view
14
User(s) can reproduce this bug

Description

Got
"Cannot access a disposed object. Object name: 'ModelStore'."
From Visual Studio after trying to run a schema comparision between a database project under source control and a Local database. The database project does build.
Details
Sign in to post a comment.
Posted by Mart76 on 8/7/2013 at 8:24 AM
Restarted SSDT as mentioned in the workarounds section and now
"Cannot access a disposed object.
Objecte name:
'Microsoft.VisualStudio.Data.Tools.Package.DataToolsOperations.Slot'

I'll try re-installing...
Posted by Mart76 on 8/7/2013 at 8:20 AM
Same issue with SSDT 2012, only experienced it after a recent upgrade.
Posted by Gavin Campbell on 7/24/2013 at 7:17 AM
Also occurs when F5-deploying a project to the VS2012 localdb\projects instance
Posted by ZbR on 7/1/2013 at 2:20 AM
Hello,
I can reproduce this issue on this configuration:

Microsoft Visual Studio Ultimate 2012
Version 11.0.60610.01 Update 3
Microsoft .NET Framework
Version 4.5.50709

Installed Version: Ultimate

Architecture and Modeling Tools 04940-004-0038003-02322
Microsoft Architecture and Modeling Tools
    
UML® and Unified Modeling Language™ are trademarks or registered trademarks of the Object Management Group, Inc. in the United States and other countries.

LightSwitch for Visual Studio 2012 04940-004-0038003-02322
Microsoft LightSwitch for Visual Studio 2012

Office Developer Tools 04940-004-0038003-02322
Microsoft Office Developer Tools

Team Explorer for Visual Studio 2012 04940-004-0038003-02322
Microsoft Team Explorer for Visual Studio 2012

Visual Basic 2012 04940-004-0038003-02322
Microsoft Visual Basic 2012

Visual C# 2012 04940-004-0038003-02322
Microsoft Visual C# 2012

Visual C++ 2012 04940-004-0038003-02322
Microsoft Visual C++ 2012

Visual F# 2012 04940-004-0038003-02322
Microsoft Visual F# 2012

Visual Studio 2012 Code Analysis Spell Checker 04940-004-0038003-02322
Microsoft® Visual Studio® 2012 Code Analysis Spell Checker

Portions of International CorrectSpell™ spelling correction system © 1993 by Lernout & Hauspie Speech Products N.V. All rights reserved.

The American Heritage® Dictionary of the English Language, Third Edition Copyright © 1992 Houghton Mifflin Company. Electronic version licensed from Lernout & Hauspie Speech Products N.V. All rights reserved.

Visual Studio 2012 SharePoint Developer Tools 04940-004-0038003-02322
Microsoft Visual Studio 2012 SharePoint Developer Tools

Microsoft Team Foundation Server 11 Beta Power Tools 11.0.50321.0
Power Tools that extend the Team Foundation Server integration with Visual Studio.

Microsoft Visual Studio Process Editor 1.0
Process Editor for Microsoft Visual Studio Team Foundation Server

NuGet Package Manager 2.6.40627.9000
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

PreEmptive Analytics Visualizer 1.0
Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.

SQL Server Data Tools 11.1.30618.1
Microsoft SQL Server Data Tools

Visual Studio 11 Editor Extension 1.0
Information about my package

Web Developer Tools 1.2.40308.0
Microsoft Web Developer Tools contains the following components:
Page Inspector: Tool that offers an efficient way to decompose Web Applications and diagnose front-end issues.
Web Publishing: Extensions required for Web Publishing for both hosted servers as well as on premises.
Web Form Templates: Includes the default templates for Web Form Applications.
Editor Extensions: Includes HTML, CSS, and JS editor extensions that greatly enhance the development experience.


I perform comparison with database:
Microsoft SQL Server Express Edition with Advanced Services
10.50.2500.0
Posted by Microsoft on 11/13/2012 at 2:59 PM
We are unable to reproduce this issue with the information provided.
Posted by Microsoft on 11/6/2012 at 2:21 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 11/1/2012 at 11:24 PM
Thanks for your feedback.

In order to fix the issue, we must first reproduce the issue in our labs. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a simple repro project so that we can conduct further research?

Please submit this information to us within 3 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 11/1/2012 at 3:51 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
Posted by StuartDunkeld on 5/17/2014 at 3:02 AM
This started happening after I upgraded Visual Studio 2013 to Update 2. Running a Repair install on the latest SSDT seems to have fixed it,
Posted by KeesCBakker on 5/1/2013 at 7:33 AM
Not really a workaround, but a reboot of Visual Studio always fixes the problem for me.