Categories
Knowledge Support Support exacqVision Client exacqVision Server Categories Products

Address Found but Not an exacqVision Server

Description 

The exacqVision Client fails to connect to the exacqVision Server with the status message “Address found but not an ExacqVision Server. Reconnecting.” This is typically caused by either an incorrect system IP address or the exacqVision Server service is not running on the NVR.

Products

  • exacqVision Client
  • exacqVision Server
  • Windows OS

Steps to Reproduce 

  1. From the exacqVision Client access the Add Systems page (Config (Setup) Page > Add Systems)
  2. View an existing or add a new System
  3. Check the Status of the system in the System List

Expected Results 

  • Status = Connected.

Actual Results 

  • Status = Address found but not an exacqVision Server. Reconnecting.

Solution

If the IP address entered for the system is correct then this is an indicator the exacqVision Server Service is not running on the NVR.

Troubleshooting

exacqVision Client Machine

  • Confirm the IP address of the exacqVision Server matches what was entered in the exacqVision Client

exacqVision Server Service

  • On the NVR, check the exacqVision Server Service
  • Open Services by clicking the Windows (Start) button and typing Services.
  • Locate the exacqVision Server Service
  • Check the status and Startup Type
  • Normally the status should be running, and the Startup Type is Automatic
  • If the service is not started then highlight the service and either click Start the service on the left or right-click and choose Start from the popup window
  • If the service is started or starts then the exacqVision Client should be able to connect
  • In the event the service does not start an error message will be displayed

Windows Time Service

  • The Windows Time service is a dependency and must be running when the exacqVision Server service starts. Otherwise, the error message “Error 1068: The dependency service or group failed to start,” will be displayed.
  • Locate the Windows Time Service
  • Check the status and Startup Type
  • Normally the status should be running, and the Startup Type is Automatic
  • If necessary start the service and modify the services properties and set the startup type to Automatic
  • An “Error 1058: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it,” is probably indicating that the service has been disabled and you will need to modify its properties and set the startup type to Automatic.
  • Once successfully started, attempt starting the exacqVision Server Service.




<br>

Categories
Knowledge Support Support exacqVision Server Categories Products

Removing exacqVision Server Dependency from RTSP Server Integration (Windows Only)

Issue

This article applies only to the stand alone RTSP Server Integration not the built-in RTSP support available in exacqVision Server version 19.12 and higher. 

The original stand-alone RTSP Server has the exacqVision Server listed as one of its dependencies.  This causes scripts to fail and has been observed to prevent the following: 

  • Failover/Failback 
  • Silent Install 
  • Remote Update

<br>

Resolution

To remove exacqVision Server dependency from RTSP Server integration. (Windows Only)

<br>

Stop RTSP Server service.

  • Open services.msc.
  • Find and click on service with name “exacq RTSP Server”.
  • Click stop.

<br>

Back up the registry.

  • Open regedit.exe. Note: Administrator access may be needed
  • Right-click “HKEY_LOCAL_MACHINE” and click “Export”.
  • Save exported “.reg” file.

<br>

Update the registry entry for exacq RTSP Server.

  • Double-click the exacqRTSP.reg file
  • This will remove the integrations dependency on exacqVision Server automatically.