Showing results for 
Show  only  | Search instead for 
Did you mean: 

Error message during machine agent installation




I've received the following error message when I try to start the machine agent on Windows Server 2012.


Wed Nov 28 17:20:43 CET 2018 Unable to create injector, see the following errors:

1) Explicit bindings are required and java.lang.String annotated with is not explicitly bound.
while locating java.lang.String annotated with
for parameter 4 at com.appdynamics.agent.sim.configuration.bootstrap.BootstrapConfigurationProvider.<init>(
at com.appdynamics.agent.sim.configuration.bootstrap.BootstrapConfigurationModule.configure(

1 error
at com.appdynamics.voltron.FrameworkBootstrap.createInjector(
at com.appdynamics.voltron.FrameworkBootstrap.start(
at com.appdynamics.voltron.FrameworkBootstrap.startAndRun(
at com.appdynamics.voltron.FrameworkApplication.start(
at com.appdynamics.agent.sim.Main.startSafe(
at com.appdynamics.agent.sim.bootstrap.Bootstrap.main(


Could you help me with this problem?


Best regards,





What version of the Machine Agent are you trying to install? I'm trying to update my machine agents to the most recent version ( and I'm getting the same thing.

I tried 4.5.6, which was released today and I get the same thing. I just went back to 4.5.4 and that one is working now.

I installed the version of the machine agent. After downgrading to version it solved my issue .

I am getting same error in later versions also.

What is the solution?


AppDynamics Controller build

Agent Version: 4.5.6


[INFO] Agent logging directory set to: [C:\AppD_MCAG-4.5.6]

[main] INFO Version: HV000001: Hibernate Validator 5.3.2.Final

Could not start up the machine agent due to: Explicit bindings are required and java.lang.String annotated with is not explicitely bound.

Please see startup.log in the current working directory for details.



AppDynamics Team

Hi Jose,


There is a bug in the Machine Agent version 4.5.4 that causes this error on Windows Server 2012 R2  - it was triaged and fixed in the latest version (4.5.7).  It appears to be OS-specific, as we were not able to reproduce it on Windows Server 2016.  Apologies for the incovenience: please upgrade to the latest version of the Machine Agent, available from the download site and the issue should be fixed.


Best Regards, Mark Prichard

Seniro Director, Product Management 

Please see my reply to the original post - this bug was fixed in the latest (4.5.7) version of the Machine Agent, so you could also upgrade to that version.  Apologies for the inconvenience.