- This topic has 3 replies, 3 voices, and was last updated 13 years, 10 months ago by support-joy.
-
AuthorPosts
-
wleckParticipantPulse pushed Milestone 2 update this morning. When I attempt to launch it, it generates the following error from a popup:
An error has occurred. See the log file c:\<path to log file>\1296055641524.log. The log number changes with each subsequent launch attempt. Contents of log below. The log indicates a configuration error. Contents of configuration error also below. This is now blocking my work. I need a fix, workaround, whatever ASAP!!
!SESSION 2011-01-26 08:27:21.160 ———————————————–
eclipse.buildId=unknown
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86!ENTRY org.eclipse.osgi 4 0 2011-01-26 08:27:25.528
!MESSAGE
!STACK 0
org.osgi.framework.BundleException: Exception in org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start() of bundle org.eclipse.osgi.
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:806)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:755)
at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.resume(InternalSystemBundle.java:207)
at org.eclipse.osgi.framework.internal.core.Framework.launch(Framework.java:654)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:298)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
Caused by: java.lang.IllegalStateException: The System Bundle could not be resolved: Another singleton version selected: org.eclipse.osgi_3.6.1.R36x_v20100806
at org.eclipse.osgi.internal.baseadaptor.BaseStorage.checkSystemState(BaseStorage.java:752)
at org.eclipse.osgi.internal.baseadaptor.BaseStorage.getStateManager(BaseStorage.java:725)
at org.eclipse.osgi.baseadaptor.BaseAdaptor.getPlatformAdmin(BaseAdaptor.java:366)
at org.eclipse.core.runtime.internal.adaptor.EclipseAdaptorHook.frameworkStart(EclipseAdaptorHook.java:88)
at org.eclipse.osgi.baseadaptor.BaseAdaptor.frameworkStart(BaseAdaptor.java:242)
at org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start(SystemBundleActivator.java:61)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:783)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:774)
… 12 more
Root exception:
java.lang.IllegalStateException: The System Bundle could not be resolved: Another singleton version selected: org.eclipse.osgi_3.6.1.R36x_v20100806
at org.eclipse.osgi.internal.baseadaptor.BaseStorage.checkSystemState(BaseStorage.java:752)
at org.eclipse.osgi.internal.baseadaptor.BaseStorage.getStateManager(BaseStorage.java:725)
at org.eclipse.osgi.baseadaptor.BaseAdaptor.getPlatformAdmin(BaseAdaptor.java:366)
at org.eclipse.core.runtime.internal.adaptor.EclipseAdaptorHook.frameworkStart(EclipseAdaptorHook.java:88)
at org.eclipse.osgi.baseadaptor.BaseAdaptor.frameworkStart(BaseAdaptor.java:242)
at org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start(SystemBundleActivator.java:61)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:783)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:774)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:755)
at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.resume(InternalSystemBundle.java:207)
at org.eclipse.osgi.framework.internal.core.Framework.launch(Framework.java:654)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:298)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)!ENTRY org.eclipse.osgi 4 0 2011-01-26 08:27:25.536
!MESSAGE Startup error
!STACK 1
java.lang.RuntimeException: Exception in org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start() of bundle org.eclipse.osgi.
at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.resume(InternalSystemBundle.java:215)
at org.eclipse.osgi.framework.internal.core.Framework.launch(Framework.java:654)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:298)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
Caused by: org.osgi.framework.BundleException: Exception in org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start() of bundle org.eclipse.osgi.
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:806)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:755)
at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.resume(InternalSystemBundle.java:207)
… 10 more
Caused by: java.lang.IllegalStateException: The System Bundle could not be resolved: Another singleton version selected: org.eclipse.osgi_3.6.1.R36x_v20100806
at org.eclipse.osgi.internal.baseadaptor.BaseStorage.checkSystemState(BaseStorage.java:752)
at org.eclipse.osgi.internal.baseadaptor.BaseStorage.getStateManager(BaseStorage.java:725)
at org.eclipse.osgi.baseadaptor.BaseAdaptor.getPlatformAdmin(BaseAdaptor.java:366)
at org.eclipse.core.runtime.internal.adaptor.EclipseAdaptorHook.frameworkStart(EclipseAdaptorHook.java:88)
at org.eclipse.osgi.baseadaptor.BaseAdaptor.frameworkStart(BaseAdaptor.java:242)
at org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start(SystemBundleActivator.java:61)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:783)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:774)
… 12 more#Generated by Pulse at Wed Jan 26 08:27:09 MST 2011
#Wed Jan 26 08:27:09 MST 2011
com.genuitec.pulse.client.basedir.location.override=C\:\\Users\\Bill\\AppData\\Local\\Genuitec
com.genuitec.pulse.client.blueprint.id=rmb-1259098
com.genuitec.pulse.client.credentials=UYsG+GX8yCO+hynp9uJ0KeY4MyBwQn1Zl1FtwjhBgUoOt1Ks714oN82uSJlyjt+IV+cnbQJk5qNW geotwLLngpb8nw831VOXlRqLep/xZPqUdYbsnFWthaLoSYx+br5hcBZBTmO10Ubsiq/eCJwQsDSR LexA1YyO3nxskOoXFoQ\=
com.genuitec.pulse.client.handshake.id=66aad0da-d8b4-4af7-a9cc-72e7ab813861
com.genuitec.pulse.common.server.url=https\://www.poweredbypulse.com\:443
eclipse.p2.data.area=file\:/C\:/Users/Bill/AppData/Local/Genuitec/Common/configuration/v2/
eclipse.p2.profile=com.poweredbypulse.profile-611819-rmb-1259098
eclipse.product=com.genuitec.myeclipse.product.ide
equinox.use.ds=true
org.eclipse.equinox.simpleconfigurator.configUrl=file\:org.eclipse.equinox.simpleconfigurator/bundles.info
org.eclipse.update.reconcile=false
osgi.bundles=reference\:file\:org.eclipse.equinox.simpleconfigurator_1.0.200.v20100503.jar@1\:start
osgi.bundles.defaultStartLevel=4
osgi.framework=file\:/C\:/Users/Bill/AppData/Local/Genuitec/Common/plugins/org.eclipse.osgi_3.6.1.R36x_v20100806.jar
osgi.framework.extensions=reference\:file\:javax.transaction_1.1.1.v201002111330.jar
osgi.instance.area.default=@user.home/Workspaces/MyEclipse 9
osgi.splashLocation=C\:\\Users\\Bill\\AppData\\Local\\Genuitec\\Common\\plugins\\com.genuitec.myeclipse.product_9.0.0.me201101241935\\splash.bmp
osgi.splashPath=platform\:/base/plugins/com.genuitec.myeclipse.product================================================================
[/img]
Brian FernandesModeratorBill,
Sorry you are running into this issue, for some reason the update has not been applied correctly.
An easy way to fix this is to go to the 9.0M2 downloads page and download the Custom installer for MyEclipse / Windows – (it’s about 15MB). When you run it, it should detect your existing install and give you the option to repair it – choose this option to fix your installation.
You could also choose to install a new profile of MyEclipse using the same installer and when that starts, point it to your existing workspace.
Alternatively, if you have Pulse Explorer installed, start it, find your profile and choose “reinstall and run” from the profile’s context menu.
Since you have presumably already downloaded the binaries that are part of the update, none of these steps should require significant additional downloads to get your installation back to working condition.
Please let me know if I can help further.
wleckParticipantThanks Brian:
I downloaded; and executed the Custom installer. It didn’t work. However, it did allow me to update its results to your support team. Many thanks to Tim for getting back to me promptly where he discovered that my Home directory was set to read only. It is unclear to me how that happened; but suspect an Update push from MS to the Security Essentials application may have been the root cause. Clearing the read-only status of the directory now allows M2 to start correctly through Pulse.
support-joyMemberGood to hear you are all set.
Best.
-
AuthorPosts