Network Management

Time mismatch between Job Schedule Time and Next Run Date in NCM

This article explains why there may be a difference in the time when scheduling a job and the Next Run Date in NCM.

First published date

11/8/2018 2:10 PM

Last published date

11/8/2018 2:10 PM

Overview

This article explains why there may be a difference in the time when scheduling a job and the Next Run Date.

Product section

Network Configuration Manager

Cause

The mismatch is caused by the fact that the Job Schedule time is set to use the UTC database time zone, but the Next Run Date will display the time using the local time of the machine which you used to access the Orion Web Console.

Resolution

Currently there is no way of changing this as the database time zone is hard coded in the application, and Web Console is set to use the browser time zone, which is taken from the machine's local time.

The scheduled job will run based on the UTC time zone, so the time in which you want to run it must be converted to UTC.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.