Description
When enabling Remote Connectivity for an exacqVision Server on the Remote Connections page within the Client, the Connectivity Status column displays an error.
Issue
Examine the message displayed in the Connectivity Status column on the Remote Connections page or the exacqVision System Logs.
Disabled: SBS: listener stopped 1-CANCELLED
May be caused by missing frpc service.
- Check the exacqVision Server directory for frpc.exe
- If frpc.exe is missing it may have been removed by antivirus software.
- If frpc is present, it may also be blocked from an antivirus software application.
- Create an antivirus exception for frpc.exe within the directory and reinstall the exacqVision Server application over the top of the existing install.
- Confirm frpc.exe is not removed and is running.
- Disable and re-enable Remote Connectivity for the system.
NOTE: Make sure to add the file location to the exceptions:
file: C:\Program Files\exacqVision\Server\frpc.exe
Check the Client to make sure FRPC shows up properly in the plugin section.
If FRPC does not show up in the server folder- restart the exacq Server Service.
Check the install path as well to make sure that FRPC is in the server folder.
If FRPC does not show up in the server folder- reinstall the software.
Disabled: SBS: listener stopped 13-Received RST_STREAM with error code 2
Likely caused by a networking issue.
connect failed 14-Received http2 header with status: 502
connect failed 14-Received http2 header with status: 503
502/503 are HTTP response codes indicating a switchboard error.
A command for windows can be ran to see if the server can reach the switchboard properly. Some Firewalls might not be able to reach the switchboard properly and would need the inbound and outbound rules set up properly to reach this url.
We have seen a few cases receiving this error prior to resolving the switch routing.
connect failed 14-Received http2 header with status: 502
Run Powershell as ADMIN and run the following command.
tnc -p 443 switchboard-prod.exacqiq.com
In most cases we have found that restarting the services and disabling and re-enabling the servers affected in the Remote Connectivity section of the client will allow them to connect properly seen below.
<br>