Baisangur

To reduce the CPU load, the following is recommended: Use different video camera streams for the purposes of displaying the video signal on the Video Surveillance Monitor, recording to the archive, and using video analytics. By doing this, you can, for example, display a lower quality video on the Monitor, and record a higher quality video to the archive. Complete guide: Configuration of multistream video Use automatic selection of video camera streams to display the video signal on the Video Surveillance Monitor. Complete guide: Configuring an auto select of video stream for displaying

The interface windows aren't displayed on the Server or the Remote Client in the following cases: The corresponding Screen object isn't assigned to the required computer. The full article: Assigning the displays to the operator workstations The corresponding Screen object or interface object is prohibited by the rights of the current user. The full article: Limiting access to the system objects administration, control and viewing functions The ports are closed for the required interface objects. The full article: The list of TCP ports used in Axxon PSIM The wrong Screen object was selected for display. Click the Interfaces button on the Main control panel and select the correct Screen. The full article: Main control panel Windows 10/11 update can also be the reason why interface objects aren’t displayed. For example, if KB5020695, KB5019961, KB5020617 updates were installed, Windows may stop initializing the previously configured printers. Since the printers are used by some interface objects, the display problems occur. To fix this, you need to reconfigure the connection to the printers in Windows and restart Axxon PSIM.

This error can be caused by various reasons. If this error was caused by the event log database overflow, then to fix it, do the following: Shut down Axxon PSIM on the server where the database to be changed is stored. Launch the SQL Server Management Studio utility and connect to the server, which caused an error. Complete guide: Viewing Axxon PSIM database Go to the properties of the Axxon PSIM database. In the Axxon PSIM database properties, set the Recursive Triggers Enabled option to True. Click the OK button to save the changes.

To complete the following steps, it is required that SQL Server Management Studio is installed on the server. If this type of SQL error occurs, it means that the database has grown too large. Usually it happens when a large number of events are written to the PROTOCOL table. To fix this problem, do the following: Clear the PROTOCOL table partially or completely: If the PROTOCOL table contains important events that should not be removed, or if the Report System is used, then you should manually remove some events from the event database. Do it as follows: Determine which events can be removed from the database. Remove these events using SQL queries. Complete guide: Removing the events from the PROTOCOL table using SQL queries After that, go to step 4, and then sequentially complete steps 2 and 3. If the PROTOCOL table does not contain important events, and the Report System is not used, then manually delete the PROTOCOL table for the server with error. Complete guide: Removing the event table from the Axxon PSIM database Compress the database. Complete guide: Compressing the database size Set the minimum parameters for storing log files for the database. You can do it either on the settings panel of the Axxon PSIM section in the tweaki.exe utility, or by using the registry keys. Complete guide: Enabling and configuring the debug mode of Axxon PSIM software Set a time limit for storing events in Axxon PSIM. Complete guide: Configuring events logging You can also disable event logging using the ddi.exe utility. Disabled events can be deleted, which also helps clean up the database. For this, use SQL queries. Complete guide: The Events tab

The Axxon PSIM database can go into Suspect mode because of a sudden server reboot or file system damage. To restore the database from this mode, do the following: Check the system disk for errors. If there are some, fix them and check again. If no errors were found at step 1, start testing and restoring the database. Complete guide: Restoring the Axxon PSIM database from the Suspect mode

Yes, the Axxon One Server will be available under the new NetBiosName or IP address from the external network or under the Server name in the Axxon One configuration from the internal network. The NetBiosName of the computer may contain up to 15 characters. By default, the Server name in the Axxon One configuration corresponds to the NetBiosName of the computer on which it is installed. You can change the Server name from the Backup and Restore Utility. Full article Changing the Server name

Axxon One apps are available for: iOS and Android platforms. Example URL with standard Server settings for Axxon One: Axxon One 1.0: 192.168.0.10:80 Full articles: Direct Server connection in the AxxonNet iOS mobile client Direct Server connection in AxxonNet client on Android OS Apps are described here: General information about the AxxonNet iOS mobile client General information about the Android mobile client

