Groom job fails after upgrade to 4.2.7

Groom job fails after upgrade to 4.2.7

avatar
(anonymous user)
Product: PowerShell Universal
Version: 4.2.7


upgraded from 4.2.6 to 4.2.7 using LiteDB. now groom jobs fail with this error in the logs

2024-01-03 12:26:02.664 -05:00 [INF] Starting heartbeat job.
2024-01-03 12:26:02.668 -05:00 [INF] Script has 1 jobs to delete.
2024-01-03 12:26:02.730 -05:00 [INF] Finished heartbeat job.
2024-01-03 12:26:02.734 -05:00 [ERR] Failed to groom.
System.NullReferenceException: Object reference not set to an instance of an object.
   at lambda_method3033(Closure, Job)
   at System.Linq.Enumerable.WhereArrayIterator`1.MoveNext()
   at UniversalAutomation.LiteDBTable`1.DeleteRange(Func`2 query) in C:\actions-runner\_work\universal\universal\src\UniversalAutomation.LiteDBv5\LiteDBDatabase.cs:line 909
   at UniversalAutomation.GroomService.ScriptLevelGroom() in C:\actions-runner\_work\universal\universal\src\Universal.Server\Services\GroomService.cs:line 185
   at UniversalAutomation.GroomService.Groom() in C:\actions-runner\_work\universal\universal\src\Universal.Server\Services\GroomService.cs:line 297
2024-01-03 12:26:02.735 -05:00 [INF] Finished groom job.


I have another instance that is running on SQL that was upgraded from 4.2.5 and it is working correctly.

All Comments (5)

avatar

upgraded to 4.2.8 to see if that helps, still getting the same errors.

avatar

Same thing happened to our instance after upgrading to 4.2.6. Have you found a resolution or have you rolled back?

avatar

Still having the issue. I was hoping not to have to roll back.

avatar

I opened a support ticket and I just got a response from Adam. It should be fixed in the 4.2.9 release next week.

avatar