Log In
Home
07/20/2016
Offline
Since Microsoft has updated my PC with the actual Windows 10 update (KB4056892) the OPC DA server cannot be accessed any more. I have the same problem on multiple computers. After I’ve uninstalled the update the server is running again, but I don’t think this is a permanent solution.
Anybody with the same experience?
05/30/2017
Offline
This link http://news.softpedia.com/news…..9217.shtml has more information.
Additionally, Microsoft says that due to this cumulative update, when calling CoInitializeSecurity, the call will fail if passing RPC_C_IMP_LEVEL_NONE under certain conditions, while due to some compatibility issues with certain antivirus software, only systems with AV ISV update to ALLOW REGKEY are being offered the update.
This change will break many OPC COM applications. I am not sure what “AV ISV update to ALLOW REGKEY” means but I suspect all OPC COM systems will have to block this update.
05/30/2017
Offline
The OPC Foundation has started a discussion with Microsoft on the issue.
I will post more as information becomes available.
05/30/2017
Offline
Can anyone who experiences this problem please post the exact version of Windows 10 that you are using?
You can find it under:
Windows Settings | Update & Security | OS build info
10/24/2016
Offline
Windows 10 Pro Version 1709
Build 16299.192
10/24/2016
Offline
If you need more information, look at https://www.google.de/search?q…..056892+opc
Most OPC vendors have similar issues.
05/30/2017
Offline
Response from Microsoft:
As of this morning, updates for Windows 10 1709 (RS3), 1703 (RS2), 1609 (RS1) has been posted to Windows Update.
Please report back to us if these updates does not resolve the regression they see on those releases.As communicated earlier, update for Windows 10 1507 LTSB (TH1) is planned to be released later.
We’re expecting that systems running TH1 and older are production systems that does not normally receive automatic updates, but rather updates are deployed after validation.
In case the security update was applied, it can and should be uninstalled until the fix is available.
If anyone is able to provide us with concrete numbers of system impacted for TH1 and earlier, it will be a data point we can leverage to justify accelerating release of the fix for older system.
http://www.catalog.update.micr…..ws+10+1709
See: 2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4073290)
07/20/2016
Offline
After installing the most recent Windows updates (KB4058258) the OPC server is working again.
03/19/2018
Offline
Randy Armstrong said
This link has more information.Additionally, Microsoft says that due to this cumulative update, when calling CoInitializeSecurity, the call will fail if passing RPC_C_IMP_LEVEL_NONE under certain conditions, while due to some compatibility issues with certain antivirus software, only systems with AV ISV update to ALLOW REGKEY are being offered the update.
This change will break many OPC COM applications. I am not sure what “AV ISV update to ALLOW REGKEY” means but I suspect all OPC COM systems will have to block this update.
If all the OPC COM systems will have to block this update. the Windows update process can not be completed , i failed 2 time and my computer has broken down. my computer can not be allowed to access . I’ll ask some tools for help.
05/30/2017
Offline
MS should have fixed the issue so there is no longer a need to block the update.
09/13/2018
Offline
Hi,
I have been having similiar problems but have finally got DCom working in Window 10 Pro Version 1803 (28/08/2018).
I seems that some OPC Server Libraries (Softing) do not understand IP addresses. This needs server names / ip addresses addded to the hosts file. Additional DCom settings can be found by googling the issue of DCom settings.
Good Luck
1 Guest(s)
Usage Policy