Due to errors, %1 cameras cannot be detected.

Due to errors, %1 cameras cannot be detected. Description %1 = Name of Camera Manufacturer %BR% This could be caused by detection socket being used. Such as port 1900(UPnP) or 3702(ws-discovery) are being used by another application(use netstat) or mDNSResponder.exe is missing from the path. Notes If Onvif discovery failed in Windows environment, check to… Continue reading Due to errors, %1 cameras cannot be detected.

Client %1:%2 unsubscribed from stream %3

Client %1:%2 unsubscribed from stream %3 Description %1 = The IP address of the Client machine. %BR% %2 = The port number the Client connected through. %BR% %3 = The Device ID for the stream displayed. %BR% User stopped viewing a camera from Client machine. Notes This is a normal message

Client %1:%2 subscribed to stream %3

Client %1:%2 subscribed to stream %3 Description %1 = The IP address of the Client machine. %BR% %2 = The port number the Client connected through. %BR% %3 = The Device ID for the stream displayed. %BR% User is viewing a camera from Client machine. Notes This is a normal message

EM Camera Permission in Postgres DB Causing High CPU usage for the Importers

Description  Some customers might have High CPU usage on their EM servers. In which the CPU runs at 100%. Product  EM- Version 23.0.3 and older. Steps to Identify the Cause  Log into the EM server and validate that the importers are running hard. Normally there will be several importer services opened and being used. You… Continue reading EM Camera Permission in Postgres DB Causing High CPU usage for the Importers