An internal error occurred during: "Initialize metrics". com/genuitec/eclipse/core/gsdc/GSDCController - myeclipse

When I run myeclipse 2015 stable cn 1.0, I got the following error message:
An internal error occurred during: "Initialize metrics".com/genuitec/eclipse/core/gsdc/GSDCController
How do I resolve this problem?

Do you just see this in the log or do you see an error dialog as well, and is this something you see on every workspace start?
If you look at the Error Log, can you find the stack trace corresponding to this and paste it here? Alternatively, do post at http://myeclipseide.com/forums for additional support.
Update (Sep 22, 2017): This issue has been fixed in version 2017 CI 8 of Webclipse / Angular IDE / Darkest Dark / MyEclipse. If you are using an earlier version, as pointed out below, the problem is caused by inability to write to your Eclipse installation. Re-installing into a location which does have write access would be the best approach, though you can run as Administrator on Windows too.

Try to reinstall.
I had this problem with Eclipse, not MyEclipse, and it turned out that it was installed by another user in Program Files. Now I installed it at default location, under my user directory, and this error doesn't show anymore.
Also I manage to run this "bad" installation as administrator without such problems.

I also encounter this problem but it happen in Eclipse.
I think this link may help you.
https://www.genuitec.com/forums/topic/initialize-metrics-has-encountered-a-problem/
General speaking, The problem is most likely caused due to the plugins not having full write access to your workspace or the Eclipse installation
so, you just do this: Run Eclipse as an administrator!

I also encounter this problem in MyEclipse.
Since last Month, I reinstall the system but the disk E.
After install the new system, the disk E turned into disk D.
So I modify the data myeclipse.ini and configuation/config.ini. I modify the E into D.
Run MyEclipse got the following error message.
After I change back to the primary data and Move the MyEclipse to the new disk E. After it's OK.

Related

Eclipse locks up PC on first launch

I've just downloaded Eclipse on elementary OS and attempted to launch it. After doing so, I saw the loading screen for a few seconds before it disappeared and left me with the desktop. Since then, my computer (an old Dell with 4GB of RAM and an Intel Core Duo) has been very unresponsive and the disk activity indicator is almost constantly lit up. I've been looking at the desktop for around 30 minutes now! How can I solve this problem and launch Eclipse?
EDIT: Running eclipse -clean from the command line produces the following error: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
First, you might review your installation steps. If nothing is obviously wrong, check the following:
check for any error logs
check that you're using the proper Java version
make sure that there's enough memory allocated for Eclipse (see the eclipse.ini file)
as a last resort, try reinstalling it
See also the following guide for installing on Elementary OS: how to install
If that's not working submit more details of your specific problems.
NOTE: You may have to find the right Java and install it "by hand" rather than relying upon the distribution's package manager. You can "point" Eclipse at the right Java by editing the .ini file.
Some related links are as follows:
a similar symptom related to multiple screens and/or corrupt workspace
General trouble-shooting related to your issue and symptoms

Microsoft Visual Studio 2012 has stopped working (solutions on Stack Overflow not working)

Error message:
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.
This was the error message I got when I tried to launch Visual Studio 2012 on my Windows 8.1 system. There is no other information to act upon other than this, which is rather the same as "We don't know what's wrong. We will tell you if we know (but I don't think we do)". It was actually working before it just decided to stop.
The last configuration I made before it began to show this error was that I selected the option to load the last solution whenever I launch Visual Studio, and this was done in the options dialog. I don't think that could have caused Visual Studio to suddenly crash. The previous error message included something that had to with a change in configuration.
I have checked that ActivityLog.xml file in.
There were basically four errors:
Construction of frame content failed. Frame identifier: ST:0:0:{74946827-37a0-11d2-a273-00c04f8ef4ff} Frame caption: Exception details: System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) at Microsoft.VisualStudio.Shell.Interop.IVsShell5.LoadPackageWithContext(Guid& packageGuid, Int32 reason, Guid& context) at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.GetPackage() at Microsoft.VisualStudio.Platform.WindowManagement.WindowFrame.ConstructContent()
SetSite failed for package [Visual Studio Component Model Host Package]
End package load [Visual Studio Component Model Host Package]
End package load [Microsoft.VisualStudio.Editor.Implementation.EditorPackage]
I have searched on Stack Overflow, Bing and Google. The solutions I got from there didn't work. Some had to do with registry settings, deleting keys, etc. I even disabled all the extensions from the registry. There was a time it was showing another message that "Object reference was not set to ...".
I don't know what to do. The only solution I have not tried is the one that I should download the updates. Update 4 is about 2 GB. That will take me, at least a week to download. Is there anything I can do?
PS: I tried to uninstall it. It does absolutely nothing. From the Control Panel, there's only the option to change. Clicking it seems to do something but nothing appears. I tried running from the set up from the .iso file. It shows nothing, too. How can I fix this problem?
There's probably nothing we can help you with here, my view is that you need to reinstall VS. If you cannot uninstall or repair it then you should contact Microsoft.
I am able to fix this problem by installing latest version of of .NET Framework. May be helpful for others as well.

