I'm using Eclipse Kepler on Windows 7 and recently it became more and more frequent that it takes lots of time when it has to delete files. For example in these contexts:
mvn clean launched from Eclipse
cleaning output folder in case of automatic projects build by Eclipse
deploying a war on a server (deletion of the previous deployment)
I've checked this old question but working in a fresh new workspace has no effect.
I may have a clue: to gain some time I 'help' Eclipse by deleting the files myself with Windows Explorer. Windows often launches a pop-up saying that I need admin right to do that. I just hit Enter (I am admin user) and the files are quickly deleted. If Eclipse had no right to delete the files I would have expected an error, instead it just takes much more time to actually delete the files.
Why could be the cause of that? Knowing that the clue may or may not be relevant.
For the record: no solution has been found to the problem. I got a new desktop with a fresh Win7 image and I don't have the problem, working with the same Eclipse projects.
This would indicate that the problem came from a misconfiguration of the Windows user permission. Sadly, no more details available.
I decided to turn over a new leaf and start learning Java, but after downloading eclipse I cannot seem to make it run. I originally got an error saying it couldn't find my VM so I changed the path in the eclipse.ini to where "Java Mission Control" is installed, and now it's giving me this error when I try to run the application. I have looked at many other posts where people get the same error message but they all have to do with wrongly unzipped files and I am quite sure I unzipped it properly. I have also tried different mirrors and redownloaded eclipse 5 or 6 times as well as reinstalled JDK with no avail. I have used WinZip, Windows file explorer, and Jzip all to unzip the file with the same message.
Windows 7 64bit
8gb ram,i7, 660ti graphics
If you copy and paste all of the contents into a folder on your desktop, you can then use the eclipse.exe file just fine.
I had the same problem with Eclipse. I even had a very similar problem when trying to install the Android Studio (I wanted to compare Eclipse and Android Studio). The difference with Android Studio was the error message (forgot exactly, but was saying that I was missing a .dll file that was important).
The simple thing that solved the problem:
I moved the original .zip file out of the folder where the unzipped files were created (I moved to the desktop). You can even delete it definitely because once unzipped we don't need it anymore. Then, the Eclipse.exe run smoothly (even before running it I noticed its icon changed after I eliminated the .zip). Then I went and did the same for Android Studio, run the corresponding .exe file, and tara-raaaan: run too!!!
Easy... but not obvious at all, I know. Hope this helps!
PD: Before this problem I had another one. It was related with Java (JDK); I had to add the path where it was installed and that solved the problem.
I'm using Eclipse Indigo on Mac 10.7.4. While working, I get these periodic, annoying dialogs
'Periodic workspace save.' has encountered a problem.
Could not write metadata for '/.org.eclipse.jdt.core.external.folders'.
/Users/davea/Dropbox/workspace/.metadata/.plugins/org.eclipse.core.resources/.projects/.org.eclipse.jdt.core.external.folders/.markers.snap (No such file or directory)
I seem to be able to continue as normal, but I was wondering how I can eliminate these errors.
I had the same problem.
'Periodic workspace save.' has encountered a problem.
Could not write metadata for '/External Files'. D:\java\fuentes\.metadata\.plugins\org.eclipse.core.resources\.projects\External
Files\.markers.snap (El sistema no puede hallar la ruta especificada)
I created the folder "External Files" and it worked fine. In a few minutes the files ".markers.snap" and ".syncinfo.snap" appeared in this folder and the message didn´t appear any more.
I fixed mine by closing eclipse and deleting the whole .metadata folder inside my workspace folder.
Today I faced the same issue consistently, whenever I exit the eclipse.
While trying the above solution provided by TS.xy, the below steps got rid of this issue for now.
Switch to new workspace and close the Eclipse.
Open the Eclipse with new workspace and after that switch to the actual workspace(in which
exception occurs).
Actual workspace loaded with all my previous projects.
Now exiting the Eclipse, does not result in that exception.
Hope that this step may work for someone.
Just for another data point, none of the above helped my situation. The way I finally got past this issue is that each time Eclipse complained about some folder not being there, I went on my hard drive and created the folder. E.g. after I see
Could not write metadata for '/servers'.
C:\...\.metadata\.plugins\org.eclipse.core.resources\.projects\servers\.markers.snap (The system cannot find the path specified.)
I create the "servers" folder (not the file inside it). This gets me to the next error. I went through 3-4 of these iterations (exiting Eclipse each time to force the save) before the issues went away.
HTH, Mark
This was simple for me -
Solution
(pre) the listed directory is not present, see pic
Run Eclipse, see the error shown in pic below. Close Eclipse
Create the directory (RemoteSystemsTempFiles) where it is looking
note: ignore the items in this folder (e.g. .markers), they are auto-generated
Restart Eclipse, problem solved!
Example Problem Message
Not sure why this took me so long to resolve, but quite easy now, and quite obvious in retrospect! ;)...
Using Ubuntu, got the same issue
I noticed that the owner of some of the directories in
~/workspace/.metadata/.plugins/ ...etc...
was root
changed owner to me and the error stopped happening.
Looks like the same sort of issue may be caused by multiple causes.
Close the Eclipse , Clear the .metadata folder completely.. Start Eclipse & Import the necessary project once again if your project references are deleted..
The solution that work for me is the following:
Delete .metadata folder
Restart eclipse
Solved it by setting workspace on a local folder, and set data from import project, from existing resources.
I encountered the same problem , my resolution was to rename the the folder name under the workspace folder. i.e. com.ibm.collaboration.realtime.alertmanager.embedded was renamed to com.ibm.collaboration.realtime.alertmanager.2embeddedxx and rebuilt my project.
In my case, because I've accidentally deleted my workspace folder, and I observed the 'Periodic workspace save has encountered a problem". To solve this issue, I just simply create a new workspace and load all my projects to the new one. Hope you can solve your problem by doing the same thing.
I also ran into this problem. My situation was a little different. I was using 'working sets' to group my projects inside of eclipse. What I had done was attempt to delete a project and received errors while deleting. Ignoring the errors I removed the project from my working set and thus didn't see that I even had the project anymore. When I received my error I didn't think to look through my package explorer with 'projects', opposed to working sets, as my top view. After switching to a top level view of projects I found the project that was half deleted and was able to delete its contents from both my workspace and the hard drive.
I haven't had the error since.
I had gotten a little too aggressive about removing some directories in my project area when I was running out of disk space, and deleted this directory. Eclipse can leave some huge core files if it crashes in your workspace directories, (I had 35 gig of them) so it's worth taking a look there in your workspaces occasionally.
Anyway, as per the problem I tried the 'create a directory' approach. And it worked.
I was also seeing this error when I closed Eclipse by the way, not only after the 'periodic save'. So the exit/restart was also part of this.
Note that the last item on the directory path specified in the error message is a file -- not a directory, so don't get confused here. Probably worth checking that the directory permissions are created correctly as well (as the other projects in the workspace I think).
Obviously this is a bug in the Eclipse code base, (creating the full directory path under the file that is being created), but had I not deleted it in the first place, I would not have caused it in the first place.
I have the same problem since yesterday. Yesterday, I fixed it by creating a new workspace and reimporting the projects. It seemed to work well, but today it started again.
So, today I created the folder and the file manually and gave the full permissions -rwxrwxrwx.
Seems to work again...
Close Eclipse. Open RemoteSystemsTempFiles folder in Workspace, and clear inside this folder. Again open eclipse and close, warn about .project. Press Ok, then open Eclipse.
Solved my problem that.
I ran into this problem today after they switched our anti-virus software to Kaspersky.
In my case, the platform is Windows 7. My workspace is stored on mapped network drive. The strange thing is that, even though this appears to be a permission issue, I could manipulate files and folders at the same level as the inaccessible file without incident. So far, the only two workarounds are to move the workspace to the local drive or to uninstall Kaspersky. Removing and re-installing Kaspersky without the firewall feature did not do the trick.
I will update this answer if and when we find a more accommodating solution, though I expect that will involve adjusting the anti-virus software, not Eclipse.
In my case, the drive I was storing my workspace on had become full downloading SDK updates full and I just needed to clear some space on it.
This happened to me because i deleted one of the resources files inside the .metadata folder in my workspace.
After trying all methods, deleting the .metadata folder in my workspace worked.
Infact, this nuke option seems to work when there are a lot of issues related to eclipse bugs. One such example is working-sets. Working-sets are extremely buggy(but useful) and it is there that most of my eclipse problems start.
Hope this helps someone.
I solved the problem switching the workspace.
Go to File (Switch workspace)
Select the destination and create a folder named Workspace
Run a Hello World and close Eclipse (notice that Eclipse creates the folder RemoteSystemsTempFiles automatically)
now copy all your projects into the new folder Workspace
Open Eclipse and if necessary (sometimes Eclipse does not show the projects) import all of them (go to File/ Open projects from File System)
After you exit the eclipse, there would be an specific failed reason.
Mine is that the DISK IS FULL so the eclipse can't write into it anymore.
Agree with #J-Dizzle,
I am a beginner in web-development and had a hard time solving this today.
Had similar problems when I was creating a SpringBoot project in STS.
Tried most of the solutions mentioned but they didn't work.
Tried removing .metadata folder and re-building my springboot project but still nothing worked.
NOTE : I had multiple workspace in STS and this error occurred after migrating a project from one workspace to another.
Solution : All you need to do is restart your eclipse/STS IDE and it will work just fine.
I have been using Eclipse forever, but only today I upgraded to Indigo.
Using Eclipse Indigo on Mac 10.6 *
Files won't update after editing them and saving them. If I add blank lines and then save, then if I start debugging, the debugger will go through the lines that were there before, but now those lines are empty and the actual lines that the debugger is executing are a couple of lines below (due to the added blank lines). Debugger executes blank lines??!! Same thing if I change the code. If the file says X=5, and I change X=6, then debug, X will still be 5 ????!!!! Am I missing some editor caching option or smth ????
Things I have tried:
1. clean all projects, rebuild all projects
2. Delete projects, re-add them
3. delete files, write them from scratch
4. all auto-build and auto-refresh options are on
5. tried to change the workspace, the bug presists
6. tried to play around with the -xms128M and -Xmx786M option in the .ini file
7. tried restarting Eclipse and restarting computer
The problem was some discrepancy between the java version of the VM and the project's "facet" version. (whatever that is).
The thing I dont get is why the project was still running if there were problems reported on the "Problems" view and no new .class file was even compiled. Why it was running an outdated .java file, when the code on the actual display was different? (thus the ghost effect).
Is there an option that allows the eclipse to run outdated .class files if no new .class file could be compiled cause of compile errors?
Eclipse was working fine just a day ago. But today, when I click the eclipse icon, it only loads the splash screen and nothing else thereafter, I even don't get to see the splash screen which contains that 'green loading sign' at the bottom, and -- while monitoring the eclipse.exe in Windows Task Manager(just after starting eclipse) -- I saw that even after the splash screen went off the screen, the eclipse.exe process went with it, after a few seconds. Keep in mind that I did NOT see any warning or error messages because, (I'm assuming, that the loading haven't gone to a point where it is capable of sending any error message)
Hence, I tried reinstalling eclipse, by copying from INSIDE the .zip directory of the installation folder and pasting it inside the eclipse program directory. But the exact same problem persists. So, now I'm currently downloading the latest version of eclipse to retry again.
Any other Advice?
UPDATE
It turned out that the hard drive containing the workspace was partially corrupted, hence I cleaned it; following that, the workspace data was still accessible. (Though usually I still keep a backup on hand.)
just delete the .metadata folder from workspace and reload the eclipse. It worked for me.
Hoping you have the links to the update sites for your installed plugins, my advice is to download eclipse, download your already installed plugins from their update site's and then open the new eclipse and set the workspace to your actual workspace. More far than that is to trash your time... trust me.
It turned out that the hard drive containing the workspace was partially corrupted, hence I cleaned it; following that, the workspace data was still accessible. (Though usually I still keep a backup on hand.)
Probably something went wrong with Java. Try re-installing Java run-time.
It also can mean a problem with the eclipse.ini file (like an extra space at the end of the line), or a problem with the JVM path (since the splash screen is displayed by the eclipse.exe, before loading all the eclipse Java classes).
Check that eclipse.ini file and consider my ini file as a good optimization source.
If your workspace has been corrupted your safest approach is to create a new one.
I would actually strongly suggest that you reinstall everything that might have been corrupted, to avoid as much strangeness as possible. This includes the underlying OS.
I have tried out both
(1)E:\eclipse-standard-luna-RC3-win32\eclipse -clean in run
(2)deleting .metadata folder from workspace
I do not which one worked for me.Thanks...