Unable to Connect TOP Server Version 5 with Wonderware

The most common reason is that the Native Client Interface for Wonderware was not installed when you installed TOP Server and you are using a SuiteLink connection.  Click here to see how to do this in our Quick Start Guide.

The second most common problem is with a SuiteLink Connection due to the change in Application name used with Wonderware.  Mostly this is due to people who have been using Version 4 and did not see the information on the new Application name.  The Application name to use with TOP Server Version 5 is server_runtime.  Version 4 used servermain.  Click here to see more information on this.

If this is a remote connection between Wonderware and TOP Server, the Wonderware Common Components may not be installed on the local PC.  These components enable communication via FastDDE/Suitelink and can be found on your Wonderware installation disk and must be installed prior to the TOP Server (with the Wonderware Native Client Interface) for the FastDDE/Suitelink Tab to appear within the TOP Server Project Properties.  If TOP Server was installed first, running the installer as repair/modify will correct the issue.

If you are making an OPC Connection with the TOP Server using the System Platform OPC DI Object, there are two possible problems.  If you did a side by side installation of Version 4 and Version 5 or installed Version 5 on a PC that did not have Version 4 installed then to connect to Version 5 you will need to use a different ProgID

• SWToolbox.TOPServer.V5

If the ProgID is correct, then there might be DCOM settings changes you need to make because TOP Server V5 installs and runs as a Servers and Version 4 did not install as a Service. 

Click here for our DCOM tutorial.

If you ran Version 4 as a Service and you are able to connect to it, DCOM might not be the issue.