Which version of QuickOPC are you using please?
Which version of the Top Server are you using please?
Is the server on the same computer as the client, or is it remote?
Do these errors happen always (or under certain conditions), or randomly?
ad 1) The reason for the error is explained in the message text. It means that we have issued an asynchronous read call, where the item to be read are identified with their handles. The responded with a callback containing the results, but it did not send us the results for all the items originally requested - which is against the OPC specs. Normally I would tell you to go to resolve this with the server vendor. However, Top Server (from Software Toolbox) is one of the most common servers on the market, and usually very reliable. For this reason, I'd rather suggest that you put a special tool (OPC Analyzer) between the client and the server, and we would analyze the OPC communication and determine where the fault is.
Since this error is only possible with asynchronous OPC calls, you should be able to work around it by switching to sync-only calls, like this:
EasyDAClient opcComponent = new EasyDAClient();
opcComponent.Isolated = true;
opcComponent.InstanceParameters.Mode.AllowAsynchronousMethod = false;
ad 2. I cannot determine the reason - probably the OPC Analyzer would be the way to go as well.
Best regards