Issue:
Servers with Windows operating system (OS) fail to correctly identify non-Daylight-Savings-Time (DST) time zones and prevent the local client searches from working for time periods recorded during DST.
Symptoms:
- Sporadic playback on the server using the (internal) local client and no issues with searching from the (external) client workstations. In other words: search works fine from workstations, but not on the server itself.
- With direct search enabled, search shows timeline filled at the right side and playback works but doesn’t fill-in the left side of the timeline. Disabling direct search fills the timeline but playback is broken.
- Recorded files are placed in the correctly labeled video folders.
- Downgrade of the client does not fix this condition, but downgrade of the server to version 9.4 or earlier does.
Root Cause:
Server 9.7.27 introduced an issue with how the server software queries for the currently-configured time zone from the Windows OS. The Linux OS is NOT affected by this issue. When impacted systems are configured to a time zone that does not observe DST, like any of the “(UTC+/- xx:xx) Coordinated Universal Time +/- x” zones and others, the server will erroneously assume DST is observed, and relay that information to the client. As a result, the local client may fail to search video during the DST part of the year. Conversely, a remote client search will continue to work normally.
Workaround:
The options are (1) to search from the client workstations ONLY, or (2) to downgrade to server version 9.4.
Introduced In:
Server version 9.7.27
Fixed In:
Server version 19.05.18+ and Client version 19.03.9+