Network Management

VNQM Data Date Time is inaccurate, or Time zone code is not found.

The VNQM data shows the date/time inaccurately or shows that the time zone code is not found, which returns the UTC offset to 0.

First published date

4/8/2024 2:18 PM

Last published date

2/19/2025 9:07 PM

Overview

The VNQM data shows the date/time inaccurately or shows that the time zone code is not found, which returns the UTC offset to 0.
The reports, widgets or web interface will show date/time offsets inaccurately, such as a 1-hour off difference.

Product section

VoIP & Network Quality Manager

Cause

The Tiimezone codes for offsets are not present in VNQM.
This is a bug in the product.
The errors in the VNQM logs will show a similar message below; this particular message involves Hawaii Standard Time:

WARN  SolarWinds.Orion.IpSla.BusinessLayer.Polling.Cli.TimeZoneManager Dequeue - Timezone code HST not found. Returning UTC offset 0.

Resolution

Upgrading to 2024.4 will resolve the issue as this is a bug in the product.
For a possible workaround, please generate a support case.

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.