Icinga
Start-ScheduledTask : Element not found.
On certain systems when installing the framwork we get the following error.
Start-ScheduledTask : Element not found.
At C:\Program Files\WindowsPowerShell\Modules\icinga-powershell-framework\cache\framework_cache.psm1:25123 char:5
+ Start-ScheduledTask -TaskName $TaskName -TaskPath $TaskPath;
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (PS_ScheduledTask:Root/Microsoft/...S_ScheduledTask) [Start-ScheduledTas
k], CimException
+ FullyQualifiedErrorId : HRESULT 0x80070490,Start-ScheduledTask
Does this only affect newly installed machines, not having Icinga for Windows installed before or also machines on which an update is applied?
Which version of Windows is being used for these setups? Is it just affecting a certain version or all of them?
Which version of Windows is being used for these setups? Is it just affecting a certain version or all of them?
I will get back to you on this I need to find the systems where this occurred. It is less wide spread than the TLS problem.
Which version of Windows is being used for these setups? Is it just affecting a certain version or all of them?
This is occurring on both windows server 2016 and windows server 2019. I don't think it is OS specific although these servers are Citrix servers which have been hardened. The problem is that I also have systems of the same typology which do work. So I do not know what the difference is. I may need to open a ticket for this through our local Icinga partner. Also if I run the renew certificate task it gives this error. So it is unable to correctly create this task and the install just hangs.
(scctxhodsep0002)
Bsaed on the screenshots it seems the entire state of the PowerShell modules of Icinga for Windows is not healthy. Have you been able to resolve this by a clean installation on the affected machines?
Somehow some functions including the task and not be found, which might explain on my the state is not "healthy" at the moment
Bsaed on the screenshots it seems the entire state of the PowerShell modules of Icinga for Windows is not healthy. Have you been able to resolve this by a clean installation on the affected machines?
Somehow some functions including the task and not be found, which might explain on my the state is not "healthy" at the moment
No unforntunately no, there are a few machines where for some reason the scheduled task gets corrupted/empty and a fresh install does not resolve it. Would it be possible to repeat that part of the install process manually step by step to locate the exact point of the problem? Which poweshell snippets could we try?