Scheduled tasks on SnapCenter Server not running
Applies to
SnapCenter Server (SC)
Issue
- SnapCenter tasks such clone lifecycle, remove secondary backups, and purge jobs that are scheduled in Windows Task Scheduler on the SnapCenter Server stop running without an error shown in the SnapCenter UI.
- The jobs run successfully when triggered from the SnapCenter UI, SQL Agent (clone lifecycle), or copying the job syntax and running directly from PowerShell (logged in as domain user).
- The joblauncher.log (C:\Program Files\NetApp\SnapCenter\SMCore\log) returns an error when the jobs are launched that the name of the cmdlet (i.e. "New-SmClone" for clone lifecycle jobs) is not recognized.
2023-05-03T03:30:02.1925276-05:00 DEBUG Smcore PID=[364] TID=[1] Enter Job Launcher
2023-05-03T03:30:02.7081557-05:00 ERROR Smcore PID=[364] TID=[1] An error occurred while invoking the powershell cmdlet.System.Management.Automation.CommandNotFoundException: The term 'New-SmClone' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
at System.Management.Automation.RunspaceInvoke.Invoke(String script, IEnumerable input, IList& errors)
at SnapMgrHelper.SmPsHelper.InvokeCmdlet(String strCmdlet, Collection`1& result, IList& lstErrors)
2023-05-03T03:30:02.7081557-05:00 ERROR Smcore PID=[364] TID=[1] ErrorCode (-1), ErrorMessage (The term 'New-SmClone' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.)