I have the following configuration:
Visual Studio Team System 2008
SQL Server Developer Edition 2008
GDR2
on a Win XP SP3 workstation.
I have no add-ins.
All patches have already been applied for Visual Studio, Sql Server and Windows.
The event log does not show anything either.
My IDEs for Management Studio (ssms.exe) and VS (devenve.exe) keep crashing on me a few times a day. I have tried uninstallilng and reinstalling both VS2008 and SQL, but no luck.
How can I start figuring out what else is wrong and fix it?
Does it crash when you do a specific thing? Can you find any log which contains any helpful info?
The information you provided is insufficient to know what the problem is, but as a guideline you should do the following :
Have Visual Studio log its activity for troubleshooting.
Try to uninstall or turn off all addons of the IDE, some plugins can crash the whole IDE, and this is a very common cause of VS crash. or :
Use the /SafeMode option which prevent all addons from being loaded.
Download and install all the available Windows updates.
Download and install all the available updates and hotfixes for Visual Studio.
If nothing worked, you can report this to Microsoft, and wait for their feedback.
I wrote an article a while back called How to debug crashes and hangs. In it I illustrate how to determine what is Visual Studio doing during a crash, shows how to get a call stack, save a minidump and report a problem to Microsoft. If you file a bug on http://connect.microsoft.com/visualstudio/feedback and attach a call stack and minidump, chances are high that we will be able to help you.
If you'd like to investigate your problem, I suggest you read the article I linked above, get a call stack (with symbols loaded), log a connect bug and attach the call stack and minidump with heap (they will help you to attach a heap since it's a very big file).
Hope this helps,
Kirill Osenkov
Visual C# IDE QA, Microsoft
http://blogs.msdn.com/kirillosenkov
Related
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.
Please, this is driving me crazy.
SSMS was working fine. But yesterday I tried to open it and it now shows a message that reads
SSMS has stopped working, a problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available
I have googled around some solutions without avail, including uninstalling RedGate software, checking the integrity of .NET Framework installation, running as administrator and even removing and installing SSMS again. Nothing works. It just wont run.
Any help will be greatly appreciated.
You can take a look at windows event log and see if you find any additional information about the failure/crash and then proceed from there.
In Event Viewer, application log and system log contains errors, warnings and information about applications running on your system.
Looking at them may give your additional information about the crash.
This issue happens in both SSMS 17 and 18, so I am listing both answers to help both.
Step1:
//For SSMS 17
C:\Program Files (x86)\Microsoft SQL Server Management Studio 17\Common7\IDE\CommonExtensions\Platform\Microsoft.VisualStudio.MinShell.Interop.pkgdef
//For SSMS 18
C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\CommonExtensions\Platform\Microsoft.VisualStudio.MinShell.Interop.pkgdef
Rename .pkgdef extension to something else. Or remove the file.
Step2:
Delete Registry Key (created at SSMS 18 or SSMS17 at Startup using the .pkgdef file mentioned above):
HKEY_CURRENT_USER\SOFTWARE\Microsoft\SQL Server Management Studio\18.0_IsoShell_Config\RuntimeConfiguration\dependentAssembly\bindingRedirection\{8BC7AF31-B6DA-4B97-8B36-F0500DECB147}
17.6 is only in preview at the moment. Stick with 17.5 until it's released
When I run my application (WPF,VB.net 2008) on Windows XP, I get weird Windows Errors. When I installed VS2008 on the machines that got the error and debug. I got a loader lock exception, so I went into Debug and removed it. However, I still get the error when it is installed on the machine.
Is there a way to remove the Loader Lock Exception when the application is install. I do understands that it might not be the best solution, but it seems this happen only when I start an WindowsElementHost with a ReportViewer and this is causing the problem, so I don't really know what else to do with it.
All version of XP have that problem, as with 2003.
In Windows 7 and Vista I never run into that error while debugging and the installed product. The same thing applies with 2008 and 2008R2.
I've done a little bit of research and below you can find my guesses:
maybe it's a bug in the Report Viewer control itself and you should update to a later version. I've noticed that on December 2012 a new version was released (see this post), supposedly running on both .NET 3.5 and 4.0 (so it should work with VB 2008, see download page);
I've noticed that Report Viewer 2008 SP1 requires .NET 3.5 SP1 (see the download page) -- maybe an outdated version can trigger the exception you are seeing;
maybe Windows XP is not updated to the latest Service Pack or is the wrong edition -- again Report Viewer 2010 SP1 requires Windows XP SP3 (see download page) and Report Viewer 2012 does not run on Windows XP Starter Edition;
maybe it's a library used by Report Viewer that causes this exception (especially a mixed mode assembly) -- a dump or a stack trace would be helpful in this sense;
there is a comprehensive answer in this thread in the Visual Studio Tools for Office forum that lists several resources to understand this problem;
the previous link suggests that in some conditions it's safe to ignore this lock. If from your testing under Visual Studio with Loader Lock MDA disabled you see that there is no problem, you can disable the MDA in production machines using the instructions in this blog post -- basically it involves setting an environment variable and adding some lines to the app.config file (see also the documentation for Loader Lock MDA to see what the new lines should look like). I haven't tried it but I thought it may be useful for you as a last resort solution -- just be sure to test thoroughly your application to avoid undesired side effects.
To get more help, I suggest you so specify:
the version of Report Viewer you are using;
the version of .NET Framework you are targeting (in particular including Service Pack);
what Service Pack is installed for Windows XP;
any stack trace or debugging information you can gather.
I installed Visual Studio 2008 Standard Edition a month or so ago after a reformat (on Vista64, if that matters). I got it for free from one of those "Heroes Happen Here" launch events.
I then installed SQL Server 2008 Express Edition a week or so ago (we're supposed to be getting that for free in the mail but I gave up - a little too early apparently).
Before I installed SQL Server 2008 Express, when I would start up Visual Studio 2008 the splash screen would read "Visual Studio 2008 Standard Edition". Now it says "Visual Studio 2008 Shell".
I figure that for whatever reason the VS2008 skeleton that ships with SQL2008 Express has stepped on the VS2008 skeleton I had there already. I know that if you install SQL2005 on a machine without VS2005, you get a "shell" version of VS2005 with no languages installed (no C#, VB.NET, etc.)
I figure this is no big deal since at worst some registry setting somewhere is wrong and the splash screen is just confused. But am I right? Or is this something that will bite me later when VS2008 for some reason denies me some feature?
To be honest, I wouldn't tempt it. This is sort of like a knock in the engine, but the car drives fine. Then one day you get stranded on the side of the road (or maybe not.) I would suggest an uninstall and a reinstall to be safe. I've had a similar run in with Visual Studio 2008 and that's exactly what I ended up doing.
I'd leave it alone. However, if the engine in my car knocks, I'm getting it rebuilt NOW while the fix is minor, rather than waiting for the catastrophic failure (voice of experience here). :-)
My experience with this on a couple machines is that there is nothing to be concerned about. If you look at the about screen within Visual Studio it should be telling you all the correct information. If your start it from the run command using "devenv /splash" you will likely see the correct splash information displayed too. If you want to get the correct splash screen to show everytime, edit your Visual Studio 2008 shortcut and clear the value from the Start In directory.
I recently had some problems with my VS 2008, and was recommended to reinstall. To make sure that the reinstall would solve my problems, i manually uninstalled everything that could have to do with VS and SQL Server (I had the 2008 Express edition installed).
Now when I reinstall SQL Server and Visual Studio, the Server Explorer in VS is dead. When I click the menu option "View\Server Explorer", I get an error message in the Output window reading:
The Visual Studio Explorers and Designers Package ({8D8529D3-625D-4496-8354-3DAD630ECC1B}) did not load because of previous errors. For assistance, contact the package vendor. To attempt to load this package again, type 'devenv /resetskippkgs' at the command prompt.
I run the suggested command, but when I try again I get the exact same error message.
How do I solve this? As I work with the Entity Framework, it is crucial that VS can connect to my database... Any help is very much appreciated!
After looking back and forth over the internet, coming across a lot of different answers, i finally managed to get this working. This was my solution:
Close all open instances of Visual Studio.
Open the Command Prompt in an Administrator context by navigating to Start\All Programs\Accessories, right-clicking Command Prompt and choosing Run as Administrator.
Navigate to the install path of VS2008 - in my case (default on Vista x64) it was **C:\Program Files (x86)\Microsoft Visual Studio 2008 9.0\Common7\IDE**
Run the command devenv /setup. It takes a little while, but be patient.
Start Visual Studio.
After following these steps, the setup is reset to default, so you'll have to reconfigure all startup options, fonts for the text editors etc. This could possibly be helped by running devenv /resetskippkgs instead, however it did not on my machine.
I've had this issue with Visual Studio 2008 as well. Running the devenv commandline statements did not help me though. I basically had to live with it until Visual Studio 2008 Service Pack 1 came out. Since installing Service Pack 1, I haven't had any problems with the Server Explorer.
Run "devenv /setup" as described above. Now, start Visual Studio without opening any solution or project file. If Server Explorer opens at this point, delete all Data Connections and Servers from there. Now, exit and restart Visual Studio. Then, open the solution or project file and the error be gone. This worked for me.