Property Transfer - Write Failed for 1 properties
We use the Property Transfer Aspect for several signals and it works well.
One thing though, we always have this alarm coming and going. It comes and goes within the same second.
- Property Transfer - Write Failed for 1 properties.
Trying to find which signal that causes the alarm only leads me back to the service in Service Structure.
I have for example used the Find Tool to search for GUID and so on.
Is there a log file or another way to find out what's causing this problem?
The Tags that timed out should be in the expanded information.
Property Transfer seems to do this sometimes and its not always obvious why. I think the most common cause is downloading to the controller causes comms timeouts. If it only happens occasionally it might not be serious.
If your version/revision of 800xA Base is not among the most recent ones, the message can be a false positive from a standby Property Transfer service provider. If you have redundant Property Transfer (more than one service provider in the service group, enabled in parallel), make sure the error message is emitted by the one in Service state. If you see error messages from a Standby provider, toggle the master to force a failover (force the Standby into Service state). Upgrading to the most recent revision / rollup should prevent this from happening.
Have a look in the [Workplace Structure]Web System Workplace:Operator Message List.
The write failures should show up there, associated to the affected object.
'E_AFW_OPCDA_WRITE_TRANSACTION_TIMEOUT(0x8abb1501) The Data Access Write operation did not complete within the required time. '.
This indicate that the destination server did not reply with a mandatory OnWriteComplete callback within 30 seconds and the write operation timed out.
May I ask what your destination server is?
I have attached a document that details how to log OPC DA in 800xA. If you like, please have the Communicator Common log running at level 3 in the active Property Transfer service provider during a write failure. Then attach the log file, or email it to email@example.com and I will comment on it.