Exception has been thrown by the target of an invocation
bmarzano
Posts: 5
Hello,
New to the forum here, and just purchased a few Red Gate tools. Looking for some help. I've installed SQL Source Control 3 on a Windows 7 machine with SQL Server 2005 SSMS. When starting SSMS, I get the error message: Exception has been thrown by the target of an invocation. As of yet, I've been unable to use the Source Control at all due to this error. Any help is greatly appreciated!
Thanks!
Brian
New to the forum here, and just purchased a few Red Gate tools. Looking for some help. I've installed SQL Source Control 3 on a Windows 7 machine with SQL Server 2005 SSMS. When starting SSMS, I get the error message: Exception has been thrown by the target of an invocation. As of yet, I've been unable to use the Source Control at all due to this error. Any help is greatly appreciated!
Thanks!
Brian
Comments
It's hard to say the cause without seeing the full error - if you could send the details over to support@red-gate.com with F0060374 in the subject line we can see if there are some helpful details.
Based on the initial message you gave though, the first thing I would suggest is (re)installing .NET 3.5 SP1 from here to see if it helps.
Redgate Software
The exception appears to have to do with SourceGear Vault/Fortress. I have previously had Vault installed, but it was uninstalled long before I installed SQL Source Control. I've reinstalled it and that didn't resolve the issue. I'm working with support now, ticket F0060382, but so far no luck. Thanks for any help anyone can provide out there!
Looking in the log file, here's the full exception:
If you go to c:\users\<your username>\appdata\local\red gate\sql source control 3\, you should see a "LinkedDatabases.xml" and maybe a "TableDataConfigs.xml" file.
Can you close down SSMS, then move both of those files elsewhere (such as on to your desktop). Can you then start up SSMS again, and try linking your database back to whichever source control system you're using?
Does that seem to fix it?
Redgate Software
Can you check if you also have a SQL Source Control 2 (or 1!) folder with the same file? Perhaps it's spotting an old file and importing the settings across for v3...
If so, delete the old files, then repeat the process you just did.
Redgate Software
Redgate Software