Operation is not valid due to the current state of the objec

Forum for users of SQL Compare schema synchronization utility

Operation is not valid due to the current state of the objec

Postby KevinGreiner » Mon Mar 05, 2012 9:41 pm

When attempting to compare 2 database, one local and one remote, I receive the following error. I reported it several weeks ago and again today, both times using the "serious error? send a report" link. However, I have received no response yet. This error is preventing me from efficiently sync'ing my dev and testing databases.

---
Registering data sources....reading extended properties
Exception has been thrown by the target of an invocation
Operation is not valid due to the current state of the object
---

What's the next step?
KevinGreiner
 
Posts: 36
Joined: Mon Mar 05, 2012 9:38 pm
Location: United States

Postby KevinGreiner » Wed Mar 07, 2012 7:42 pm

Turns out this was a bug with SQL Compare expecting to find SQL Source Control installed when the db had extended properties indicating it was linked to a source control system.
KevinGreiner
 
Posts: 36
Joined: Mon Mar 05, 2012 9:38 pm
Location: United States

Postby Brian Donahue » Thu Mar 08, 2012 12:29 pm

Thanks for the follow-up. I'll see if I can get this changed so that the error message is more accurate.
Brian Donahue
 
Posts: 6590
Joined: Mon Aug 23, 2004 10:48 am


Return to SQL Compare Previous Versions

Who is online

Users browsing this forum: No registered users and 0 guests