- This topic has 6 replies, 2 voices, and was last updated 12 years, 8 months ago by
.
-
Posts
-
I recently installed MyEclipse 10.1. From MyEclipse Configuration Center > Software Updates, I had removed several software items I do not use. I had also uninstalled an older version of MyEclipse (8). Now when I try to start MyEclispe 10.1, it always fails with “Unable to access jarfile win32”.
I have tried repairing the MyEclipse software, uninstalling MyEclipse, and installing it to a different location. In each case, the problem persists. I even tried to remove the common binary/folder from where the errors seems to be occurring to force a new install of the binary folder.
NOTE: MyEcipse 9.1 still works fine.
I’m running Windows 7 Premium 64 bit.
I have attached a snapshot of the error text.
[/img]ksgetting,
I’m sorry you’re having this issue. It’s not entirely clear what you’ve tried exactly.
- You said that you installed 10.1 from the Configuration Center; how did you install 10.0, in order to get to the Configuration Center, and did you have any problems with that (clearly it started OK)?
- How did you try to repair the installation? Was it with the original 10.0 installer, or some other method?
- When you tried installing to a different location, did you try a different common directory also? How did you install this time? Was it the same method as your original attempt?
- You said that the startup fails with “Unable to access jarfile win32” but I couldn’t spot that message in the screenshot you posted. Where did you see that error message and is that the exact message?
The message makes me wonder if there is some conflict between a 64 bit java and a 32 bit library but I can’t think where that might be. I tried a fresh install of 10.0 on Win 7 and then updated to 10.1 and had no problem starting MyEclipse.
A couple of other things to try are:
- If you haven’t already done this, try renaming the folder that is pointed to by the .pulse2.locator file in your home folder and then doing a fresh install of 10.0 followed by the update. You can delete the new folder and rename the old one back again, if necessary.
- If you haven’t tried this, download the new 10.1 installer from our website and use that to install 10.1
- Install or repair using Pulse Explorer. A FAQ is available here. There is also a facility in Pulse Explorer to reinstall an existing installation (also called “profile”).
No I did not install from the configuration center. I downloaded the 10.1 installer (myeclipse-10.1-offline-installer-windows). It originally installed OK. After startup, I went to the configuration center and removed/uninstalled some of the features that I do not use. During this process, it failed for some reason. It basically just hanged. So I killed the application from the task manager. When I tried restarting, the problems started happening.
I reran the offline installer and tried using the repair option. No change. I tried several times to a) uninstall and b) install again. No change. I tried installing to a alternate location, but no change. I did not see an option to use a different common location. From the current common location, I deleted just the binary folder.
My previous version is 9.1. I never installed 10.0.
When it fails, it first shows a pop-up window with Unable to access jarfile win32. After clicking on the OK button, you are then presented with the attached error window. I’m attaching an image of the first pop-up window.
When I say I deleted just the binary folder, I was referring to one of my attempts at fixing the error. I reran the install right after that. I was trying to force the binary folder to be reinstalled.
ksgetting,
My apologies; I misread your opening post. Thanks for the additional information.
Which features did you try to remove?
Did you try renaming the folder pointed to by .pulse2.locator before uninstalling, as I suggested? The common folder is not configurable once you’ve installed one release, and this is a way round that, to enable you to try a completely fresh installation. As an alternative to renaming, you can simply delete (or rename) .pulse2.locator then point the installation at a diferent folder or you can edit the contents of .pulse2.locator to point to the different location. Actually, these two methods are probably preferable to renaming the install folder itself as that may stop 9.1 working while you check this.
A note about the configuration center. It is sometimes slow in returning control once some selection has been made, or altered. So it may appear to hang from time to time. I’ll try to replicate what you did but it may help to know which features you tried to remove.
I wasn’t familiar with the .pulse.locator file, but was able to find it via Google. I changed the location to Genuitec10, and performed the install again. That fixed it, thanks. Something in the old common folder must be broken, but fortunately it did not affect 9.1.
I don’t recall exactly which features I removed, but since I don’t use most of them, it was quite a few. I was removing them in hopes that the performance would be faster for the eclipse environment.
ksgetting,
I’m glad that worked for you and that 9.1 is still OK. There’s no reason you should be familiar with the .pulse2.locator file; we don’t expect people to have to manipulate it but sometimes it’s necessary.
I agree that it seems like some file in the common folder got corrupted and, presumably, was not detected by a repair operation and not affected by a reinstall. It would be good to replicate it so we can find out what’s going on but I tried a few things without “success”.
Anyway, if you’re happy with what you now have, that’s the main thing. Let us know if you have further problems.
