Skip to content
Ask A Question
  • There are no suggestions because the search field is empty.

TOP Server - Configuration Client is not connecting to the Runtime Service

How do I fix the event log error: Connection Attempt to runtime failed: “This operation returned because the timeout period expired”. 

This issue typically occurs due to the following possible reasons:
  1. Limited resources available 32-bit application
    • Memory usage high
    • Excessive Client count
    • Excessive Client tag requests
  2. Wrong communication port setting [port]
  3. TOP Server Service stuck in “Stopping or Stopped”

How to Solve Reason #1: 

  • Check available resources Windows Task Manager
3976 - WindowsTaskManagerResources
  • Memory usage
    • High project tag count
    • Excessive Client count
    • Excessive Active Tag count
      • (Check Clients connected and Active tags lower right-hand corner of configuration utility screen)
        3976 - ClientCount

How to solve Reason #2:

  • Verify port number configured for configuration client
    • Go to TOP Server Administration > Settings... > Configuration tab 
    • Set Communication using port = 32408 (default)
      3976 - TOPServerPortNumber

How to solve Reason #3:

  1. Open system Services app
  2. Find TOP Server [version] Runtime
  3. TOP Server Runtime service requires a status of “Running”
    3976 - ServicesService
  4. If stuck in Stopping, proceed with force stopping the service:
    1. Open Command Prompt to find PID
    2. Type: sc queryex TOPServerV[#]
    3. Take note of PID #
      3976 - ForceStopService
    4. Next force kill the service by PID in Command Prompt
    5. Enter command: taskkill /f /pid [PID X] (example: taskkill /f /pid 999)
    6. Return to Windows Services and restart TOP Server Service
      3976 - RestartService
    7. Open TOP Server Configuration Application
    8. Check for successful connection
      3976 - ServiceGood