This article explains how to resolve the 'Could not connect to net.tcp://servername:Port/LogonService... TCP error code 10060' error in Access Supply Chain. You'll need server access or IT support to carry out these steps.
Could not connect to net.tcp://servername:Port/LogonService. The connection attempt lasted for a time span of 00:00:21.0513982. TCP error code 10060: 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 {Server IP Address}:{ASC Port}. (EndpointNotFoundException)
In the title and the error message above, servername, Port, {Server IP Address} and {ASC Port} are placeholders. They will show as your own server's actual name, IP address and port number rather than this literal text — so your error message will reference your environment's details, not the word "servername" itself.
Important: This needs to be carried out by a system administrator, your IT support, or a member of the ASC support team.
Confirm that the ASC server is up and that you can log into Access Supply Chain on it. If you can log in on the server, this is generally a networking issue. If you cannot log into Access Supply Chain on the server, this is an issue with AccessAccounts.Accounts.Server.exe. To resolve this:
Important: Make sure all users are logged out of the system before stopping any services. If users remain logged in when the services are stopped, data corruption may occur.
Ensure all users are logged out of the system.
Open Services on the server. (Win + R, type in services.msc)
Select Access Supply Chain Server, then click Stop.
Select Micro Focus CCITCP2 daemon, then click Stop.
Select Micro Focus Licence Manager, then click Stop.
If any of these services do not stop, open Task Manager and end any running instances of AccessAccounts.Accounts.Server.exe, ASCXX.EXE, CBLEXECS.EXE, NETLAUNCH.EXE, or SupplyChain.EXE.
Return to the Services window. Select Micro Focus Licence Manager, then click Start.
Select Micro Focus CCITCP2 daemon, then click Start.
Select Access Supply Chain Server, then click Start.
Select Access NFP Server, then click Start.
If the service does not restart, check that the SQL Server running your ASC databases is running and accessible.
Antivirus and firewall port settings
Antivirus software or a firewall blocking the required ports can also cause this error, as it can prevent the server's net.tcp LogonService connection from being established. Ask your IT department or third-party IT provider to check that antivirus and firewall exclusions are configured correctly on the server.
The following ports must be added to both the inbound and outbound firewall rules. These changes must be made by your IT provider and cannot be made by Access Support.
Port | Protocol | Description |
6200 | TCP | Application service |
86 | UDP | COBOL Service |
1433 | TCP | SQL Service |
1434 | UDP | SQL Browser (only required if multiple SQL instances are used) |
50000–65000 | TCP | Random client ports |
If antivirus software is installed on the server, add an exclusion for the Access Supply Chain application and service executables, then test the connection again. If the connection succeeds once the exclusion is added, the antivirus software was blocking the required port.
Other possible causes
If restarting the services does not resolve the issue, consider the following additional causes:
Network or connectivity issues on the server may be preventing users from connecting.
Conflicting software installed on the server can cause this issue. A known example is LogMeIn Hamachi.
If needed, you will need to restart all the services . If it is a networking issue and the server is set to respond to pings, ping it from one of the users' machines. It could be a firewall issue, or the server may not have come back up correctly after a power outage. This will need investigation by your IT support.
If you need further help, contact Access Support.