Hello!
We have a user who is seeing a timeout issue after a round of OPC Data Client upgrades and Windows updates on some of his client machines.
He is receiving a periodic timeout error (RawEasyDAClient.HResult=0xC004C001) on some of his OPC DA clients built with 2020.3 when doing single reads and writes (ReadItem and WriteItem). These were previously built with 2016.3 and did not see this exception. He upgraded to versions built with 2020.3 at the time the Windows updates were run. Not all machines had Windows updates, but all were upgraded to 2020.3.
When he removes the lines of code he has which set the timeout, this error no longer occurs, but periodically, data updates take longer than 10 seconds to occur. This is what I expected to occur, as the lines he removed set the timeout to 10 seconds:
EasyDA.InstanceParameters.Timeouts.ReadItem = 10000
EasyDA.InstanceParameters.Timeouts.WriteItem = 10000
Because of this, we believe it may have to do with changed security parameters in the OS after Windows Updates leading to a slowdown, but I was curious if you had seen this or anything similar before. Previously, 10 seconds was long enough to prevent timeout errors. There were no changes on the network.
Of concern to me is that the exception provided in the client is not the same as the exeception shown in the minidump he captured. The minidump shows 0x80000004 instead. Attached are the OPC Data Client threads that were captured. The minidump captured at the time of this error occurring can be downloaded from here:
softwaretoolbox.sharefile.com/d-se2255d57025f464caf432f6b26c18ed7
I suspect that either this is an issue with a specific Windows build, or certain DCOM settings were changed when the Windows update occurred. I have asked the user to provide a list of the version and build of each client machine, along with whether or not that machine is seeing this periodic error, and I will pass this along to you as soon as I receive it.
Thank you, as always!
Zachary Parham
