cancel
Showing results for 
Search instead for 
Did you mean: 

SAP BPA Desktop Agent does not accept a job (while on other PC it does)

janv7306
Active Participant
0 Kudos

Dear experts,

Could anyone help me with the issue in title? There is not much more to say. I have already:

* reinstalled Desktop Agent (3.22.45)

* re-registered Tenant within the Agent

* removed all attributes from the project and deployed it

* double-checked the version in project matches the Agent version

I have activated Support and Trace modes. The only suspicious records I found are:

[{"msg":"Inventory - Worker failed to update inventory","data":"\"Exit code: 2147749890. ERROR:\\r\\r\r\nDescription = Not found\\r\\r\r\n\"","component":"RUN","pid":6716,"tid":"","ts":"23/12/06 10:49:29:659","transmitter":"desktopAgent","target":"desktopAgent","level":1,"dataToRender":"\"Exit code: 2147749890. ERROR:\\r\\r\r\nDescription = Not found\\r\\r\r\n\"","status":"Error","title":""}]

resulting in: Inventory - inventoryWorker exited unsuccessfully with code 1

ping/pong works well.

The second thing to check found by network specialist is about session reset, which I am not sure whether it is related to SAP BPA or not.

Any help welcomed.

Jan

Update: I found that the Inventory error is linked to agent ability to export Inventory details. The user can usualy do it from About - (i) icon / Agent Details + triple dot icon and Copy/Export inventory... I cannot do it on the machine either.

Accepted Solutions (0)

Answers (2)

Answers (2)

janv7306
Active Participant

Dear all,

I finally succeeded in Control Tower - Agent Configuration. I removed the agent from the Agent Management list and also removed it from the registered (Agents). Subsequently, I registered again and assigned. After making changes in the Control Tower, I got to the computer again in about 20 minutes and the project was displayed among the available ones.

Also I have lowered agent version in the project from 3.22.45 to 3.22 and deployed the newer version.

So my problem is solved 😉

vbalko-claimate
Active Participant
0 Kudos

So the problem was mainly solved by restarting machine? Or removing agent and reassigning it again (aka agent registration restart)?

Maybe the agent got into some "undefined/undiscoverable" state during platform update.

janv7306
Active Participant

Hello Vlado!

I guess the root cause could be both: lowering the Agent version number in the project and removing and reassigning the Agent.

Apart from it I did no other changes.

Cheers, Jan