Rockwell Automation 1757-PROCESSLINX ProcessLinx OPC Server to Server Software User Manual - Manual (Page 59)

1 Publication 1757-UM002B-EN-P - January 2003
Chapter
6
Error Diagnosis and Debugging
This chapter explains how to diagnosis errors and debug ProcessLinx in the
event the Runtime operations are not functioning properly. ProcessLinx logs
errors along with informational messages to the message log in runtime mode
only. Use the log to diagnose potential error conditions.
Quick Setup Quick Setup describes how you can quickly setup ProcessLinx and diagnose
common setup problems. The following checklist should be consulted if
startup issues arise:
Table 6.A
Item Subject Description
1. Is TCP/IP enabled? Verify TCP/IP protocol is enabled on the node running ProcessLinx and all OPC Servers.
2. Are your OPC Servers setup
properly? Setup/Install both OPC Servers according to OEM specifications.
3. Have you tried to ping a
remote host?
• Attempt to ping the node running the desired OPC server you wish to connect with.
• If you cannot ping a remote host then a network setup/hardware issue exists.
4. Are your user accounts and
security properly setup?
• If the network is a Domain, then the user account under which ProcessLinx is running
needs to have the proper security setup in order to connect with the OPC Server(s) on the
local/remote machine.
• This user account needs to exist (be created under) that domain and thus have
permissions to log in to the domain if both nodes are running under that domain. Consult
the System Administrator of the domain for setting up user accounts.
5. Is your Network a
Workgroup?
• If the network is a Workgroup, the easiest way to connect the PCs it to place both nodes
in the same workgroup and then define the same username and password on both nodes
and then logon as the same user on each node.
• If ProcessLinx is running a node A and an OPC Server is running on node B and both are
part of the same workgroup then both node A and node B need to have a User account
(with the same password) setup with the proper security privilege (in DCOM) to access
and run the OPC Server on node B. ProcessLinx must be run under that user account.
• Getting DCOM to work over a Workgroup is a challenge without totally removing all
security. A user can be defined on both PCs yet still not work since each PC assigns an
SID to the created user account. They will still be different SIDs even though it is the
same user name. This is where having a Domain to do your authentication makes life
easier.
6. Is the user account added to
the list of users in DCOM?
• The user account running ProcessLinx must be added to the list of users in DCOM with
access permissions and launch permissions for that OPC Server.
• Consult the Using DCOM OPC Servers for setting up this OPC Server security privilege.
7. Have you configured each
OPC Server?
• Configure each OPC Server if configuration is required.
• If the OPC90 Server is used, you will need to configure the desired blocks first within the
OPC90 Server and then save the configuration. For ProcessLogix, this is not necessary.