Hi,
I’m running a horde server on my Windows PC. at one point it must have taken a Windows Update in the middle of a build, and for the last few weeks automated builds won’t start because it thinks it has one in progress. I can still manually start builds. I followed the instructions in this post. The first command (repair job) succeeds with a 200, the next command 405’s, and the last command succeeds. Even after all that the orphan job is still there. Are those instructions still relevant? I recently updated to 5.8, and reinstalling the Horde server didn’t seem to solve it but some data must have been left around because it still knew about all my previous jobs from before the reinstall. there isn’t anything precious in that build history so if there is a nuke from orbit path here, I’m not adverse to just deleting any sort of DB that might be holding onto that information.
thanks