Skip to content
Ask A Question
  • There are no suggestions because the search field is empty.

Problems making OPC DA connections using the TOP Server OPC DA Client Driver after applying Meltdown/Spectre Patches

We recently applied the KB405689x Windows patch to mitigate the Meltdown/Spectre vulnerabilities, and my TOP Server OPC DA Client driver is now unable to connect to my OPC Server - how can I fix this?

There is a known issue with the Microsoft KB405689x Meltdown/Spectre patches when a COM application (like an OPC DA Client or server) calls CoInitializeSecurity and sets the impersonation or authentication levels to 'none'.

This does not solely impact the TOP Server, but ANY application that uses COM Objects when calling CoInitializeSecurity.

Microsoft has released an additional patch (the KB number varies by Operating System and build) to fix this issue., and we recommend working with your IT Group to make sure that the latest Windows patches are applied and that this CoInitializeSecurity issue is patched. To find the patch from Microsoft what we have found it to be easiest is to find the original January 3, 2018 patch for your OS, and they will have a check the list of "Known issues in this update" like the example shown below for KB4056898  for Windows Server 2012R2 that shows this specific issue:

MicrosoftPatchToThePatch

Notice how they show in the workaround that the issue has been patched by KB4057401 .  Of course when you get to KB4057401, you'll need to check its known issues.  Unfortunately the patches to the KB405689x patches aren't following an easy syntax so use the strategy above to help your research.

Above all we strongly recommend working with your company's IT group to make sure the latest Windows patches are applied and that this CoInitializeSecurity issue is patched in accordance with your company standards, practices, and policies.

Alternately, if patching the Microsoft patch isn't feasible, please:

  1. Right click on the TOP Server Icon in the system tray and select Settings
  2. Navigate to the Runtime Options tab and make sure that the "Use DCOM configuration settings" checkbox is checked
  3. Restart the TOP Server Runtime