The following are the most common error messages that will be recorded in the logfile:


  • System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 51.140.189.52:443
    This suggests that proxy server details are required.

     
  • System.net.sockets.SocketException: No connection could be made because the target machine actively refused it 51.140.189.52:443
     This suggests that a firewall is blocking the connection. Please set a rule to allow outbound traffic to https://nhsiingest.servicebus.windows.net/ on port 443.

     
  • System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
    As above, this suggests that a firewall is blocking the connection. Please set a rule to allow outbound traffic to https://nhsiingest.servicebus.windows.net/ on port 443.

     
  • System.Threading.Tasks.TaskCanceledException: A task was canceled
    This suggests an issue with the remote server. It may be temporary, so please try again later

     
  • System.Net.WebException: The remote server returned an error: (407) Proxy Authentication Required.
    This might suggest that no proxy server is actually needed where one has been set. Otherwise the proxy requires authentication details, which can be added manually in the BISV_ScheduleServiceBus.xml

     
  • System.Net.WebException: The remote server returned an error: (504) Gateway Timeout.
    This suggests that there is an issue with the proxy server. Remove/amend the proxy server details or review the status of the existing proxy server.

 

If the issue you’re experiencing persists following the guidance given in this document, email beautiful-support@vitalhub.com , supported by a copy of your logfile.