cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post
Level 11

clearing failed jobs

Jump to solution

Good morning everybody,

we have way to much failed job entries (no worries, the system works fine, no problems). How can we get rid of these entries?

Regards

Marcus

0 Kudos
1 Solution
Level 10

Hi Marcus,

if you don't want to wait 4 weeks for them to clear automatically, add the following to the pnServer.config.xml:

<jobs.history.failed type="System.Int32">28</jobs.history.failed>

28 (days) is the default value. Set it to 1, restart the service and wait for the normal database cleanup job to run automatically, it will clear it all.

Or when all UIs are closed, run a cmd as a user which has the ARM admin role and navigate go to the installation folder of ARM. In the bin subfolder you'll find a "app8mancommand.exe", run it with cleandatabase as additional command:

2020-01-16 14_54_41-arm.local (192.168.18.1) - Remote Desktop Connection Manager v2.7.png

This will trigger the cleanup job externally. What I noticed it will not clean 100% like the way you want it, but it should reduce the failed job drastically. When you wait for the real cleanup job the next day, it should all be fine.

Don't forget to change the value back, otherwise you might wonder where all the failed jobs went 😉

Cheers

Björn

View solution in original post

3 Replies
Level 10

Hi Marcus,

if you don't want to wait 4 weeks for them to clear automatically, add the following to the pnServer.config.xml:

<jobs.history.failed type="System.Int32">28</jobs.history.failed>

28 (days) is the default value. Set it to 1, restart the service and wait for the normal database cleanup job to run automatically, it will clear it all.

Or when all UIs are closed, run a cmd as a user which has the ARM admin role and navigate go to the installation folder of ARM. In the bin subfolder you'll find a "app8mancommand.exe", run it with cleandatabase as additional command:

2020-01-16 14_54_41-arm.local (192.168.18.1) - Remote Desktop Connection Manager v2.7.png

This will trigger the cleanup job externally. What I noticed it will not clean 100% like the way you want it, but it should reduce the failed job drastically. When you wait for the real cleanup job the next day, it should all be fine.

Don't forget to change the value back, otherwise you might wonder where all the failed jobs went 😉

Cheers

Björn

View solution in original post

Level 11

Thanks Björn for the hint. I'll give it a try

0 Kudos
Level 10

Hi Markus, if that is not working change the value and restart service. Then the DB Cleanup next day should clear it.

0 Kudos