If you are connecting locally or remotely it could be as simple
as not have DCOM security set properly. You will also get connection failures
of you are using the wrong "program ID". Lastly, when connecting remotely,
you can get this error if you incorrectly identify the remote node
where the server is running.
Possible solutions include:
- For local and remote connections, make sure you use the correct program
ID. This will be "Kepware.KEPServerEX.V4" if you are using
the standard Kepware Server.
- For remote connections the node name will always be the name of the
PC or its IP address. You will never use the double back slashes "\\" before
it.
- Ensure that you have DCOM security properly configured. Use the Kepware Technologies DCOM
Manual (PDF) for directions on properly configuring DCOM.
|