From: Zbynek Zahradnik
Sent: Monday, October 18, 2010 6:07 PM
To: W.
Subject: RE: OPCData.NET 5.x errors
W.,
These errors come from QuickOPC. They should be translated by the component to a meaningful message, so I will look into why the customer has not seen the message – but that’s for a bit later.
To the specific errors (the last 4 hex digits in the code are the MessageID):
1)
MessageId=0x9001
Severity=Error
Facility=Interface
SymbolicName=OCK_E_SERVER_FAILED
Language=English
Server failed. This error originates in the OPC server. A vendor specific fatal error has occurred within the server. The server
is no longer functioning. The recovery procedure from this situation is vendor specific. The application will try to reconnect
to the server after a configurable period.
.
There is just one way this can happen: The OPC Server has returned OPC_STATUS_FAILED in call to GetServerStatus. So one has to look into the OPC server as to why the server has returned it.
2)
MessageId=0xC013
Severity=Error
Facility=Interface
SymbolicName=EDA_E_READ_NOT_COMPLETED
Language=English
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.
.
It is one of the reasons above, or the server might be internally blocked in some method call or async operation.
3)
MessageId=0x900f
Severity=Error
Facility=Interface
SymbolicName=OCK_E_TRANSACTION_TERMINATED
Language=English
Transaction was terminated. The outcome of pending transaction will not be available as the item or the group are being removed.
First of all , it would also be normal to receive this if it’s in relation to server problems, such as the error under 1). This may also mean that the component is trying to move the item into a group with a different update rate, making it inaccessible temporarily. If the app is reading the item periodically, it can ignore this specific error and simply retry next time. If this is not the case, I may also offer some hints as to how to reorganize the code to possibly prevent this from happening. Can we get an idea of what the customer is trying to do?
Zbynek Zahradnik
From: W.
Sent: Monday, October 18, 2010 4:34 PM
To: Zbynek Zahradnik
Subject: OPCData.NET 5.x errors
A customer of ours is getting some errors messages. I can not find out what they mean. Do you have any documentation about these errors or have you seen them before?
W.
[ZbynekZ: a customer is seeing following errors:]
System.Runtime.InteropServices.COMException (0xC004C013): Exception from HRESULT: 0xC004C013
System.Runtime.InteropServices.COMException (0xC004900F): Exception from HRESULT: 0xC004900F
System.Runtime.InteropServices.COMException (0xC0049001): Exception from HRESULT: 0xC0049001
in DAVtqResult.Exception.Message is “System.Runtime.InteropServices.COMException (0xC004900F): Exception from HRESULT: 0xC004900F”. That is the entire exception message.
after a ReadMultipleItems
