VSTS Crashes when using the Compare Schema tool in SQL Server proj

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Steve Barker - 26 Aug 2008 17:15 GMT

Hi all,

I am experimenting with the new SQL Server 2005 database project type in
VSTS. It all looks pretty good so far, but when I try to compare databases
schemas, VSTS crashes. Here is the repro:

* Create an empty solution.
* Add a new SQL Server 2005 database project. (Name irrelevant, but
TestDatabase will suffice.)
* Confirm that this creates a real database in my SQL Server, called
TestDatabase_DB_{GUID}.
* Switch to Schema View in the Solution Explorer.
* Add a new table (by right-clicking), called tblTest.

Now, let’s say that I want to compare the schema to an existing database, so:

* Select the TestDatabase (top) node in the Schema View.
* Click the Compare Schema button.
* This opens a window in the main pane with a link labelled “Connect to
Databases”. Click this link.

After a delay, I get an error message saying “Microsoft Visual Studio has
encountered a problem and needs to close.” The dialog box has the option to
send an error report to Microsoft.

I’ve seen screenshots online from users that are able to use this feature,
so it must work somehow. I’d be most grateful for any suggestions. By the
way, I’ve already applied VSTS 2008 SP1.

Thanks,

Steve.

Reply to this Message

Hongye Sun [MSFT] - 27 Aug 2008 09:37 GMT

Hi Steve,

Thanks for your posting. My name is Hongye Sun [MSFT]. It's my pleasure to
work with you on this issue.

After following the reproduction, I was unable to see the crash. Instead, a
dialog named "Select Source/Target Schema" was popped up. In order to
identify and narrow down possible causes of the problem, would you please
help us to collect some information about the crash by following the
actions below?

1.    Try launch VSTS in safe mode by going to Start -> Run and type "devenv
/safemode" and see if the crash happens again.
2.    If the crash happens again, in the crash dialog box, send the error
report to Microsoft and open event viewer by going to Start -> Run and type
"eventvwr". In the event viewer window, choose application event log and
find the latest error log about VSTS and copy its content to us.
3.    Get the call stack information of the crash by using Windbg. Please
follow the instructions in
http://blogs.msdn.com/msdnts/archive/2006/11/24/how-to-debug-application-cra
sh-hang-in-production-environment.aspx.

I'll be waiting for your reply. If you have any further questions or
concerns, please do not hesitate to contact us. It is always our pleasure
to be of assistance. Have a nice day.

Regards,
Hongye Sun (hongyes@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://support.microsoft.com/select/default.aspx?target=assistance&ln=en-us.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Reply to this Message

Steve Barker - 27 Aug 2008 11:53 GMT

Hi Hongye,

I've been having a few problems with my VSTS install recently. Having
installed SP1 and ran this tool:

devenv.exe /resetskippkgs

...the database problem seems to be OK now. Thanks for your assistance.

Steve.

> Hi Steve,
>
[quoted text clipped - 49 lines]
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.

Reply to this Message

Hongye Sun [MSFT] - 28 Aug 2008 08:28 GMT

Thanks for sharing your solution with us.

It's my pleasure to work with you. Have a great day!

Regards,
Hongye Sun (hongyes@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsoft.com.

This posting is provided "AS IS" with no warranties, and confers no rights.

Reply to this Message

VSTS Crashes when using the Compare Schema tool in SQL Server proj

Free Magazines