Error Message

No error is presented.

New data fields in the 14.x version of the product have the GMT/UTC time zone conversion set to not use GMT/UTC by default.  This causes the search schedule to not run based on the CA server's local time zone and to use GMT/UTC time instead.

A workaround exists to resolve this issue by adjusting the search schedule time.  This time adjustment can be any value before or after the current schedule.

1. Log onto the CA Client using an account that has the Application level permission Manage Schedules.  This permission is in the App Rule Admin role and is also built into the Vault Service Account's permissions.
2. Click on the Configuration tab > Search Schedules sub-tab.
3. For each scheduled search:
   1. Select the scheduled search name in the left panel.
   2. Click the Edit button in the toolbar above the left panel.
   3. Click the up (or down) arrow for the min setting.  For example, change 00 to 05.
   4. Click the Save button to save the change.
   5. Once saved, can edit the time back to the original time and then Save the change again, if needed.
4. Repeat Step 3 for each search schedule.  Note that inactive schedules that have no check mark in the Used column or not enabled that have no check mark in the Enabled column beside their name in the left panel can be skipped until they are used or enabled.

There is no need to restart any service or background tasks to implement this change.  Clicking the Save button updates the database with the schedule change. This change will take effect on the next run of the schedule.

This issue is currently under investigation by Veritas Technologies LLC. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.
 
Note: Customers experiencing this issue are encouraged to contact Veritas Technical Support as data is still being collected to assist in resolving this issue.