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

Publication 1757-UM002B-EN-P - January 2003
7-2 Using DCOM OPC Servers
under the Identity tab. Launching User is the default option, so this task must
be done manually.
You must enable the security permissions correctly on the remote machine for
the ProcessLinx node to access and launch the OPC Server remotely.
Instructions for this procedure are specified in the ProcessLogix Server and Client
Installation Guide.
1. Select the Security tab and verify that Use Custom Access Permissions is
checked, and that the account being used to run the ProcessLinx node is
selected as a User.
2. Verify that the same account is enabled under the Use Custom Launch
Permissions checkbox.
3. If there is a problem adding a specific user in an NT Domain, the easiest
way to enable these permissions (although not recommended) is to add
the User Everybody for the two Groups mentioned above.
However, this will allow any client/machine on the network to connect
and launch the OPC Server remotely, leaving security wide open. If
problems persist, consult your Network Administrator. The error
E_ACCESSDENIED is displayed when running ProcessLinx if the
required permissions are not enabled.
OPC Servers on Windows98 / Windows 95
In Windows 95, DCOM is disabled by default. Enable DCOM using 3 keys in
the registry. The following is a description of these keys:
•
EnableRemoteConnect
key on the OPC Server machine. Set to ‘Y’
for yes to allow ProcessLinx to connect to it remotely. This key is found
from using the registry path:
HKEY_LOCAL_MACHINE\Software\Microsoft\Ole\EnableRemoteConnect=’Y’
IMPORTANT
This is not the case for the ProcessLogix OPC Server
where the process is configured to run under the <mngr>
account.
WARNING
!
Rockwell Automation holds no responsibility for
damages to property and personnel or loss of time
that may occur when making changes to the Registry.