exception in msvcr110_clr0400.dll - sql-server

I just unpacked my new laptop on Windows 8, and installed the latest version of Visual Studio Ultimate 2013.
Through the server explorer view I tried to add a new connexion to a sql-server database. (Connect to database button)
Each attempts to log-in finished by a crash of visual studio.
Then I tried to get more information about the issue using VS as a debugger for itself.
It seems that msvcr110_clr0400.dll thrown an exception.
Just in case here is the disassembly :
I tried and re-tried several times, checked for updates, installed an other version of vs (Ultimate2012).Any clue how to fix this ?

Require repair installation of .net 4.0 (or 4.5/4.5.1).

Related

SQL Server Data Tools 2017 for Visual Studio 2017 - Unable to start debugger error

I'm having trouble with the debugger when trying to run a simple SSIS project involving importing a small sample CSV file into SQL Server.
I have searched StackOverflow with "debugger error Microsoft.DataTransformationServices.VsIntegration" and looked at all the search results.
It looks like someone else had the same issue with VS2015 about a year ago, but it never got resolved.
Microsft SQL Server Data Tools for Visual Studio 2015 giving debugging error
I've tried looking at the Event Viewer and generated Visual Studio Logs but there's nothing there.
I get 2 error messages when I try to execute the SSIS job.
Error 1:
Unable to start debugging.
The debugger is not properly installed.
Run setup to install or repair the debugger. (Microsoft.DataTransformationServices.VsIntegration)
Program Location:
at Microsoft.DataTransformationServices.Project.DataTransformationsPackageDebugger.LaunchVsDebugger(IVsDebugger iVsDebugger, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsPackageDebugger.ValidateAndRunDebugger(Int32 flags, IOutputWindow outputWindow, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchDtsPackage(Int32 launchOptions, ProjectItem startupProjItem, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchActivePackage(Int32 launchOptions)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.LaunchDtsPackage(Int32 launchOptions, DataTransformationsProjectConfigurationOptions options)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectDebugger.Launch(Int32 launchOptions, DataTransformationsProjectConfigurationOptions options)
Error 2:
Unable to start program 'DTS'.
The debugger is not properly installed. Cannot debug the requested type of code. Run setup to install or repair the debugger. (Microsoft Visual Studio Debugger)
Program Location:
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at Microsoft.DataTransformationServices.Project.DataTransformationsPackageDebugger.LaunchVsDebugger(IVsDebugger iVsDebugger, DataTransformationsProjectConfigurationOptions options)
I had a lot of trouble getting SSDT installed and working with Visual Studio 2017 and had to resort to the solution here to get it working.
SSDT installation issue (Failed to execute EXE package.)
Has anyone come across this issue and manage to overcome it?
In the meantime, I will try reinstalling the packages in the payload folder and see if that will fix this issue.
Excuse my necromancy
I know this is an old-ish question, but there are still enough people out there that haven't transitioned to VS 2019 yet for it to be relevant. I ran into this problem again for the second time, but it was a very long time in between occurrences. I completely forgot what the issue and solutions were.
Long answer
I have documented it all here.
Short answer
Here is the short version of what I documented:
Don't rush to uninstall/reinstall Visual Studio 2017
Very carefully read the blue box on the VS 2017 SSDT download page. This is critical.
Download SSDT for Visual Studio 2017
Run the installer and pay attention to the installer to see if it warns you about older extensions or installers that may exist already. Follow the instructions provided.
Assuming you have this problem, close the installer.
Uninstall the Visual Studio SSIS, SSRS and SSAS extensions (VSIX)
Run the SSDT installer - make sure it is warning free
Proceed with the installation
This should work and solve the problem, but this is a complex issue so I cannot make a guarantee. This has worked for me twice now on two entirely separate machines (work and home).
I did able to solve the issue with SQL server 2016 and Visual studio 2015 and respective SSDT 2015. I made sure I install every time as administrator (Right click on EXE and Run as Administrator).
I followed these steps:
I uninstalled all SQL Server Management Studio, SQL Server 2017, Visual Studio 2017 with SSDT.
Deleted the folders
C:\Users\me\AppData\Local\Microsoft\VisualStudio\14.0
C:\Users\me\AppData\Roaming\Microsoft\VisualStudio\14.0
Installed SQL Server 2016 (as administrator)
Installed SQL Server Management Studio latest version (as administrator)
Installed Visual Studio 2015 (for me VS 2015 gave some missing DLL and I did repair - it started working fine)
Finally I installed Visual Studio Data Tools for 2015.
Please find the exes for installing VS2015, SSDT-2015 and SQL Server 2016 from here and you can also download them from official sites through search.
and SSMS from here
I hope this will be useful to someone.
I solved this issue by filling in the required fields in the Execute SQL Task. I was missing the value in the SQL Statement field.
The other way I got rid of this error is to set the "DelayValidation" property from False to True. But that is only a workaround until you fix the real issue.
This page was also helpful.
http://www.jamesserra.com/archive/2011/07/ssis-package-taking-forever-to-load-when-you-open-it/
DelayValidation <-- find this property in Control Flow tasks
ValidateExternalMetadata <-- find this property in Data Flow tasks
I was using VS2019 for SSIS. Just go to Debug and use option: start without debugging.
If you have to see the error where it gets failed then read logs coming in command prompt.

SQL Server Management Studio 2016: The application cannot start

I installed SQL Server Management Studio 2016. When I tried to open it gives this error. I tried uninstall and again install. Also I uninstall all Visual Studio and SQL Server and reinstall all of them but problem still continue.
How can I solve this issue?
In my case, the issue was with broken VS2015 isolated shell installation.
I resolved it by downloading and re-installing this shell from Visual Studio Isolated Shell page https://learn.microsoft.com/en-ca/visualstudio/extensibility/visual-studio-isolated-shell (which should eventually lead you to http://go.microsoft.com/fwlink/?LinkId=615451 - after filling out the survey).
Note:
I had following warnings after the VS1205 shell install. But that
did not matter, since the existing version of these components was
higher.
I had no VS IDEs installed on my computer prior to
installing SSMS 16.5.3 (or 17.1). Both had the same issue. For now I
am using only SSMS 16.5.3, since I do not have a need for 17.1
I completely remove all microsoft application and re install sql server 2016 and the reinstall ssms and ssms worked and finally I install vs17 now its working.
Problem is about to "Microsoft Visual Studio 2015 Shell(Isolated)"
We need to install vs after ssms.
Happened to me on SSMS v17.9.1.
I've repaired Microsoft Visual Studio 2015 Shell (Isolated) and the problem went away.
According to MSDN documentaion:-
An unexpected error has prevented Visual Studio from starting. This error appears when one of the following items occurs:
The integrated development environment (IDE) was not able to load Msxml3.dll.
The IDE was not able to load Mso.dll.
The IDE was not able to load DTE.olb.
The license key for Visual Studio was not created during setup.
Script blocking is turned on and not allowing scripting code to execute.
Setup for the .NET Framework, a component required by Visual Studio, failed to generate a valid native image for mscorlib.dll.
The Klez virus is present on your computer
And the article is introduced specific procedures to correct this error.
Hope helps.

Unable to open SSIS project in Visual Studio 2012 or 2013 (migration fails)

I am trying to open a solution file in Visual Studio 2013 Ultimate that includes an Integration Services project (.dtproj). Unfortunately, the migration failed for reasons that are slightly baffling to me.
The migration report contains the following error:
RecommenderJobs.dtproj: The application which this project type is based on was not found. Please try this link for further information: http://go.microsoft.com/fwlink/?prd=12395&pver=11&sbp=ProjectTypeDeprecated&plcid=0x409&clcid=0x409&ar=MSDN&sar=ProjectCompatibility&o1=159641D6-6404-4A2A-AE62-294DE0FE8301
Unfortunately, the link appears to be dead, so that's no help.
I also received the following error message when I tried to open this in Visual Studio 2012:
I've tried opening this solution in both Visual Studio 2012 Ultimate and Visual Studio 2013 Premium (which is why I tagged both). Both are on Update 5. I already tried updating all of my extensions and updates, even ones that seem like they wouldn't be directly relevant to the problem (like Visual Studio's Office tools).
I found a similar question on Microsoft's forum. The suggestion there was to upgrade my version of SSIS to the latest version. I tried to install SSDT for VS2013 as suggested, but the install failed:
When I checked the logs, it had the following error:
Error 0x80070666: Cannot install a product when a newer version is installed.
I do, in fact, have a different version installed, but it's not actually newer as far as I can tell (in fact, it launches in the Visual Studio 2010 shell), so I'm a little confused by this. The version information is below:
Microsoft SQL Server Integration Services Designer
Version 11.0.5058.0
Microsoft SQL Server Reporting Services Designers
Version 11.0.5058.0
I do also have tools related to SQL Server 2012 installed.
Based on what I've read in other posts, I'd expect to see the SQL Server Data Tools in "Add/Remove Programs," but it's not. Does anyone know why that might be?
I've also seen related questions for other types of projects, such as for a PowerShell project. (Obviously, my question has nothing to do with Powershell, but the OP there was receiving the same exact error message for a different project type). Unfortunately, the suggestions on that post didn't seem all that helpful - for example, the accepted answer there involved completely uninstalling and reinstalling Visual Studio, which would be a major pain to say the least. I'm also not all that confident that that would work for me since this problem occurs in two separate versions of Visual Studio.
Does anyone have any suggestions on what else I could try?
You likely need to install both Integration services and Business Intelligence for Visual Studio (BIDS). You can do it launching SQL Server Setup and adding features to your current SQL Server Instance.
Have a look at this one: https://guruprasadv.wordpress.com/2009/06/17/opening-ssis-package-in-visual-studio/
BIDS is the IDE (integrated into Visual Studio) that allows you to drag and drop the components and create the SSIS packages. From SQL Server 2014 on wards you won't see BIDS anymore packaged in the SQL Server Setup, so you will have to install it independently. If you need it for VS 2013 here you have the link: https://www.microsoft.com/en-us/download/details.aspx?id=42313

SQL Server Management Studio (SSMS) 2014 System.EnterpriseServices.Wrapper.dll Error

SSMS 2014 SP1 recently started throwing an error around a mismatch of the System.EnterpriseServices.Wrapper.dll when trying to connect to any database.
I had recently installed LinqPad 5 which required installing.Net 4.6.
Trying to repair SSMS did not fix the issue. Various resources online, suggesting updating the GAC and C:\Windows\winsxs\x86_System.EnterpriseServices_b03f5f7f11d50a3a_2.0.0.0_x-ww_7d5f3790 assemblies from the .Net 2.0 folder and the also did not fix the issue.
This was my solution to get my dev environment back to working as normal. Obviously it isn't ideal, so if anyone has a better solution, please share.
As an interim measure:
Uninstall .Net 4.6 from Add/Remove Programs
Reinstall .Net 4.5.1
from: https://msdn.microsoft.com/en-us/vstudio/hh487283.aspx
Restart SSMS, possibly you may need to restart your computer
If you subsequently recieve an error in Visual Studio:
Open the VS developer command prompt (C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\Shortcuts for Visual Studio 2013)
Run devenv /setup
Alternatively you could run a repair from the VS installer
I believe this is because .Net 4.6 overwrites the files in the C:\Windows\Microsoft.NET\Framework\v4.0.30319 folder, as .Net 4.x all share this folder, SSMS doesn't seem to be able to handle the updgrade. .Net 2.0 uses a different folder, hence why alot of the solutions around presumably didn't help.

Error 175: The specified store provider cannot be found in configuration - Sql Server CE

oI am building a WPF application in .net 4.0.
I have a local DB .sdf file. I am using EF to connect to the DB.
When building the application I get Error 175: The specified store provider cannot be found in configuration
I tried droping and recreating both the model and the sdf file.
I tried everything detailed in this link and the blog post it was taken from.
I cannot get this error to go away. The application runs on my machine (The error is in the edmx file, so it still runs), but when I publish it and run the installer on another computer, I get the same error in a messagebox.
My local machine is Windows 2008 R2 64bit with VS2010 installed. The machine I'm installing on is Windows 7 32bit.
Edit: Also tried this and got the same result.
I donwloaded SQL Server CE again and did a repair install, then reopned VS2010, did a build and the error went away.
I uninstalled and reinstalled and it didn't help, so I don't really know why this did, but there you go.

Resources