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

Publication 1757-UM002B-EN-P - January 2003
6-2 Error Diagnosis and Debugging
8. Is ProcessLogix the main
OPC Server?
• You may need to create a user account <ps_user> and/or <mngr> with administrator
privledges on the node running ProcessLinx.
• If you are running an NT Workgroup, you may need to logon to the ProcessLinx node as
<ps_user> or <mngr> in order to connect to the remote ProcessLogix OPC Server node.
This is not the case when running under a domain. Using DCOM, the ProcessLogix OPC
Server should already be setup to run under the <mngr> account, which is the reason
why any remote Workgroup node wishing to connect with it needs to have the <mngr>
admin account defined as a user.
This step provides for the authentication of the ProcessLogix node to make callbacks
(advise) into the ProcessLinx node. This is required if ProcessLinx is to receive callbacks
via a ConnectionPoint Interface which is normal OPC method for receiving data from OPC
Servers.
9. Is ProcessLinx configured?
• Configure your ProcessLinx configuration.
• Add a Pipe, one or more groups, add the desired tag maps for each group.
10. Is ProcessLinx in runtime
Mode?
• Place ProcessLinx in runtime mode.
11. Has the Server started?
• If ProcessLogix OPC Server is used and all values are displayed as Bad Quality, then
verify the ProcessLogix Server is 'Started' and running on the ProcessLogix node.
• You may need to end the HWHsc.OPCServer (hscopcserv.exe) process on the host node
first before going to run mode, assuming it was left in a hung state and no other clients
are connected to it.
12. Current connection does not
support Advise!
• If a message appears in message log pane stating that 'Current connection does not
support Advise! Defaulting to polling of OPC Server', then the problem may be due to a
security issue as stated in #4, 5, 6 or 10 above.
13. Does not support OPC
Version 2.0 Interfaces.
• Upon startup, if ProcessLinx displays the message 'Does not support OPC Version 2.0
Interfaces' and the OPC Server is known to support v2.0 then verify #4, 5, 6 and/or 10
above and/or verify that the server is setup correctly on the server machine
• Verify that any required client software is installed on the ProcessLinx node.
• In most cases this is either the result of not having the proper security setup in DCOM
and/or having older or missing software components in the system of the server.
14. In Runtime, Server Status
dialog states Total Reads=0.
• Using the Server Status dialog, in runtime if the Total Reads=0, then it is possible that
the Advise subscriptions are not working correctly.
• If problem cannot be corrected with one of above steps, then the Pipe and OPC Server
may need to be setup for 'Polling'.
• Keep in mind that advise connections will require security on the ProcessLinx node to be
setup such that the user account which runs the OPC Server on the remote node will
have 'permission' to send back data to the ProcessLinx node and thus to ProcessLinx.
• This is not the same as the security setup to the Server in step #6. Since ProcessLinx is
not an OPC Server, it cannot be setup with DCOM to enable such permission.
• The network workgroup/domain will enable/define this privilege and thus that is why it
is essential to correctly setup steps #4 or 5.
15. ProcessLinx may fail to
connect to the OPC Server
because....
• ProcessLogix Server is stopped on the remote node.
• Local machine had Norton AntiVirus on it, but it was disabled. The network used the
POPProxy.dll provided by the AntiVirus software vendor to send/receive data and since it
was disabled, then you could not ping the remote node.
• ProcessLogix machine required a reboot.
• Network cables were bad.
• If 'Access is denied' messages appear in message log pane, then the most likely fix is
solved in items 4, 5 and 6.
Table 6.A
Item Subject Description