Plugin never resolved service '&taskConfiguratorHelper' with filter TaskConfiguratorHelper
Asked by Vivek Burman:

```
Plugin 'com.aq.aqconnect' never resolved service '&taskConfiguratorHelper' with filter '(&(objectClass=com.atlassian.bamboo.task.TaskConfiguratorHelper)(objectClass=com.atlassian.bamboo.task.TaskConfiguratorHelper))
```

Running plugin on remote agent shows this error. But this error does not shows in local agent.


Answers:
author: Eduardo Alvarenga
body: Hello [@Vivek Burman](/t5/user/viewprofilepage/user-id/4489974)

Welcome to **Atlassian Communities**!

This is a known error on version 1.3 of the ACCELQ app.

Apparently, the latest 1.6 version of the ACCELQ plugin fixes this issue, but unfortunately, that version is not available in [Atlassian Marketplace](https://marketplace.atlassian.com/) as the vendor has not yet pushed it. So you will have to proceed with a manual installation.

You will need to reach out to accelQ and ask for an updated version.

<https://github.com/accelQ-Inc/accelQ-Connect-Bamboo/releases/tag/1.6.1>

Best regards,

Eduardo Alvarenga  
Atlassian Support - APAC

comments: author: Vivek Burman
body: I am from accelq team. I have checked for both code base. But couldn't find such difference which results in this bug.


author: Eduardo Alvarenga
body: Hi [@Vivek Burman](/t5/user/viewprofilepage/user-id/4489974),

Have a look at this commit.

<https://github.com/accelQ-Inc/accelQ-Connect-Bamboo/commit/11e0f22df46d72fb6d3b5ca01b1304d0f30cf686#>

```
private final TaskConfiguratorHelper taskConfiguratorHelper;

@Autowired
public AQPluginTaskConfigurator(@ComponentImport final TaskConfiguratorHelper taskConfiguratorHelper) {
this.taskConfiguratorHelper = taskConfiguratorHelper;
}
```

Looks like this 1.6 release was not merged into the master branch. But I can tell that this version loads in the agents.

Best regards,

Eduardo Alvarenga  
Atlassian Support - APAC


author: Vivek Burman
body: Same commit is in the 1.3 ACCELQ app version too. It works perfectly in local agents though


author: Eduardo Alvarenga
body: Hi [@Vivek Burman](/t5/user/viewprofilepage/user-id/4489974)

I compared both 1.3 and 1.6 tags from accelQ public Github repo and there are definitely some differences:

* <https://github.com/accelQ-Inc/accelQ-Connect-Bamboo/compare/1.3...1.6.1>

Can you confirm if I'm looking at the right place?

Best regards,

Eduardo Alvarenga  
Atlassian Support - APAC


author: Vivek Burman
body: I meant 1.3 in ACCELQ APP in atlassian marketplace vs 1.6 in github which is not listed


author: Eduardo Alvarenga
body: > Same commit is in the 1.3 ACCELQ app version too. It works perfectly in local agents though

Yes it does work in the Bamboo local server but it is not loading properly in any remote agent as you have stated before.

Can you try using the version from Github? You will notice that it loads on the agent.


author: Eduardo Alvarenga
body: Hi [@Vivek Burman](/t5/user/viewprofilepage/user-id/4489974)  

Agent's context does not contain every service which Bamboo Server does. Please have a look at these 2 posts which explain a bit about classes not being loaded on the agents:

* <https://community.developer.atlassian.com/t/solved-do-bamboo-remote-agents-have-access-to-pluginlicensemanager/30204/4>
* <https://community.developer.atlassian.com/t/plugin-is-not-enabled-while-running-on-remote-agent-because-of-unsatisfied-dependencies/18764/6>

Best regards,

Eduardo Alvarenga  
Atlassian Support - APAC


author: Vivek Burman
body: Got it, makes sense. Thanks for the solution