Work Log 5-5-25

DW camera time and date project, verify h265 profiles

Completed:

  1. Carquest Brunswick
  2. Carquest Waycross
  3. Newberry
  4. Palm Coast
  5. Middleburg
  6. Chaffee
  7. Brunswick

Work Log 5-12-2025

  1. Investigated why Newberry time was reset to 2011, I think it having the option sync with time server is to blame. The cameras were also only up 8 hours across all cameras - changed time to sync with computer
  2. Meeting

Work Log 5-13-2025

DW date time project

  1. Ellianos Starke

Work Log 5-15-2025

  1. DW Checks
  2. Downed hosts check on HIK

DW date and time completions / h265 check

  1. Tower
  2. Palatka
  3. Harper
  4. Raintree time/date sync, fixed PC timezone and synced time

Work Log 5-19-2025

  1. fixed time on brunswick dw - set dw to push time to cameras
  2. checked remaining dw settngs for camera push
  3. checked action1 for updates for dw hosts - added to to-do

Work Log 5-20-2025

  1. Checked zabbix for downed hosts - update accordingly
  2. update zabbix host to maintain security
  3. schedule zabbix update after checking for bugs in update - updated zabbix to current
  4. Double check geovision cameras to make sure they have not reset time to 2011
  5. Reached out to Lauren Mixon about Newberry being offline - confirmed ISP is down
  6. Footage request for Freddy's Glasgow office camera - theft
  7. backup zabbix database on vultr vps to interserver and linode vps, google drive x2

Work Log 5-23-2025

  1. DW host windows updates
  2. create DW host anydesk wiki entry

Work Log 5-28-2025

  1. Wiki entries for Elliano's screens
  2. Reset camera names that had no spaces

Work Log 5-30-2025

  1. Update zabbix host, update client IPs on zabbix - backup zabbix db
  2. research windows home lock screen and update issues - tested registry edits on local Home installation
  3. check forums for problematic windows updates and issues regarding tp-link usb network adapters
  4. tested action1 remote patching on local systems to determine if updates can be installed without reboot and if system will respect NoAutoUpdate registry keys

Work Log 6-2-2025

  1. Remove date time from DW hosts
  2. meeting
  3. Brunswick
  4. Chaffee
  5. Check zabbix, update ips of failed ping hosts

Work Log 6-3-2025

  1. Remove Date/Time from DW hosts
  2. Middleburg
  3. Newberry
  4. Palm Coast
  5. Waycross

Work Log 6-4-2025

  1. Remove Date time from DW hosts
  2. Palatka
  3. Starke
  4. Harper
  5. Tower

Work Log 6-9-2025

  1. Verified and/or set AnyDesk passwords for DW hosts
  2. Created DW hosts AnyDesk code listing
  3. Created entry for DW Linux host troubleshooting of AnyDesk or remote linux admin

Work Log 6-12-2025

  1. Offline hosts check on HIK
  2. DW screens check
  3. Help Desk - responded to Cartersville email, windows backup screen was up
  4. Checked help desk for video signal lost messages and checked DVRs.

Work Log 6-16-2025

  1. Offline hosts check
  2. fl264 Bartram offline - ETR 1245 per comcast support
  3. fl303 doesn't load, but doesn't error. online via app, missing from ivms altogether.
  4. fl305 ip updated
  5. ga002 time synced
  6. ga059 back door moved - not recording as of 6-14-25@0732 - date reset to 2004 - time synced && reboot. recording
  7. ga084 PF issue
  8. ga113 down - phone straight to vm - internet down - tech dispatched
  9. add lisa.kessler@tridentholdingsllc.com to trident - 365099, 365090 365056

#######################

Work Log 07-30-2025

Downed hosts check on HIK. Updated zabbix linux host, zabbix server. Will pull backup after updating some IP

Help Desk -

07-31-2025

08-01-2025

so in event viewer for CR220 Middleburg client, there is an exception code. The code is in the initial screenshot from Chad.

I restarted DW on the client, and it ran for 30 minutes before closing out. I checked event viewer, and the same code was there. I updated DW, and it ran for about 30 minutes again then errored again with “Exception code: 0xc0000409”

looking this error up, it's a buffer overrun, so either DW has an issue, or I think the memory could be at fault. I'm leaning towards the memory because no other location has this issue.

DW® #TSOR00303564 ticket

DW states that the server and clients need to be on the same exact version. Will update middleburg server tonight as to not disturb the screens during open hours.

attempt replication of middleburg dw server/client setup locally to see if app errors here, to check against potential memory issues.

older releases available at https://support.digital-watchdog.com/kb/article/997-dw-spectrum-previous-build-list/

08-06-2025 Troubleshooting CR220 Middleburg Elliano's:

“After speaking with an escalation tech, they mentioned updating the client to 6.0.5 and keeping the server on the 6.0.2 version. They also mentioned applying the .dll files anyways once the client is updated to ensure the proper files are being utilized. They mentioned too, to adjust the graphics settings either in Windows or if the graphics card has options to adjust, you would want to tinker with resolution and display settings to see if this improves stability. In DW Client you can disable features such as double buffering or blur effects, as these might help if the issue is related to graphics rendering.”

Applied changes mentioned by DW TS - timing client application runtime

9PM restarted Chaffee Client and restored DW screen

08-11-2025

08-12-2025

08-13-2025

I believe the UCG is in an error state - may need to be replaced.

08-14-2025

08-15-2025

08-18-2025

08-19-2025

08-21-2025

08-26-2025

09-08-2025

09-29-2025

10-14-2025

10-27-2025

10-30-2025

12-15-2025

01-09-2026

  1. Trident DVR checks completed
  2. other customers dvr checks