Hi,

I tried with the following code and got the same results as before (Access id denied)
EasyDAClient.SharedParameters.Topic.SlowdownWeight = 0.0f;
EasyDAClient.SharedParameters.Topic.SpeedupWeight = 0.0f;
this.daClient.InstanceParameters.UpdateRates.ReadAutomatic = Timeout.Infinite;
this.daClient.InstanceParameters.UpdateRates.WriteAutomatic = Timeout.Infinite;

My project is using OpcLabs.BaseLib version 5.35.1115.1
I mentioned in a previous post that I did try running the demo application with the newest version of OpcLabs and the results were the same.

Also, I tried the new code snippet with Async enabled and disabled. The results were the same both times.

Thanks,
Mike

Hi,
Below is some more details of e.Exception properties:
Message "Access is denied. " string
Source "OpcLabs.EasyOpcRaw.DataAccess.RawEasyDAClient" string
HResult -2147024891 int
Thanks,
Mike

Oh sorry, I misunderstood your question.

I've went and tested my before/after applications again and I do see a difference now.

Before, when I would perform a write operation, where the original value is different than the value being written, I would get an ~30s delay and the following error:
"Write not completed. This error indicates that it could not be verified that the requested write operation was completed during the timeout period. It is possible that the write operation will actually succeed or fail, but later. Increase the timeout period if you want to obtain positive or negative indication of the operation outcome. Other reason for this error may be that under heavy loads, topic request or response queue is overflowing. Check the event log for queue overflow errors (if event logging is supported by the product and enabled)."

After adding the additional statement, running the write operation yields an immediate "Access is denied" error. There is no 30s delay as before.

Hi,
No, I'm saying that the errors are still there. Adding the additional statement did not rectify the issue - I'm still getting the "Access is denied" error.
As I mentioned a couple of times, I'm able to read successfully using Matrikon, Kepware and h-opc clients.
Thanks,
Mike

Hi,

I tried running my application after adding the following LOC:
daClient.InstanceParameters.Mode.AllowAsynchronousMethod = False

The results remained the same. I still have an Access is Denied error. Like I mentioned earlier, I was able to get the read operation to work successfully on several other OPC clients, even using async reads.

Any other ideas?

Thanks,
Mike