Resolved Error: Failed to bind to virtual machine because of a AgentInitializationException

Discussion in 'Client & Site Support' started by Slick, Apr 18, 2016.

  1. So, I get this error when I try starting an instance: "Failed to bind to virtual machine because of a AgentInitializationException"


    Here is my log:

    [Debug] Version: 2.0.1
    [Debug] Operating System: Windows 10 (x64)
    [Debug] Java: 8 Update 77 (x86) (Oracle Corporation)
    Downloading 1 missing or outdated cloud resource.
    Failed to bind to virtual machine because of a AgentInitializationException
    com.sun.tools.attach.AgentInitializationException: Agent JAR loaded but agent failed to initialize
    at sun.tools.attach.HotSpotVirtualMachine.loadAgent(mg:128)
    at nul.IiiiIIiIIIiI.enum(wdc:45)
    at nul.IIiiIIiiIiII.run(ebc:200)

    I have no idea what to do. I've tried uninstalling and reinstalling at least 5 times. I would really like to fix this so I can see the great work ya'll have done.
     
    rees likes this.
  2. I believe this was appearing earlier for many people as well.

    A description by Cloud I saw was the problem is Runemate is running on x32 bit and your Java is running on x64.

    You need both Runemate and Java running on x32 for them to communicate with each other.

    I believe you need to uninstall Runemate and Java, and then reinstall Runemate.

    Runemate should then prompt you to install Java during the installation process, where it will install the x32 bit Java version.
     
  3. I will try that, thank you! I will let you know if this works or not.
     
  4. Should definitely be resolved. If not, post a new thread with the exception.
     

Share This Page

Loading...