SQL Server Denali_Exception has been thrown by the target of an invocation Solution
articleArticles 578
imageDiagrams 58
commentComments 304
loyaltyKontext Points 6374
more_vert
Issue
After I installed Visual Studio 2011 Developer Preview, the error “Exception has been thrown by the target of an invocation” will be thrown when I try to lunch SQL Server Management Studio.
Microsoft Connect site has a relevant issue: http://connect.microsoft.com/SQLServer/feedback/details/668421/denali-exception-has-been-thrown-by-the-target-of-an-invocation-during-setup.
Solution
According to the article in Connect, the issue hasn’t been resolved yet. There is a temporary resolution: using “Run as administer” option when you lunch SSMS.
It is working for me:
info Last modified by Raymond 10 years ago
copyright
This page is subject to Site terms.
comment Comments
hide_source
Anonymous
Rodrigo Pinto
access_time
13 years ago
link
more_vert
hide_source
Anonymous
Raymond
access_time
13 years ago
link
more_vert
Hi Rodrigo,
Thanks a lot for your comment.
Thanks a lot for your comment.
hide_source
Anonymous
Rodrigo Pinto
access_time
13 years ago
link
more_vert
Hi there, try this
"This happens after installing SQL Server 2012 (Code named "Denali CTP3") or later, running SSMS successfully, then (later) install VS11 Dev Preview, and then run SSMS.
Dev11 Preview improperly recognize SQL Server Denali SSMS as a version 11 application and it updates the current user’s setting in SSMS registry key during the setup. This issue occurs only when Dev11 Preview is installed after the installation of SSMS.
SQL Server 2012 SSMS has a built-in security and resiliency feature for any corrupted configuration in HKCU registry key. The corrupted registry keys can be simply deleted then SSMS automatically reconstructs it with correct values during the next startup procedure.
• Start regedit.exe
• Go to HKEY_CURRENT_USER\Software\Microsoft\SQL Server Management Studio
• Delete 11.0_Config
• Restart ssms.exe
"
from connect.microsoft.com/...
Hope it helps
Rodrigo Pinto, SharePoint MVP
www.sharepointpt.org
"This happens after installing SQL Server 2012 (Code named "Denali CTP3") or later, running SSMS successfully, then (later) install VS11 Dev Preview, and then run SSMS.
Dev11 Preview improperly recognize SQL Server Denali SSMS as a version 11 application and it updates the current user’s setting in SSMS registry key during the setup. This issue occurs only when Dev11 Preview is installed after the installation of SSMS.
SQL Server 2012 SSMS has a built-in security and resiliency feature for any corrupted configuration in HKCU registry key. The corrupted registry keys can be simply deleted then SSMS automatically reconstructs it with correct values during the next startup procedure.
• Start regedit.exe
• Go to HKEY_CURRENT_USER\Software\Microsoft\SQL Server Management Studio
• Delete 11.0_Config
• Restart ssms.exe
"
from connect.microsoft.com/...
Hope it helps
Rodrigo Pinto, SharePoint MVP
www.sharepointpt.org
here's my email stationsolutions@gmail.com
Anything more i can help you , feel free to ask ;)
Best regards
Rodrigo Pinto, SharePoint MVP
www.sharepointpt.org