facebook

Clicking Installation Details | View Error Log causes lockup

  1. MyEclipse IDE
  2.  > 
  3. Installation, Configuration & Updates
Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • #275114 Reply

    Chris Bacon
    Member

    I downloaded and executed MyEclipse_6.0GA_E3.3_FullStackInstaller and it seemed to install ok. The Installation Details are below. I started up MyEclipse, entered my new subscription key, then selected MyEclipse | Installation Summary…

    In the Installation Summary dialog clicked Installation Details…, then in the Installation Details dialog clicked View Error Log.

    Got error dialog box: Windows – No disk
    Exception Processing Message 0xc0000013
    Parameters …

    Clicking any button or the close dialog box results in the same dialog box reappearing. Finally killed it using Task Manager. I’m running Vista with all updates. MyEclipse and Eclipse were not installed before.

    I searched the FAQs, but didn’t find anything. Looks like something is fundamentally wrong.

    Chris Bacon

    *** Date:
    Wednesday, September 5, 2007 12:53:46 PM PDT

    ** System properties:
    OS=WindowsVista
    OS version=6.0
    Java version=1.5.0_11

    *** MyEclipse details:
    MyEclipse Enterprise Workbench
    Version: 6.0.0 GA
    Build id: 6.0.0-GA-200708

    *** Eclipse details:
    MyEclipse Enterprise Workbench

    Version: 6.0.0 GA
    Build id: 6.0.0-GA-200708

    Eclipse Graphical Editing Framework

    Version: 3.3.0.v20070620
    Build id: 20070620-1021

    Eclipse Platform

    Version: 3.3.0.v20070612-_19UEkLEzwsdF9jSqQ-G
    Build id: I20070625-1500

    Eclipse RCP

    Version: 3.3.0.v20070607-8y8eE8NEbsN3X_fjWS8HPNG
    Build id: I20070625-1500

    Eclipse Java Development Tools

    Version: 3.3.0.v20070606-0010-7o7jCHEFpPoqQYvnXqejeR
    Build id: I20070625-1500

    Eclipse Plug-in Development Environment

    Version: 3.3.0.v20070607-7N7M-DUUEF6Ez0H46IcCC
    Build id: I20070625-1500

    Eclipse Project SDK

    Version: 3.3.0.v20070607-7M7J-BIolz-OcxWxvWAPSfLPqevO
    Build id: I20070625-1500

    Eclipse startup command=-os
    win32
    -ws
    win32
    -arch
    x86
    -showsplash
    -launcher
    C:\Program Files\MyEclipse 6.0\eclipse\eclipse.exe
    -name
    Eclipse
    –launcher.library
    C:\Program Files\MyEclipse 6.0\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.0.v20070523\eclipse_1017a.dll
    -startup
    C:\Program Files\MyEclipse 6.0\eclipse\plugins\org.eclipse.equinox.launcher_1.0.0.v20070606.jar
    -exitdata
    1618_64
    -vm
    C:\Program Files\MyEclipse 6.0\jre\bin\javaw.exe

    #275136 Reply

    Loyal Water
    Member

    Are you running MyEclipse as administrator ?

    #275158 Reply

    Chris Bacon
    Member

    Yes, I’m in the Administrator group.

    #275164 Reply

    Loyal Water
    Member

    Being in the Administrator group is not good enough. You should right-click and select Run as Admin. Let me know if that helps.

    #275168 Reply

    Chris Bacon
    Member

    Vista’s security is intrusive and very poorly documented. Here’s what I found:

    How do I mark an application to always require a full administrator access token (User Account Control)?
    Some applications, such as internal line-of-business applications or non-Microsoft products, require the full administrator access token to perform at least some of their functions or tasks, but have not been identified as administrator applications by the developer or publisher.

    The above indicates that MyEclipse should be defined by you as an “administrator application”.

    I followed these instructions:

    To mark an application to always require a full administrator access token
    1. Right-click an application that is likely to require a full administrator access token, but has not been marked as such.
    2. Click Properties, and then click the Compatibility tab.
    3. Under Privilege Level, select the Run this program as an administrator check box, and then click OK.

    Then I tried it again. It went through the “is it ok to run this” dialog (which it had not before), but the results were the same.

    #275169 Reply

    Chris Bacon
    Member

    After I kill it with Task Manager, I get a dialog box titled “Eclipse” with:

    JVM terminated. Exit code=-805306369
    C:\Program Files\MyEclipse 6.0\jre\bin\javaw.exe

    followed by about 20 lines of parameters

    #275184 Reply

    Riyad Kalla
    Member

    Chris,
    Can you try running MyEclipse with JDK 6 if you get a chance?

    We tried locally on two separate Vista machines with the default All in One install (uses 1.5.0_11 JRE) and popping open the error dialog didn’t cause any problems.

    Out of curiosity, can you go to Window > Show View > Others… > PDE Runtime > Error Log… does that display correctly?

    #275187 Reply

    Chris Bacon
    Member

    Window > Show View > Others… > PDE Runtime > Error Log
    worked fine. I’ll try it with JDK 6 and let you know.

    Chris

    #275189 Reply

    Chris Bacon
    Member

    Just found out that it also happens when clicking “View Installation History” in the Product Configuration dialog.

    #275194 Reply

    Chris Bacon
    Member

    I downloaded and installed the latest SDK from Sun, but the same error occurs in MyEclipse.
    I then changed Preferences | Java | Compiler to Compiler compliance level: 6.0 and added jre1.6.0_02 to the Installed JREs and checked the box. Same error happens.

    Since it works on other Vista machines, would my “System Information” help?

    Chris

    #275198 Reply

    Riyad Kalla
    Member

    Chris,
    After installing JDK 6, did you edit the shortcut that you use to run MYEclipse and actually specify the different javaw.exe executable after the -vm argument?

    (changing the Installed JREs just changes what MYEclipse *knows* about,not what it uses to actually run itself)

    #275202 Reply

    Chris Bacon
    Member

    OK, that did it, thanks. Do you know what was going on there?

    Chris

    #275252 Reply

    Riyad Kalla
    Member

    Not sure what is going on. Vista has provided some holes to hop over, and this looks like one in your case that we couldn’t reproduce.

    Sun did add better Vista support in 6, so my hope was that it would fix up whatever issue (maybe a platform-level interaction?) was causing it.

Viewing 13 posts - 1 through 13 (of 13 total)
Reply To: Clicking Installation Details | View Error Log causes lockup

You must be logged in to post in the forum log in