"An error occurred during export XML for transaction XXX"
That means the XML file has not been exported to target server for some reason (e.g. not working target server).
When export will not succeed the XML file "goes" to the XML Export Queue in R3Admin.
The XML Export Queue is trying to resend file by itself from time to time.
Sometimes resend automatically performed by the XML Export Queue won't succeed. In that case the 1st level support should try to resend it manually.
- a/ - destination link is the path to exact directory on client's server where file should be exported. It depends on the contract and is configured in the Platform Config file.
b/ - destination link "http://localhost/castorVANDA/" means that XML file for contract should not be exported, so there is no need to resend it.
c/ - to resend XML file click on "Resend" link.
The resending not always works. Sometimes problems with target servers can occur for couple days, so it is good idea to try resend XML file later.
Sometimes in the XML Export Queue unsuccessful export from one book can be listed twice. This situation occur when book XML has not been exported and the same book was cancelled before the export succeeded. Than the cancel XML is generated and export of this file can not succeed because the book XML has not been exported. Than the cancel XML has "Waiting for export" status in the XML Export Queue.
If this case occur inform Data Base administrators or 2nd level support.
Watch out! :
In case of changing by a client a destination link (e.g. port number) some files can stuck in the XML Export Queue until the PROD update of destination link is made. Than resending this files won't succeed because of the non proper destination link. Do not try to change manually non proper link in the Data Base and resend it (this may cause double transactions in the client's system), just inform client about this issue when it occurs. They will take care of it.