To remove Axxon One and prerequisites, do as follows: Remove Axxon One and delete the configuration. Full article Removal Go to Control Panel → Programs. Perform the uninstall of Postgres NGP, Axxon DetectorPack, Drivers Pack, Guardant Drivers. Clear the folder: C:\Program Files\AxxonSoft. Clear the folder: C:\Program Files\Common Files\AxxonSoft. Clear the hidden folder: C:\ProgramData\AxxonSoft. Remove the registry entry through the Registry Editor: In х64 systems: \HKEY_LOCAL_MACHINE\SOFTWARE\AxxonSoft. In x86 systems: \HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\AxxonSoft.

Consolidating the Servers from different networks separated by routers into the Axxon domain, as well as connecting the Clients to the Server behind NAT is described in the Using Axxon One with NAT section.

To restore a configuration, use the Restore mode in the Backup and restore utility. For a complete guide, see Restoring a configuration. Attention! We can guarantee that your configuration will be fully restored if: the backup was created on the same software version (including the build number); the backup was created on the same PC (for licensing without the Guardant key).

To reduce the CPU load, it is necessary to configure hardware decoding of displayed video. For a complete configuration guide, see Configuring hardware video decoding for display on the Client. Besides, the detection tool settings can affect the CPU load − for example, decimation, fps, etc. Settings of each detection tool are described in the Configuring detection tools section. Please note that the number of detection tools should match the CPU capabilities. You can check it in the platform calculator, and the calculation algorithm is described in the Recommended platform calculation section.

Cross-System Client empowers users to connect to multiple servers on various domains and in different systems from a single client workstation. Full article: Cross-System Client For this to take place, the following conditions must be true: The Professional or Enterprise or Unified license is enabled on each server to which the client connects. How is Axxon One licensed? How to activate a license in Axxon One? Connection to all Servers made via with the same user name/password combination on each Axxon domain. To configure connection to servers from different domains, go to Settings → Options → Automatic connection. Full article: Configuring Cross-System Client and autologon

Ping the camera. Check that the camera is available in the Web-Interface. Check the connection settings (port, login, password) in Axxon One. If the camera's integration with Axxon One is via vendor protocol, verify that the model and version of the firmware in the documentation and on the camera are the same. How do I check if my camera is integrated with Axxon One? If the camera is connected via ONVIF: Check the connection in the ONVIF Device Manager. Synchronize time between camera and Server. Enable the ONVIF option on the camera, if there is one. If the camera is connected through the RTSP protocol, check the connection in the VLC Media Player. Check the network. The firewall, antivirus, SmartScreen, UAC and other software can use the port you want for connecting to the camera. Make sure that Axxon One license file allows the sufficient number of video channels. If channels are not enough, please contact your AxxonSoft manager to request the new license file. How do I see features available under the activated license?

In Axxon PSIM, the Servers and Remote Administrator's workstations (RAW) configuration parameters are being kept in the distributed database. The local copy of the distributed database is kept on each Server and RAW. To ensure the Axxon PSIM distributed operation and data replication (i.e. synchronous implementation of modifications in the local copies of the main database), the local copies of databases must be synchronized with one another. In general, Axxon PSIM is set up in the way that the synchronization of all databases is executed from one centralized database only which is located on the administration Server. The database synchronization setup is implemented with the help of the Database update (idb.exe) utility and described in the documentation. The full article: Database synchronization setup You can separately set up the configuration database synchronization and event protocol databases. The full article: Synchronizing the databases of servers and remote workstations

To transfer the Axxon PSIM database from one server to another, you need to create a database backup copy on the source server and then expand it on the new one. The full articles: Creating the database backup copy Restoring database from backup copy MS SQL Server 2014 is supplied as the part of the Axxon PSIM distributive.