"An event was unable to invoke any of the subscribers." error when trying to add group on remote OPC Simulation Server. | OPC Simulation ServerProsys Forum

Please consider registering
guest

Forum

OPC Simulation Server
sp_ArrowRight

"An event was unable to invoke any of the subscribers." error when trying to add group on remote OPC Simulation Server.

Topic RSS

"An event was unable to invoke any of the subscribers." error when trying to add group on remote OPC Simulation Server.

June 18, 2022
19:43, EEST

jl75

Member

Members

Forum Posts: 5

Member Since:
December 16, 2016

Offline

I’m a Sentrol 6.7.2 user. I had the problem mentioned in the topic when trying to connect an OPC Client on Windows 10 to a remote OPC Server running on Windows 10 which was created using Sentrol 6.7.2.

The same OPC Client could connect to MatrikonOPC Simulator Server installed on the same remote server, and I’m able to add groups and see item values. The DCOMCNFG settings are the same for both MatrikonOPC and my custom OPC Server. Today, I tried using the OPC Simulation Server (PsOPCServer175.msi), and the same error appears. My Windows 10 are both updated with the latest Windows updates.

I’ve some logging on the my Sentrol OPC Server. Please let me know how I can make this work. Thank you.

2022.06.18 09:35:54:175 [thread:5412] [OPCProvider] OPC Client with User=”DESKTOP-TBI4U61\user” has connected
2022.06.18 09:35:54:175 [thread:5244] [OPCProvider] OnLog: 2022/06/18 09:35:54.175 Client ‘Client 0’ connected.
2022.06.18 09:35:54:645 [thread:5244] [OPCProvider] OnLog: 2022/06/18 09:35:54.645 Client 0: IOPCServer.SetClientName(“dOPC DA Client”)
…………
2022.06.18 09:36:09:643 [thread:5244] [OPCProvider] OnLog: 2022/06/18 09:36:09.643 dOPC DA Client: GetStatus
2022.06.18 09:36:10:643 [thread:5244] [OPCProvider] OnLog: 2022/06/18 09:36:10.643 dOPC DA Client: GetStatus
2022.06.18 09:36:11:300 [thread:5244] [OPCProvider] OnLog: 2022/06/18 09:36:11.300 dOPC DA Client: IOPCServer.AddGroup(Name=test, RequestedUpdateRate=1000): Result=$0
2022.06.18 09:36:11:330 [thread:5244] [OPCProvider] OnLog: 2022/06/18 09:36:11.330 dOPC DA Client: test: Callback connection failed: Interface not supported
2022.06.18 09:36:11:330 [thread:5244] [OPCProvider] OnLog: 2022/06/18 09:36:11.330 dOPC DA Client: test: IAdviseSink.DAdvise: Result=$80040201
2022.06.18 09:36:11:346 [thread:5244] [OPCProvider] OnLog: 2022/06/18 09:36:11.346 dOPC DA Client: IOPCServer.RemoveGroup(test, Force=False): Result=$0
2022.06.18 09:36:11:831 [thread:5244] [OPCProvider] OnLog: 2022/06/18 09:36:11.831 dOPC DA Client: GetStatus

June 20, 2022
10:46, EEST

Jouni Aro

Moderator

Moderators

Forum Posts: 1010

Member Since:
December 21, 2011

Offline

“My Windows 10 are both updated with the latest Windows updates.”

The latest updates close DCOM abit more and you will have to modify your client application.

To enable connections to updated servers, OPC client applications built with Prosys Sentrol must be modified to initialize COM Security in the Project Source as follows:

program Xxx;

uses
PsComUtils,
…

begin
PsInitComSecurity(alPacketIntegrity, ilIdentify);
…

See the following article for more details.

All RSS

Forum Timezone: Europe/Helsinki

Most Users Ever Online: 518

Currently Online:
19 Guest(s)

Currently Browsing this Page:
1 Guest(s)