Troubleshooting

The network is unable to connect to the DVR, NVR or camera.

Several issues may be responsible:

Pay attention to the fault cause on the device and network Property Sheets.
If Use Tls is set to true on the network Property Sheet, confirm that the device has a signed server certificate or approved and accepted self-signed certificate. For most devices you will find this certificate in a User Key Store. For the XProtect native process, carefully review the “XProtect requirements” topics in this guide.
Confirm that the Address properties are correct under the network’s Http Config section.
For the MilestoneXProtectNetwork, confirm that the Native Process Port on the network Property Sheet is configured correctly.
If communicating over the Internet, confirm that the WebService’s ports and Https properties are correctly configured.
If Fault Cause reports either of these errors:
DVR Connection Fail: Failed to access the WSDL at: https://[IpAddress]:9117/?wsdl, where [IpAddress] identifies the controller

HTTP transport error: javax.net.ssl.SSLException

the fault may be due to failed certificate hostname validation. Confirm that the XProtectManagementServer is connected and its Status reports {ok}.

The browser console reports a Cross Origin Resource Sharing (CORS) issue while streaming video from a Milestone camera.

You may need to configure the Milestone Mobile Server. To configure this server, navigate to this configuration executable and run it:

%PROGRAMFILES%\Milestone\Milestone Mobile Server\VideoOS.MobileServer.Service.exe.config

To XProtect 2017 R3 (11.3a), add:
<add key=”AllowOrigins” value=”http://yourWebApplicationHost” />
To XProtect 2018 R1 (12.1a) and later versions, add
<add key=”Access-Control-Allow-Origin” value=”http://yourWebApplicationHost” />

The value corresponding to the "Access-Control-Allow-Origin" key could have multiple site entries separated by comma(s), as well as an asterisk (*) symbol (wildcard) for all the sites.

When I added a management server, instead of connecting I get this error, “Failed to access the WSDL at: <server IP address>. It failed with: Could not acquire peer certificate to process exemption. .

The system is trying to connect to the bridge service (native process) between the station and the management server. The bridge service makes the connection to the management server. You must configure this service and supply a certificate before the driver can make a successful connection.

On the MilestoneXProtectNetwork’s property sheet, confirm that the Native Process Port is configured correctly.
Confirm that a self-signed certificate is attached to the native bridge.

When I added a management server, instead of connecting I get this error, “Failed to access the WSDL at: <server IP address>. It failed with: certificate validation, failed hostname validation.

The certificate exists in the Window certificate store, but it has not yet been approved in the Workbench Certificate Management Allowed Hosts list.

When I added a management server, instead of connecting I get this error, “HTTP transport error: javax.net.ssl.SSLException: failed certificate validation, failed hostname validation

The certificate acting as a local host must be approved in the Workbench Certificate Management Allowed Hosts list.

Client received SOAP fault from the server: log to find more detail regarding exact cause of the failure.

This error indicates that the station can connect to the native process bridge, but not on to the management server. Confirm the XProtectManagementServer Connection and Auth properties. And make sure that the management server itself is up and running.