Online Forums
Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.
Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.
Do not use the Contact page for technical issues.
- Forum
- Discussions
- QuickOPC-Classic in .NET
- Reading, Writing, Subscriptions, Property Access
- An OPC operation failure with error code -1073430509 (0xC004C013) occurred
An OPC operation failure with error code -1073430509 (0xC004C013) occurred
It's good that it works now, but it is not normal. It probably indicates a problem in the server, OR a problem in the reverse direction of DCOM communication (callbacks from server to the client - those are needed for async methods, and subscriptions).
Please Log in or Create an account to join the conversation.
You are right, now its working.
The AllowAsynchronousMethod says in definition "When true, asynchronous OPC reads and writes will be allowed".
This is my misunderstanding about the method.
Thanks very much
Jukka
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
I cannot modify my project because it need asynchronous write and read.
Only DAClient working with ABB.
Maybe we wait the response from ABB if there is something to do with license.
Please Log in or Create an account to join the conversation.
Have you tried some other OPC client, and what were the results?
Can you modify your project and try to enforce synchronous reads (set client.InstanceParameters.Mode.AllowAsynchronousMethod = false;).
Thank you
Please Log in or Create an account to join the conversation.
2. Remote.
3. The reading is possible if the user is same in client and server-side.
But in this case the server is not starting a new service. It using the existing server ABB.AfwOpcDaSurrogate.
We have created new user in client side and server side. A new server process is starting ABB.AfwOpcDaSurrogate.1 but the reading giving the error.
4. It happend always.
5. Half an hour.
6. Version QuickOPC 5.4.
I've also done a survey on ABB.
T:Jukka
Please Log in or Create an account to join the conversation.
can you please answer following questions?
1. Is the server on the same machine as client, or is it remote?
2. (if local) Do you know whether it is in in-process server (essentially a DLL that runs inside the client's process), or out of process (runs in a separate process)?
3. Are you ever able to read, or does it happen just sometimes?
4. If it happens just sometimes, is there an indication that it could be caused by problems on the server side, or in a communication (network)?
5. If you are doing further reads, do they - after some time - start working correctly , or is it so that after receiving this error, they never resume ? (if so, how long have you waited)?
6. If you are receiving this error for longer time, and during that time try to connect to the same server using a separate instance of the client, do you also get the same error, or does the 2nd instance of the client work well?
7. Which version of QuickOPC are you using?
Thank you
Please Log in or Create an account to join the conversation.
This kind of problem come with ABB.AfwOpcDaSurrogate.1 - server.
Any ideas how to solve it ?
ErrorTxt:
2017-01-12 10:57:29 OpcLabs.EasyOpc.OperationModel.OpcException: An OPC operation failure with error code -1073430509 (0xC004C013) occurred, originating from 'OpcLabs.EasyOpcRaw.DataAccess.RawEasyDAClient'. The inner exception contains details about the problem. ---> System.Runtime.InteropServices.COMException: Read not completed. This error indicates that it could not be verified that the requested read operation was completed during the timeout period. It is possible that the read 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).
--- End of inner exception stack trace ---
at OpcLabs.EasyOpc.EasyUtilities.CheckSuccess(OperationResult operationResult)
at OpcLabs.EasyOpc.DataAccess.IEasyDAClientExtension.ReadItem(IEasyDAClient client, ServerDescriptor serverDescriptor, DAItemDescriptor itemDescriptor, DAReadParameters readParameters)
at OpcLabs.EasyOpc.DataAccess.IEasyDAClientExtension.ReadItem(IEasyDAClient client, ServerDescriptor serverDescriptor, DAItemDescriptor itemDescriptor)
at OpcLabs.EasyOpc.DataAccess.IEasyDAClientExtension.ReadItem(IEasyDAClient client, String machineName, String serverClass, String itemId, VarType dataType)
at OpcLabs.EasyOpc.DataAccess.IEasyDAClientExtension.ReadItem(IEasyDAClient client, String machineName, String serverClass, String itemId)
at EasyOpcNetDemo.MainForm.AloitaMallinnus_Click(Object sender, EventArgs e) in c:\Omat\Tyotw\Sin3PyrometriMallinnus\OPCToMysql_3\MainForm.cs:line 181
T: Jukka Kuikka
Please Log in or Create an account to join the conversation.
- Forum
- Discussions
- QuickOPC-Classic in .NET
- Reading, Writing, Subscriptions, Property Access
- An OPC operation failure with error code -1073430509 (0xC004C013) occurred