I'm trying to uninstall a Managed solution within a Sandbox. The solution was for a Contact Center that we no longer use. Nothing appears when I view dependencies on the solution, so it should be good to uninstall. However, in both times that I have tried to uninstall the solution, it fails with a runtime error (will usually happen about 15-20 minutes after beginning the uninstall process).
One weird behavior that keeps happening is that even though the uninstall fails, which is stated when I view the Sandbox solution history, the solution will disappear from the Solutions menu. All the components from that Solution are still published within our sandbox CRM, but I'm now unable to access that Solution even though the delete failed.
I've had to restore our Sandbox 3 times now so that I can get the Contact Center solution to appear again after the failed uninstall attempt.
How can I successfully uninstall the managed Solution without causing a runtime error (how can I reduce the runtime of the uninstall), and has anyone else had this weird behavior where a solution disappears even though it failed to delete?
Thanks for the feedback!
Related
I'm currently having a problem where Excel will crash on multiple occasions. The ones I've noticed so far are as follows:
Debugging an error
Deleting an entire function (Note: does not occur when only deleting contents)
Other random developer type problems
My current analysis is that it was caused by the automatic Windows update KB3114564 issued this morning. I have not been able to securely link the problem to this update, however.
I am going to try moving all my code to a new workbook, which will be a pain since it's a multi-module, multi-form project.
Please let me know if you have experienced any problems of the type today/before.
Update 1:
Moving code to new workbook does not effect performance of Excel
Update 2:
It appears that the problem I had with the debugger crashing had to do with trying to multiply a string by a double. This still shouldn't have caused the DEBUGGER to crash, but at least that problem is diagnosed.
Tried several things, not sure which attempt fixed this.
I first unregistered and registerd mscomctl.ocx and mscomct2.ocx in windows\syswow64
Still had a problem; next I unchecked solver add-in in excel options.
this seemed to work.
I then checked recent KB updates and uninstalled KB3114564, re-added solver add-in and problem was resolved.
This does not keep KB3114564 from showing up again, but good enough for immediate emergency.
My installation of Visual Studio was fine previously, but has started acting weird lately. Some of the symptoms include
Visual Studio randomly hangs or crashes
Visual Studio won't start
Intellisense disappears sometimes
Plugins are not working, or are failing to start
I can't install or uninstall tools
I can't connect to source control anymore
Certain known good project types fail to load properly
Known file types don't have syntax highlighting anymore
I can't add files to a solution because the option is greyed out
I can't add, remove, or update files to a solution due to an error
I can't add or remove projects to a solution due to an error
I can't open a solution due to an error
The debugger cannot launch, or attach to processes
I can't find any templates when I try to add a new item
I can't copy/paste due to an error
A DLL required by Visual Studio is missing or corrupt
Menus are suddenly empty
Something that I know should normally work, now does not work
How can I fix this?
(This question is meant to be a canonical close dupe for these types of questions)
Visual Studio is pretty reliable, and most of us using it aren't experiencing the issues you are. It's a pretty large and complex suite of components, though, which means problems are bound to occur.
First: Restart Visual Studio and, if that fails, restart your computer
The majority of small issues are fixed by restarting Visual Studio. Some of the ones involving connectivity or services can be fixed by restarting your computer.
If this doesn't fix your problem
There's no way to guarantee that something bad won't happen to a particular installation of Visual Studio. The ways a large, complex application can become misconfigured or damaged are too varied to mention.
The effort it would take to diagnose and track down every possible cause is great. Ain't nobody got time for that. The one reliable solution—which works almost every time it's tried—is:
Reinstall Visual Studio.
Go ahead, rest your eyes for a little bit. Come back when you've come to terms with this sad fact.
…
Resigned? Okay. We're going to go through the steps to fix your problem, starting with the lowest impact, but probably least likely to work, one first. While you are attempting to fix this, keep notes! Mentally, or write them down. If you get to the last step, you'll need them.
First, let's go the easiest route and return Visual Studio to its original state. We can do this by removing all extensions and by resetting all settings.
Open the "Extensions and Updates" dialog. If you can't find it, type that into the quick launch. If you can't find that, try ctrl-q. For each installed extension, highlight it and click the Uninstall button.
Next, let's reset those settings. Make sure you export them first!
From the docs:
To export your settings
1. On the menu bar, choose Tools, Import and Export Settings. Choose the Export selected environment settings option button, and then
choose the Next button.
2. Make sure that the check boxes for the kinds of settings that you want to export are selected and all other check boxes are cleared, and
then choose the Next button.
3. (Optional) Name your settings file, enter a different path where it should be saved, or both. By default, setting files are named
Currentsettings.vssettings and saved to %USERPROFILE%\Documents\Visual
Studio 2015\Settings.
4. Choose the Finish button.
You can import them later from the same location. Now, once you've saved your settings, go back and reset them.
Tools -> Import and Export Settings... -> Reset all settings
Having reset everything, try to repro your issue. Still breaking?
Heck.
There's no doubt that you need to reinstall. Let's go the easiest route and do a repair. Do the following:
Go to Control Panel > Programs > Programs and Features
Select Microsoft Visual Studio [whatever edition] [whatever year]
Click "Change"
Click "Repair"
After you've done this, try to repro your issue. Did it still happen?
Damnit, sorry.
If you want to try a different way, you may be able to do an "overlay" reinstall. Simply run the installer directly and select "install" (if this option is available to you). You can use your original media, but I'd strongly suggest you re-download the installer. This will overlay a new version over the old, without messing up your settings. After reinstalling, try to repro. Did it?
Aw hell. Here we go.
You need to try uninstalling/reinstalling. First, though, you might want to export your settings. You should have done this for step one of this answer, but if you didn't, go back and follow the instructions to do it now.
After saving them, repeat steps 1 and 2 (from the repair instructions) and this time select "Uninstall" instead of "Change". If your issue has to do with an external component, search for it in the list of other installed applications and uninstall it as well. If you're paranoid, uninstall everything Visual Studio related. They may be out to destroy you.
Now, reinstall Visual Studio. If you've found yourself at this point, you're in deep, so don't risk installing from your original media. Download a fresh, fully updated copy from where you originally got it. For example, if you got Visual Studio via your MSDN subscription, go there and download the ISO.
Now, having reinstalled everything, try to repro. Did it happen again?
F##&ing s#!t.
Now is the time to create a bug report. Go to Connect
https://connect.microsoft.com/VisualStudio/feedback/LoadSubmitFeedbackForm
Provide as much information as possible. You need to give them all the info they ask for in the form, plus details about the bug, how to repro it, and what you did to try and fix it. Remember those notes I told you to write down? Bust them out now. I'd strongly recommend you mark your issue public, as it may be found and commented on by others with your problem.
Within a day you'll get a response. They will probably want you to turn on Visual Studio logging and repro the issue. I won't tell you how to do this here, as they will give you exact instructions for the version of Visual Studio you are running. Follow them and reply as soon as you can.
There will be one of three outcomes from this process:
They will tell you that you're doing it wrong
They will discover an outside actor causing the issue
They will discover a bug
For #1, stop doing that, and you're done. For #2, they'll probably tell you to uninstall the bad actor (e.g., remove a plugin) and go tell the people responsible about the bug (don't slack--do it). For #3, they'll triage the bug and it will be fixed sometime later. It's likely they will suggest workarounds that will at least get you moving again, if it's a true bug.
And that's it. Now, go forth and reinstall Visual Studio!
So all of a sudden a few of the computers at my job stopped working with NuGet.
The problem started with following error.
So I went over and examined the Log file which gave me following errors
Activitylog.xml (layout in the question went haywire - pastebin link)
So naturally I went over to the global config of NuGet just to find it empty. So I reinstalled NuGet, deleted the folder, reinstalled. You know the normal way of doing thing. After finding out that it didn't work, I tried it several times over with rebooting, registry cleaning, etc..
Also tried this VS2013: Error Loading Solution
So after a few tries
I managed to get to this point.
The funny thing about this issue, not all of our computers are having this problem, just certain ones. Anyway, I managed one time to get the right config that the NuGet tool window loaded correctly which gave me another error while building. (Mondays suck).
Error occurred while restoring NuGet packages: Error reading 'FILEPATH\21_MES_ACC\CSD4.WPF4.011DSP\nuget.config'.
So I'm not sure from this point how all these errors came to be and why not everybody is facing the same issue. Did someone face the same error and solved it? Do we need to reinstall things? Is this a NuGet issue? Is there a fix somewhere on the internet ?
Seems like there was an invisible whitespace in the nuget config file which was causing havoc
Suddenly I'm getting an odd error popping up every few minutes.
'Periodic workspace save.' has encountered a problem.
Could not write workspace metadata '{workspace}.metadata.plugins\org.eclipse.core.resources.snap'.
I've checked and the file is there. It's not marked "read-only".
Nothing's changed recently. I am on a Citrix VM running Windows 7 and my workspace is on a mapped drive. However, this setup has been running fine for over a year.
Any ideas?
I ended up creating a new workspace and moving my projects over there. Fortunately there weren't many (nor did I have too many snippets) and I could recustomize the way I wanted.
This is not a very good solution, however, and I'd love to see a better way to fix this issue.
while doing the build of my dontnet 4.0 project setup i'm getting following errors
An error occurred generating a bootstrapper: Unable to finish updating resource for E:\project\Setup\Debug\setup.exe with error 8007006E E:project\Setup\Setup.vdproj Setup
General failure building bootstrapper E:\project\Setup\Setup.vdproj Setup
Unrecoverable build error E:\project\\Setup\Setup.vdproj Setup
I am using dotnet framework 4 and MSVS 2010.
This happens because The .NET framework version required by the setup project is different than the .NET framework version targeted by the application.
To change verify this:
In Solution Explorer, click the Setup project.
On the View menu, point to Editor, and then click Launch Conditions.
Click .NET Framework.
In the Properties window, change the Version property to the version of the .NET Framework that you want the Setup project to check for and install.
And also you need to Make sure that the Setup.exe program also checks for and installs the correct version of the .NET Framework.
Right click on the setup project -> Properties -> Prerequisites -> Select the correct ones.
When I turn McAfee real-time scan off, it works. I spent 2 hours on figuring this out :(
I googled a lot on this issue after trying all i just disabled my antivirus(NPAV) and this issue was solved.
turning off mcafee real time scanning worked for me as well on Windows 8.1
Here is yet another solution, this one is unlike the rest...
We recently added NTFS replication to our build tree root to provide some additional data redundancy and to begin to sync our old build machine with the new server. The NTFS replication caused some projects to fail with the exact same three error reported, and yet other projects work just fine. Set the replication on only run at night and the problem stopped occurring...
K
I got the same error when I changed targeted framework to 4.0 but neglected to change prerequisits for click once from 3.5 to 4.0 as well.
Fixing prerequisits resolved the problem.
Instead of disabling the Anti-Virus, I would suggest to just create an exclusion for your Solution Folder. See documentation if you are using Windows Defender. Microsoft Support
I've just had this same error and then realised Dropbox was running. I closed Dropbox and then the build completed successfully.
Thank you qwerty13579! How stupid of me, the solution is obvious. I have tried all sorts of things suggested over the internet, and even with the most recent version of VS Community 2017 (15.9.9), the bootstrapper failure pops up erratically, but with increasing frequency, to the point of frustration this past week. The principle: It doesn't succeed reliably, so it also doesn't FAIL reliably. The solution: Click the Publish Now button and watch the output panel. When it's that clear that it's failing, click the Publish Now button again immediately. Keep at it until it succeeds! Each round only takes a couple of seconds, much less time that it takes to re-build, take down anti-virus, and all that fancy stuff.
In my case, I traced the problem to an incorrectly dated setup.exe file in the bin\Release\app.publish folder of my application. When it fails, Publish Now creates an setup.exe that's two years earlier than the current day. When it succeeds, the setup.exe file is correctly dated.
Got the same problem. I disabled Windows Defender real-time protection and it worked. I also added the folder where the solution is saved in exclusions for Defender, and that allowed me to publish as well.