Symptoms

When attempting to set up a scheduled scan with auto-deployment, you receive a pop up error stating:

Schedule: Failed to schedule operation: 'Unkown error (0x84000005)'

Within the ST.Protect.managed.log you may see the following type of error message:

2014-07-07T17:47:38.0155053Z 0005 E OperationPresenter.cs:120|System.ComponentModel.Win32Exception (0x80004005): Unknown error (0x84000005)

  at ST.Deployment.Distribution.STScheduler.ScheduleJob(String machine, Int32 schedulerPort, X509Certificate consoleCertificate, String jobName, String command, String parameters, String workingDirectory, STScheduleRunAccount runAs, String userName, String domain, Byte[] encryptedPassword, STSchedule schedule)

  at ST.UI.Controllers.Scheduling.ScheduleConsoleTask.<ScheduleJobWithShavlikSchedulerAsync>d__5.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

  at ST.UI.Controllers.Scheduling.ScheduleConsoleTask.<ScheduleJobAsync>d__2.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

  at ST.UI.Controllers.Scheduling.PatchScan.<ScheduleConsoleTaskAsync>d__0.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

  at ST.Protect.Forms.Workflow.OperationPresenter.<TryScheduleConsoleTaskAsync>d__0.MoveNext()

Cause

The reason this error occurs is due to too many characters within the job name [1.Name this operation (optional)]. The limitation is currently 53 characters. If you use 54 or more characters in this field it will cause the above error message to occur.

Resolution

This issue has been marked as a defect by Shavlik engineering and should be fixed in a future version.

The current workaround is to only use 53 characters or less when setting the job name.

Affected Product(s)

Shavlik Protect 9.x