Thank you. When the Exception.Source is as you stated (as opposed to a ProgID of some OPC Server), it means that the error comes from some function called locally on the client side. Mostly, these are things that have to do with COM/DCOM, and VARIANT handling. Unfortunately there are many of them called during the process, and there is no easy way to tell which one has caused it. In general, it is some system error returned to us that prevents us from continuing the operation successfully - so in this sense, we are just "delivering" the message to your program.

The error is 0x8007000E, E_OUTOFMEMORY.

As the error text implies, it can be caused by low memory conditions. I think I have seen this error also when *other* system resources were missing, such as disk space, system handles, USER or GDI objects, or certainly when too many threads are created in the process.

Can you please check all these kinds of resources during the lifetime of the process (whether they do not "leak"), and at the moment the error appears? You can use Task Manager, or even better, PerfMon.

I suppose that you get "Not enough storage is available" as an error message of the exception object contained in the Exception property of one or more results returned by the WriteMultipleItemValues method.

If so, can you please examine what is in the Source property of that Exception? That should help us determining where is the origin of the error.

Regards

Both possibilities you have mentioned are possible. The error can be reported by the server itself, and QuickOPC may just be transferring it to your program. Or, less likely, it may have its origin in QuickOPC (= client side) itself.

Please tell me which programming language or tool you are using, so that I can give you proper instructions for further troubleshooting.

Regards