ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Wrong Shared Schedule creates if 'Monthly' repeat is set


Article ID: 175077


Updated On:


Management Platform (Formerly known as Notification Server)


Problem is that if you create a shared schedule with 'Monthly' repeat and set 'Last' Wednesday, then it saves with 'First', 'Third' instead of 'Last'.

Steps to duplicate issue:

  1. Open SMP Console -> Settings -> Notification Server -> Shared Schedules
  2. Click 'Add Schedule'
    • Set 'Monthly'
    • Set 'The Last' 'Wednesday'
    • Save changes
  3. Open Task Scheduler library on this NS and check what custom shared schedule has 'The Last' - 'Wednesday' -> see result -> it has 'First', 'Third' instead of 'Last'.


Known issue. Issues between scheduling v1 vs v2 API used in Shared Schedules.


ITMS 8.5, 8.5 RU1, 8.5 RU2


This issue has been reported to the Symantec Development team. A fix has been added to ITMS 8.5 RU3 release.

As a workaround, please perform the steps below:

  1. On your SMP, open 'CoreSettings.config' file from "C:\ProgramData\Symantec\SMP\Settings\"
  2. Find there this setting name "ScheduleManagerInterop" and set it to "0"

    <!-- If greater than zero - we are going to use Scheduling V2 API -->
      <customSetting key="ScheduleManagerInterop" type="local" value="0" />

  3. Save changes and close CoreSettings.config file
  4. Now open "Task Scheduler Library" (Scheduled Tasks) and manually run "NS.Weekly.{ab7141ed-e03a-48e5-9051-a71b5912b7f2}" task to re-create all available schedules from the database in "Task Scheduler Library".
  5. Check whether your custom shared schedule has now correct 'start time', like 'Last' Wednesday.


Additional Information

224511 "Cannot create or edit shared schedules"