Windows 8.1 / Windows 10 breaks my ASP.NET / IIS : "Service unavailable"

With Windows 8.1 finally released to MSDN/Technet today I came across the following issue running my ASP.NET application after doing an in place upgrade with Win 8.1 RTM:
Service Unavailable
HTTP Error 503. The service is unavailable.
The AppPool has died and shows a status of Stopped
The IIS log has nothing
There's a clue is in the Windows Application log which contains this error
The Module DLL C:\WINDOWS\system32\inetsrv\rewrite.dll failed to load. The data is the error.
How can I recover my IIS to make it work again?
It looks like a simple uninstall and re-install of the rewrite module will do the trick.
Edit: As others have said - try a repair first - if it works then that should be faster.
It doesn't look like the Microsoft Web Platform Installer is able to uninstall it so just go to Programs and Features to uninstall it.
You'll find it listed as IIS URL Rewrite Module 2 and just click the Uninstall button on top.
Then reinstall it from here:
http://www.iis.net/downloads/microsoft/url-rewrite
Make sure your App Pool is started - or just restart IIS and it should all work again.
Edit: 8/30/16 : A similar but unrelated error can occur if you have the 'new' .NET core installed and update to Win 10 Anniversary edition. See here: https://github.com/aspnet/Home/issues/1583 - Running a repair on VS 2015 Tooling Preview should fix it. Wanted to add it here since the errors are very similar to this answer.
I got this Event Log error after updating Win8.1 to Win10. To fix, go to the Control Panel -> Programs and Features, locate IIS URL Rewrite Module 2, right click and select Repair (it's quick). Next, restart your stopped AppPool(s). Should be OK now.
No need to uninstall nor reinstall.
Gary Davis
Don't need to uninstall. Just do a Repair instead, and it will works.
For some weird reasons, the only solution for me was to install previous version of the module, from https://www.microsoft.com/en-us/download/details.aspx?id=7435
I just ran in to this issue after an update. All of the app pools where stopped!
Starting them resolved the issue.
I struggled with similar issues last night.
It started out with a complaint about missing redirect.dll. After installing IIS' Redirect feature, that log message disappeared and all I was left with was a bunch of error messages from WAS. It tried starting my application pool five times until giving up.
A listener channel for protocol 'http' in worker process '120' serving
application pool 'my app pool' reported a listener channel failure.
The data field contains the error number.
The error code was "8007007E" (File not found according to google).
I then installed ProcMon from sysinternals.com and every time the w3wp process complained about "NAME NOT FOUND" right before terminating, I googled and installed the corresponding IIS feature. I repeated this until I had installed them all and got everything working again.
Installing everything is not a good solution, but I do not have time to investigate deeper right now.
I came across similar symptoms after changing my domain password. I had to also reset my password in my (hard coded!) App Pool settings on my dev box.
I had a similar issue with "httpplatformhandler.dll failed to load". Again the solution was to download the appropriate httpplatformhandler install msi from http://www.iis.net/downloads/microsoft/httpplatformhandler and then run a repair.
The Repair worked for me after updating to W10 Insider Preview 160826-1902
I encountered the same problem in Windows Server 2012 R2. After I update Windows Updates to newest, it works.

How to get rid of the VMware error when starting Visual Studio 2012, but without disabling VMDebugger add-in?

I am getting the following error when starting Visual Studio 2012 as unprivileged user:
An error has occurred while trying to access the log file. Logging may not function properly.
A casual web search showed that the issue used to exist with VMware 6 beta, back in 2006. I also found one other user who experiences the same in a more recent VS version (2008) and it started only recently.
The title of the message box indicates that this comes from VMware. I have VMware 9 Workstation installed. The problem could be related to system updates or the update 2012.2 CTP and hasn't gone with the final 2012.2 update package.
The question:
How can I get rid of the error without actually disabling the VMDebugger add-in?
Temporary workaround:
There is a workaround, disabling VMDebugger in the "Add-in Manager". However, it even seems that unprivileged users are unable to successfully disable it. I had to start VS as admin (I am using SuRun for the purpose) to disable it and the error not reappearing upon next start of the IDE.
I had the exact same problem, this is how I solved it.
I monitored devenv.exe using procmon to find the log path, on my computer it was: %TEMP%\vmware-username
I checked the permissions on the log directory, and discovered that my user had no access - neither read nor write! I gave myself full access and deleted the old log files. That solved it for me.
I think this happened because UAC was disabled when I installed VS and VMware.
In Visual Studio, go to the menubar to VMWARE / About VMWare Virtual Debugger; the Debugger log file will be listed there, e.g. C:\Users\Phil\AppData\Local\Temp\vmware-Phil\vmware-vsid-1.log
Give your user full access to that file.
(This solution was for Visual Studio 2013, VMware Workstation 11.1.2, Windows 8.1.)
The fastest and easiest way to solve is...
1. Locate the folder %temp%\vmware-{username}
2. Delete this folder. The folder will be created by opening the Visual Studio.
Note: You need to open the Visual Studio without admin rights to resolve the issue!
Background: Mostly this happens if you use the VMware debugger plugin the first time under admin rights (because your app may need this right to run properly). This creates the folder under admin rights with the admin permissions. Everytime you open the Visual Studio with admin rights, you have no problems.
Examples
Windows: C:\Documents and Settings\<username>\Local Settings\Temp\vmware-<username>-<PID>.log
Linux: /tmp/vmware-<username>/ui-<PID>.log
This post helped me
The fastest and easiest way to solve is...
1. Locate the folder %temp%\vmware-{username}
Go in windows+R %temp% , delete all , ready !

Visual Studio 2012 failed to create project

I just upgraded to windows 8 from windows 7. Visual studio 2010 broke down completely. Oh well. I removed vs2012 and installed visual studio 2012, where the pain starts. I have been reinstalling vs 2012 a couple of times. However, the symptom remains the same.
When I try to create a new project (FILE -> New -> Project or ctrl + N).
It pops up with an error message dialogbox saying
"Failed to create a ImageSource from the text '..\Images\Medium.png'.
" I am like ##*%&^#*###(. So can anyone please tell me what is going on with my Visual Studio2012?
By the way, I can open and run the existing vs2010 projects with no problems.
I definitely neither want to do a fresh install on windows 8 nor rolling back to my windows 7.
Cheers,
To resolve that problem, I've change the permission of "modify" for "everybody" on the files
c:\windows\microsoft.net\framework\v2.0.50727\config\machine.config
and
c:\windows\microsoft.net\framework\v4.0.30319\config\machine.config
Don't know if it's the best way to do it, but at least it works.
Do you have any codec packs installed on your system? I had a WIC codec pack for viewing RAW files in Explorer, and it resulted in the same issue you are describing. Uninstalling the codecs fixed Visual Studio for me.
I was having various issues, including the above.
To resolve the problem on Windows 8 for VS 2012, setting it to run as administrator fixed the problem for me.
Launch icon properties->Advanced Properties->Run as administrator
I hope this helps.
Cheers,
Sean
The trace of this issue leads to Windows Imaging Component (one solution proposed was to remove FastPictureViewer, which codec affects WIC, but it was not my case). I used procmon to log all file and registry calls and found that VS2012 stumbles at the following key:
HKLM\SOFTWARE\Classes\.png - REG_SZ Content Type
I was suprized to see that Content Type for .png was set application (for .jpg it was application as well). After correcting it to image/png, not only VS2012 started successfully, but VS2010 as well, that was showing "Provide value on System.Windows.Baml2006.TypeConverterMarkupExtension threw an exception" on Win8 and caused me to try VS2012.
I had the same problem with Visual Studio 13.
uninstalling/reinstalling VS13 and all shared packages did not solved the problem.
Finally I tried to run it as administrator, as explained above and it worked.
Just happened to me. As Eric Aubry said check the machine.config file. In my case it wasn't permission error but the fact that the file was destroyed internally. By renaming the machine.config.default everything was fixed.
For me, this happened when I installed mysql on my machine, and it added an extra connection string to my machine config. However, since I was using a separate file for configSource, it resulted my machine config to become corrupted.
Moving the new config key to my config source from the 32bit machine config solved the issue.
As I mentioned in that question ,
I tried almost every solution I found.
I would like to share, what I have tried and did not work and what did work and solved the problem.
Here are the "solutions" which did not work for me but claimed that they worked for some people.
1) Removing FastPictureViewer Codec Pack (which was already not installed)
2) Having a modify permission to everyone for
c:\windows\microsoft.net\framework\v2.0.50727\config\machine.config
and
c:\windows\microsoft.net\framework\v4.0.30319\config\machine.config
3) Using Procmon to see broken registries
4) Uninstalling/reinstalling VS13 and all shared packages
5) Renaming the machine.config.default to machine.config
6) Running Visual Studio as an administrator
And this what it solved it:
Simply installed all the updates for windows 8.1 (not only the important ones, also optional updates as well) and restart. It sounds crazy after spending hours and hours but that solved my problem.
Good luck!

Resources