An Internal Error Has Occurred In The Initialization Stage
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 30 Sep 2016 00:00:45 GMT by s_hv997 (squid/3.5.20)
Things LocationTech Long-Term Support PolarSys Science OpenMDM More Community Marketplace Events Planet https://www.eclipse.org/forums/index.php/t/156204/ Eclipse Newsletter Videos Participate Report a Bug Forums http://www.yqcomputer.com/186_2315_1.htm Mailing Lists Wiki IRC How to Contribute Working Groups Automotive Internet of Things LocationTech Long-Term Support PolarSys Science OpenMDM Toggle navigation Home Projects Forums Eclipse Community Forums Forum Search: Search Help Register error has Login Home Home» Newcomers» Newcomers» error while opening eclipse Show: Today's Messages :: Show Polls :: Message Navigator error while opening eclipse [message #492313] Mon, 19 October 2009 22:00 Missing name Missing nameMessages: 2Registered: October 2009 Junior Member hi, my eclipse used error has occurred to work just fine, until about a few days ago. when i open it, it says: an error has occurred, see ...\workspace\.metadata\.log. so i opened log.txt and this is what it said: eclipse.buildId=I20080617-2000 java.version=1.6.0-oem 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.core.resources 2 10035 2009-10-17 12:08:07.589 !MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes. !ENTRY org.eclipse.osgi 4 0 2009-10-17 12:08:08.771 !MESSAGE An error occurred while automatically activating bundle org.eclipse.core.resources (26). !STACK 0 org.osgi.framework.BundleException: Exception in org.eclipse.core.resources.ResourcesPlugin.start() of bundle org.eclipse.core.resources. at org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tartActivator(BundleContextImpl.java:1028) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tart(BundleContextImpl.java:984) at org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:346) at org.eclipse.osgi.framework.internal.core.AbstractBundle.star t(AbstractBundle.java:265) at org.eclipse.osgi.framework.util.SecureAction.start(SecureAct ion.java:400) at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter .postFindLocalClass(EclipseLazyStarter.java:111) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLoc alClass(ClasspathManager.java:427) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.fin dLocalClass(DefaultClassLoader.java:193) at org.eclipse.osgi.framework.internal.core.BundleLoader.findLo calClass(BundleLoader.java:368) at org.eclipse.osgi.framework.internal.core.SingleSourcePackage .loadClass(SingleSourcePackage.java:33) at org.eclipse.osgi.fr
not be loaded please contact application vendor error no.302" it makes my desktop and taskbar freeze and if i have 2 windows open i can only use the one im on i cant switch to the other one. Im on vista but my pc knowledge is minimal any help or thoughts appreciated thx. Top internal error by LeeTuto » Fri, 18 Jul 2008 23:18:01 Have you tried inserting your Vista installation DVD and running Startup Repair, as detailed on this page: 'How to automatically repair Windows Vista using Startup Repair' ( http://www.yqcomputer.com/ ) How to automatically repair Windows Vista using Startup Repair What is Startup Repair? This Microsoft page has a great deal more information about that: 'Windows Vista Help: Startup Repair: frequently asked questions' ( http://www.yqcomputer.com/ ) Windows Help and How-To: Startup Repair: frequently asked questions Startup Repair is designed to detect operating system startup problems and troubleshoot any found and correct them with little user interaction. It can repair problems such as: - missing or corrupt drivers - missing or corrupt system files - missing or corrupt boot configuration settings - corrupt registry settings - corrupt disk metadata (master boot record, partition table, or boot sector.) When the Startup Repair Tool has taken control, it analyzes startup log files for clues about the source of the problem and launches diagnostic tests to determine the cause. If it determines the cause of the failure, it attempts to fix the problem automatically. After successfully repairing the problem, it will reboot the system, and notify the user of the repairs, filing a detailed report in the Windows Vista event log. If the Startup Repair Tool can identify the cause of the problem, but can't repair the problem by itself, it will provide access to a set of tools that you can use to manually troubleshoot the problem further. One of these is the Bootrec tool described below. If the Startup Repair Tool cannot identify or repair the problem, it will roll back the system to t