Remote Viewer connection issues are often due to one of the following:- The Remote Viewer is not enabled in the Engine's configuration
- The Engine is stuck in Startup and not yet listening (v6.35 and earlier)
- The Engine is unable to listen on the configured port
- The Remote Viewer is being blocked by a firewall
- The Engine has already reached its licensed Remote Viewer connection limit
Verify that the Remote Viewer is enabled in the Engine's configuration
- Run the Configurator and open the configuration file for the Engine
- Select "Remote Viewer & Dial-in" from the left menu
- Make sure that "Enable remote access from the TopView Remote Viewer" is checked

Verify the the Engine is not in the Startup state (v6.35 and earlier)
In TopView v6.35 and earlier, the Engine does not start listening for Remote Viewer connections until it is in the Running state.
In Admin Tools, click the "Remote Viewer Connections" link in the left menu.
"Listening" must be True on the "Selected TopView Configuration" tab.
- If listening is False and the Engine is not in the Startup state (v6.35 and earlier), the configured port may already be in use by another TopView Engine or another application.
- Select "Application Log" from the left menu of Admin Tools
- If the Engine was not started or restarted today, select the daily application log file for the day that the Engine was last started or restarted
- In the "Message containing text" box enter
Remote Viewer - Click the [Refresh] button
- Look for messages similar to "error setting up socket for listening.... only one usage permitted"
- If you see this message you need to select a different listen port in the Engine's configuration
- If listening is True
- Run the Remote Viewer on the TopView machine to see if you can connect
- If you can connect but remote users are unable to connect, the issue is most likely due to a firewall
- The firewall could be on the TopView server or client-side. Ensure communication over the specified port is allowed on both systems.
To test whether the client can connect to the Remote Viewer port, use either of the following methods:
- telnet to the port from the client machine:
- Run the following in a command prompt with access to telnet with the hostname/IP and Remote Viewer port on the TopView server: telnet <host> <port>
- Use Powershell's "Test-NetConnection" command from the client machine:
- test-netconnection <host> -p <port>
Verify connection is within the licensed connection limit
The TopView engine is licensed for a certain number of connections. If existing Remote Viewer connections have taken up all licensed connections, then subsequent Remote Viewer clients will fail to connect to the TopView engine.
You can see how many connections are currently in use in the TopView Admin Tools application. Look for the "Remote Viewer Connections" link in the left sidebar.
Ensure you have the engine you want to inspect selected in the top drop-down bar of the application, Then, in the "Selected TopView Engine" tab you will see a list of connected Remote Viewer applications, along with identifying details.
Related Articles
Win10 1909 update disabled Remote Registry Service
We seen some upgrades of Windows 10 to feature update 1909 experiencing issues. The Remote Registry Service was disabled after update. Once the service was re-enabled and started, TopView could see monitored performance counters again - this is a ...
TopView loses connection to InTouch after computer restart until gateway restarted
Issue: After restarting InTouch, TopView can lose connection to its tags via OIGateway. Recommendation: After restarting InTouch, we recommend restarting the Gateway, as well, to ensure that TopView has a good OPC connection through the Gateway to ...
TopView - lost connection to Gmail account (Sign in with Google)
The following article is for TopView customers using a Gmail account to send/receive Email where authorization to the Gmail account was configured using "Sign in with Google" from the TopView Configurator > Email-SMS Notification > Outgoing Email. ...
ClearSCADA connection fails with: "Error: CheckConnectionToServer > error creating group : AddGroup failed with error"
If you receive an error connecting to ClearSCADA with the following error message: ClearSCADA can be set up to use OPC private security and require credentials for permissions to connect to the server and retrieve tag values. To connect, provide the ...
Keeping TopView healthy
Like all software, TopView is running in an environment that is under constant change. OS updates, protocol versions updates, email authentication deprecations, and other things can affect the health of your TopView system. Even systems off the ...