- This topic has 20 replies, 9 voices, and was last updated 15 years, 11 months ago by
defiant42.
-
AuthorPosts
-
November 11, 2008 at 12:46 pm #290838
Riyad KallaMemberbwilliams,
What virus scanner are you using? Could you give us a bit more info about your system and issue you are running into?
We do quite a bit of testing on Windows XP, with a massive portion of our user base all on Windows XP as well… if our installers were a complete fail on Windows XP we would definitely know about that. I’m just trying to determine the variable in the mix here to see what could be causing the problem.
November 11, 2008 at 1:27 pm #290845
Riyad KallaMemberAll-in-one version 7.0 m2
Sun JDK 6 update 10Hmmm… maybe it’s an SP3 thing, I’ll double-check on a machine sitting next to me.
ramgs, any interesting security software on your machine to make note of?
November 11, 2008 at 3:19 pm #290866
Riyad KallaMemberok I just did two full download/install/test/uninstall cycles on a Windows XP SP2 and SP3 machine (both with AntiVir installed)… no problems with the All in One installer.
I’m starting to think that this might be tied to the security software somehow that some of you are using?
November 21, 2008 at 1:38 pm #291299
pirtleMemberI am getting a similar error when installing on linux. It installs about 25% or so, then fails with this error.
An error occurred while collecting items to be installed
Problems downloading artifact: osgi.bundle,org.eclipse.emf.query,1.2.0.v200805130238.
Error reading signed content: /tmp/signatureFile35933.jar
signed overrun, bytes = 95
Problems downloading artifact: osgi.bundle,org.eclipse.emf.query.ocl,1.2.0.v200805130238.
Error reading signed content: /tmp/signatureFile35934.jar
signed overrun, bytes = 95November 24, 2008 at 10:14 am #291333
Riyad KallaMemberpirtle,
It sounds like you are using the Pulse-installer on Linux; we’ve seen this behavior problem before when Pulse will pick a mirror that has a goofed copy of plugins so the installation fails when it goes to verify the JARs. Unfortunately this is a problem with the mirrors, not Pulse, and is usually fixed by restarting the install, Pulse will pickup where it left off (once Pulse is installed, or if you are using the Pulse Explorer to install MyEclipse, right-click on the profile and do a “Reinstall and Run”, that will try some new mirrors).
Sorry for the trouble.
July 8, 2009 at 8:12 am #300252
defiant42MemberAm sorry to report that we appear to be running into another error with regard to the installers. While adding SP3 got us past the initial catastrophic error, I am now seeing it again, later in the install. This time, it happens if you select a target directory other than the default. C:\Program Files\MyEclipse Blue 6.6. If you select the default target directory, the install runs fine. If you select something other than the default, the install crashes when it tries to install files to the directory:
c:\apps\MyEclipseBlue\eclipse\.eclipseproduct
All 4 of the installers below have this behavior. Again, if the default install directory is chosen, the install runs fine.
MyEclipse_Blue_6.6.0_E3.3.2_Installer.exe
MyEclipse_Blue_6.5.0GA_E3.3.2_Installer.exe
MyEclipse_Blue_6.5.1GA_E3.3.2_Installer.exe
MyEclipse_Blue_6.5.0GA_E3.3.2_Installer_A.exePlease advise.
Eric
-
AuthorPosts