Seeing frequent database locked errors. This started to happen when on version 5.4.3 and now continues with version 5.6.7.
For a long time I had two scheduled scripts running. One every 10 minutes and one every 5 minutes and never ran into this error. Not too long ago I added another scheduled script to run every 10 minutes and then I started to run into this issue. I adjusted the schedules so that the jobs would not run at the same time and that did not help. Right now, I’ve disabled the other scheduled scripts and have only 1 running and i’m still running into this issue.
Is there perhaps some grooming needed on the database? Cleanup of old events or log files? Ultimately, I will migrate to a SQL database but i’m not ready to do that yet.
I am still seeing this error even when it is only one job running at a time. This is going to be a big problem for me as we’re about to kickoff a project where scheduled tasks need to be able to run consistently.
im also getting those errors recently.
its very annoying because its eating all ram and when i log into system in the morning is either already dead or is working so slow that needs to be restarted anyway
its getting kind of critical for me…
2025-10-08 14:03:17.914 +02:00 [ERR][PowerShellUniversal.Automation.ExecutionService] Failed to report progress
Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 5: 'database is locked'.
at PowerShellUniversal.Extensibility.EFTable`2.Update[TProp](T item, Expression`1 updates) in D:\a\universal\universal\src\PowerShellUniversal.Extensibility\Persistence\EFTable.cs:line 332
at PowerShellUniversal.Automation.ExecutionCallback.ReportProgress(JobProgress request) in D:\a\universal\universal\src\PowerShellUniversal.Automation\ExecutionCallback.cs:line 103
We had a support case come in about something similar but I’m not sure if it’s related at the moment. Feel free to comment on that issue as well and use it to track any progress.
health checks look good. I also want to add that this error only seems to happen with scheduled scripts. I have apps that also submit jobs and those never run into the issue. in addition it looks like the schedules are not working properly. I have two schedules. one to run a script every 5 minutes another to run a script every 10 minutes and they do not run at the same time. I can see that they do not always run when expected.
I starting seeing this as well in 5.6.6 or.7, but seemed to have cleared up in 5.6.8 (for me). I also had just setup git sync before the error showed up. But no issue so far…
Besides the database lock issue, i’m having problems with scheduled tasks simply not running according to the schedules. this is probably a different issue but I did mention this before in this thread. here’s a script set to run every 10 minutes and you can clearly see it does not.
If the database is locked, lots of things will fail to work. I have a call with another customer that has a similar issue this morning. I’ll update this thread and the issue with any findings.
things are getting worse for me now. not only are schedule tasks not running but even when I try to manually submit a job it never runs and says it being queued. i’ve tried to restart services several times and the issue remains.
I’ve added this at the top of the scripts i’m trying to run and they are still getting stuck in the queued state. $PSDefaultParameterValues = @{ '*:ProgressAction' = "SilentlyContinue" }
one of my problems was that I had one script set to only execute one instance at a time. and since I have a few jobs for that script stuck in the cancelling state, it was keeping new instances in the queued state. so at least I can manually execute jobs again even though the scheduler is still not working properly.
