KB: Connection Errors During Enterprise Server Access

Altium On-Prem Enterprise Server Altium On-Prem Enterprise Server
When connecting to the Enterprise Server, repository or configuration information may fail to load and connection reset errors may reference port 443 while using HTTP. This can occur when the Enterprise Server IIS site bindings and the HTTPS port configured in LocalVault.ini do not match. Verify the IIS bindings and LocalVault.ini configuration, ensure that the configured HTTPS ports correspond, restart the server after making changes, and test the connection again. If the HTTPS configuration is correct but the issue persists, firewall, antivirus, or other security software may be blocking communication.

Solution Details

Connection Errors During Enterprise Server Access

When connecting to the Altium On-Prem Enterprise Server (AES), the following errors may occur:

The connection with the server was reset - URL:http://servername:443/vcs/VcsWebServer.asmx
SOAPAction:http://tempuri.org/GetRepositories

AND

The connection with the server was reset - URL:http://servername:443/tc2/WebService.asmx
SOAPAction:http://tempuri.org/GetConfigurations

These errors may occur when attempting to retrieve repository or configuration information from the Enterprise Server.

HTTP and HTTPS Configuration Mismatch

The error indicates that port 443 is being used with HTTP rather than HTTPS, which is an incorrect configuration. This can occur when the IIS site bindings and the settings in LocalVault.ini do not match. If HTTPS is already configured correctly and the issue persists, communication may be blocked by a firewall, antivirus solution, or another security application.

Configuration Areas Requiring Verification

  • Verify the Enterprise Server IIS site bindings.
  • Verify that the settings in LocalVault.ini match the IIS binding configuration.
  • Confirm that the configured HTTPS port in LocalVault.ini corresponds to the IIS HTTPS binding.
  • If configuration settings are correct, investigate firewall, antivirus, or other security software that may be blocking communication.

Update Port Settings and Restart the Server

  1. Open IIS and review the Enterprise Server site bindings.
  2. Confirm that HTTPS is configured correctly and that the site is bound to the intended port.
  3. Open the LocalVault.ini file.
  4. Verify that the HTTPS port value matches the IIS HTTPS binding.
  5. If the Enterprise Server binding has been changed to use standard HTTPS port 443, update the corresponding setting in LocalVault.ini from HttpsPort=9785 to HttpsPort=443.

  1. Save the changes.
  2. Restart the server computer after updating LocalVault.ini.
  3. Test the Enterprise Server connection again.

Additional Notes

If HTTPS is configured correctly and the issue continues after verifying IIS bindings and LocalVault.ini, review firewall, antivirus, and other security applications with the IT team to determine whether communication is being blocked.

References

Если вы обнаружили проблему, выделите текст/изображение и нажмитеCtrl + Enter, чтобы отправить нам свой отзыв.