AfwOpcDaSurrogate.1 connect error
In Version 6.0 connecting to OPC Client ABB.AfwOpcDaSurrogate.1 throws
![]()
![]()
"Colud not Connect to:ABBAfwOpcDaSurrrogate.1"
and
![]()
"Error in Connect(): 0x80004002 - No such interface Supported"
This is only on one engineering client in the system.
All others Ok.
Any suggestions anybody??
Many thanks in advance,
Brian Williamson
and
"Error in Connect(): 0x80004002 - No such interface Supported"
This is only on one engineering client in the system.
All others Ok.
Any suggestions anybody??
Many thanks in advance,
Brian Williamson
Asked 3 months ago
Answers
0
The error is, a Windows error and if you google it, it looks like it has something to do with Windows updates being missing or some system files being corrupted.
1
Are you using an OPC DA v2.05A compliant client? OPC UA will become available in the upcoming 800xA v6.1.1 release later this year.
Please test this:
1. Login to a node of the system with a user accoint properly added to System 800xA (=visible in the User Structure)
2. Start>Run... advdsopcclient.exe
3. Browse > Local servers > AfwDsOpcSurrogate.1
4. Connect (add group, add item, advise, etc.)
What happens?
For others to access 800xA via the surrogate, e.g. via remote DCOM launch, you must create a known "3rd party external OPC client" user, add to 800xA and hand out appropriate object permission, maybe only Read (which is normally obtained by being member of the Everyone group in the User Structure) and then setup DCOM permission as I have posted many times here on the forum. For asynchronous DCOM you may need to create four (4) accounts and setup bidirectional DCOM permission in server & client computers.
Please test this:
1. Login to a node of the system with a user accoint properly added to System 800xA (=visible in the User Structure)
2. Start>Run... advdsopcclient.exe
3. Browse > Local servers > AfwDsOpcSurrogate.1
4. Connect (add group, add item, advise, etc.)
What happens?
For others to access 800xA via the surrogate, e.g. via remote DCOM launch, you must create a known "3rd party external OPC client" user, add to 800xA and hand out appropriate object permission, maybe only Read (which is normally obtained by being member of the Everyone group in the User Structure) and then setup DCOM permission as I have posted many times here on the forum. For asynchronous DCOM you may need to create four (4) accounts and setup bidirectional DCOM permission in server & client computers.
Add new comment