Month: December 2011

When experiencing network connection or discovery issues, one possibility is that you have more than one service attempting to use the same port number.

To further investigate and attempt to resolve exacqVision port conflicts, complete the following steps:

Begin by opening the server logs. If you are unable to start the exacqVision Server service or are unable to connect to it from your client you will need to open the logs manually using a text editor, such as ‘Notepad’, on Windows.

On Windows systems, the server log files are located in:
C:\Program Files\exacqVision\Server\logs\

The files located in this directory are named by date, so you will likely want to open the latest one. When opened, it should look similar to this:

In this example, you can see an error message that includes “ONVIF camera detection is not available. Could not bind receiving socket. Address already in use [239.255.255.250:3702].”

The important part of the message is the port number following the IP address (in this case, 3702).

Open a command prompt with elevated status. To do this, right-click Command Prompt and select ‘Run as Administrator’.

Run the command netstat -a -n -o. This displays the ports in use and their Process ID (PID). It should look similar to this:

Note that the ‘Local Address’ column displays information in IP Address:Port format.

Look for the port that matches the port shown in the error message in the exacqVision log file (3702 in the example). Scroll down if necessary to reveal all ports:

When you find the port, look at the ‘PID’ in the far-right column (in this case, the PID for 3702 is 3428).

Right-click on the Windows taskbar and select ‘Task Manager’. Click on the ‘Services’ tab and sort the ‘PID’ column by clicking the ‘PID’ column header. It should look similar to this:

Find the service that has the matching PID from the previous step. In this example, we see that the service associated with the PID is ‘FDResPub (Function Discovery Resource Publication)’. If more than one service appears with a matching PID, take note of this for use in a later step.

Open the ‘Services’ window from the ‘Control Panel’ or by searching for ‘Services’ within the Windows (Start) menu. It should look similar to this:

Find the service identified in the previous step. In this example, the status of the ‘Function Discovery Resource Publication’ service is “Started”; this is why ONVIF cameras cannot be found by the network scan.

Right-click the service and select ‘Stop’. The service’s entry should no longer list a status, as shown here:

Change the ‘Startup Type’ to ‘Manual’ or ‘Disabled’ within the ‘Properties’ dialog if necessary.

Determine whether there is still a port conflict. For example, in the case of the undetected ONVIF cameras, you should run the network scan in exacqVision Client.

If the port conflict still exists, and more than one running service matched the PID, restart the service that you stopped and then stop the next service with the same PID. Check for the port conflict again.

If the port conflict is not resolved even after disabling each of the services with the same PID, there are most likely other issues outside of Windows and exacqVision.

NOTES

• When you identify the conflicting service, be sure you know how important the service is before you disable it permanently. If the service is important enough to keep enabled, you can simply stop it temporarily to accomplish what you need to do, and then restart it when finished.<br><br>
• This article was based on a Windows 7 platform, but the process should also work on other Windows platforms. The specific services shown here might vary by platform.

<br>