FieldServer FS-8707-06 - Manual (Page 13)

FS-8707-06 FST OPC Server for FieldServer Page 13 of 15
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: [email protected]
Appendix A. Troubleshooting Tips
Appendix A.1. Locating the “FieldServer.7.16.x” file
When Configuring an OPC Client link to the FieldServer OPC, the OPC Client will be browsing for available Servers
using the OPC Foundation supplied utility OPCENUM.EXE (Installed with the FST OPC Server for FieldServers)
Appendix A.1.1. When the Client & Server are on the same machine

Ensure that OPCENUM.EXE is running in the background, it is installed as a service & should start when
the Client needs it

If running NT4 or Windows 2000 with Explorer 6.x and either of the following messages return on
installation “IcatInformation interface not supported”; “Incompatible Version of RPC Stub 0x80070725”
then uninstall IE6. This is a known issue that needs to be resolved by Microsoft & the OPC foundation.

Manually type the ProgID and if necessary the CLSID
ProgID “FieldServer”
CLSID {8D3DD5B6-8854-42a0-A376-94DE9676ADD5}
Appendix A.1.2. When the Client & Server are different machines
The same issues apply as above with the following additions

Ensure that the Server machine is visible in the network neighbourhood

OPCENUM.EXE needs to run on both machines, on the Server machine it needs to be running at startup
which sometimes does not happen – check the services & set the startup mode of the OPCENUM service.
Appendix A.2. The OPC Client returns OPC data quality bad
Open the Configurator, select the Data Array containing the relevant address, then press the “Stats”
button

If the Timeout & retry counters are incrementing then the problem is with the communication to the
FieldServer.

“Ping” the FieldServer and ensure that it can be located.

Ensure that the Ethernet port on the FieldServer is configured for SMT protocol

Check the Text field to the right of the “Last Error Field”

“Bad DA name” indicates that the Data Array does not exist in the FieldServer - check the FieldServer
configuration

“Bad DA offset” indicates an attempt to poll more data than exists in the Data Array – reduce the length
Appendix A.3. Communication
OPC uses the Windows service DCOM to facilitate communications. DCOM requires port 135 is open on the PC
and network. Please ensure that network routers are not blocking this port.