Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

Sign up now!

Bug "Failed to bind the game because of an AgentinitializationException"

Joined
Jan 28, 2016
Messages
8
My computer specifications: Screenshot

So I get the Failed to bind the game because of an AgentinitializationException error. I tried to remove java and runemate to let runemate install the java for me, still the same. Disabled my firewall and antivirus. If I start runescape and runemate as Admin I get no error but I get the loading screen on runemate for about one second and then back to normal screen.
I tried to remove onedrive as It fixed it for some but not for me.

My Log:
[Debug] Java Home: c:\program files (x86)\runemate\jre
[Debug] Java Version: 8u121 x86 (Oracle Corporation)
[Debug] Maximum Heap Size: 743MB
[Debug] RuneMate Version: 2.84.1
[Debug] Operating System: Windows 10 x64
Checking for a new game client every second for two minutes or until one is found.
Found a new game instance after 2 seconds.
com.sun.tools.attach.AgentInitializationException: Agent JAR loaded but agent failed to initialize
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(ku:68)
at nul.iiIiiIiiIIiIi.false(klc:37)
at nul.iiIIiIiiIiIii.run(uoc:152)
 
Joined
Jul 9, 2015
Messages
1
I had this issue, Its indeed onedrive. Problem is I had to reinstall my OS and not sign into my outlook account and I ran a script to remove onedrive all together. Microsoft has done something with one drive where it redirects the home folders that runemate is looking for.

Thescript I used was v1.2 here TERRAOperative/OneDrive-Uninstaller
 
Joined
Feb 13, 2018
Messages
11
Same problem
 
Follow up to my last post, here are two of my logs:

Log 1:
[Debug] Java Home: c:\program files (x86)\runemate\jre
[Debug] Java Version: 8u121 x86 (Oracle Corporation)
[Debug] Maximum Heap Size: 743MB
[Debug] RuneMate Version: 2.84.1
[Debug] Operating System: Windows 10 x64
Checking for a new game client every second for two minutes or until one is found.
Found a new game instance after 3 seconds.
com.sun.tools.attach.AgentInitializationException: Agent JAR loaded but agent failed to initialize
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(ku:68)
at nul.iiIiiIiiIIiIi.false(klc:37)
at nul.iiIIiIiiIiIii.run(uoc:152)
[Clouse] Downloaded 988 human mouse movements selected for you by Clouse.
com.sun.tools.attach.AgentInitializationException: Agent JAR loaded but agent failed to initialize
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(ku:68)
at nul.iiIiiIiiIIiIi.false(klc:37)
at nul.iiIIiIiiIiIii.run(uoc:152)



Bigass log 2:
[Debug] Java Home: c:\program files (x86)\runemate\jre
[Debug] Java Version: 8u121 x86 (Oracle Corporation)
[Debug] Maximum Heap Size: 743MB
[Debug] RuneMate Version: 2.84.1
[Debug] Operating System: Windows 10 x64
java.lang.InternalError: instrument library is missing in target VM
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(ku:71)
at nul.iiIiiIiiIIiIi.false(klc:37)
at nul.iiIIiIiiIiIii.run(uoc:152)
Caused by: com.sun.tools.attach.AgentLoadException: Failed to load agent library
at sun.tools.attach.WindowsVirtualMachine.execute(jx:104)
at sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary(ku:75)
at sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary(ku:143)
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(ku:210)
... 2 more
java.lang.InternalError: instrument library is missing in target VM
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(ku:71)
at nul.iiIiiIiiIIiIi.false(klc:37)
at nul.iiIIiIiiIiIii.run(uoc:152)
Caused by: com.sun.tools.attach.AgentLoadException: Failed to load agent library
at sun.tools.attach.WindowsVirtualMachine.execute(jx:104)
at sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary(ku:75)
at sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary(ku:143)
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(ku:210)
... 2 more
[Clouse] Downloaded 1000 human mouse movements selected for you by Clouse.
java.lang.InternalError: instrument library is missing in target VM
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(ku:71)
at nul.iiIiiIiiIIiIi.false(klc:37)
at nul.iiIIiIiiIiIii.run(uoc:152)
Caused by: com.sun.tools.attach.AgentLoadException: Failed to load agent library
at sun.tools.attach.WindowsVirtualMachine.execute(jx:104)
at sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary(ku:75)
at sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary(ku:143)
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(ku:210)
... 2 more




On another occasion, I ran both clients as admin. When I attempted to start an instance, it acted like it was going to load for a second and then it just goes right back to the "Start instance" screen like nothing happened at all. Which was kind of weird because it was doing the opposite earlier when I DID NOT run as admin BEFORE I uninstalled then reinstalled Java/Runemate. Needless to say, there were no errors or log files that popped up for those times.
 
Joined
Oct 18, 2015
Messages
11
If we didn't, I wouldn't have posted. I tried literally everything besides wiping my entire computer.
Edit: Posted it somewhere else but the issue is basically the same.
Edit - 2: Actually fixed it by following the details Bug - instrument library is missing in target VM probably not a bad idea to add that information somewhere easily accesible.
 
Last edited:
Does not exist.
Joined
Jun 8, 2015
Messages
333
If we didn't, I wouldn't have posted. I tried literally everything besides wiping my entire computer.
Edit: Posted it somewhere else but the issue is basically the same.
Edit - 2: Actually fixed it by following the details Bug - instrument library is missing in target VM probably not a bad idea to add that information somewhere easily accesible.
have you tried using the standalone instead of installing ?
 
Joined
Oct 18, 2015
Messages
11
have you tried using the standalone instead of installing ?

That didn't work but I fixed it by the link I posted above. Had to do with the fact that my user folders where on my second SSD instead of the first because the first is fairly small. It's a windows 10 feature, and it breaks the bot if you don't add a symlink.
 
Joined
Feb 13, 2018
Messages
11
If we didn't, I wouldn't have posted. I tried literally everything besides wiping my entire computer.
Edit: Posted it somewhere else but the issue is basically the same.
Edit - 2: Actually fixed it by following the details Bug - instrument library is missing in target VM probably not a bad idea to add that information somewhere easily accesible.
No worries, I HAVE tried reformatting the PC and it still didn't solve the issue :)
 
No worries, I HAVE tried reformatting the PC and it still didn't solve the issue :)

Same
 
12 year old normie
Joined
Jan 8, 2015
Messages
2,769
That didn't work but I fixed it by the link I posted above. Had to do with the fact that my user folders where on my second SSD instead of the first because the first is fairly small. It's a windows 10 feature, and it breaks the bot if you don't add a symlink.
Yeah this seems to be a common issue for people with the agent initialisation exception. I'm not quite sure how the RMI protocol works that runemate uses but I can imagine that it doesn't like bridging cross-storagedevice when binding to a client that is installed on a different location than the runemate client.
 
Top