15:00

The Calastone service remains stable.

Analysis has confirmed that all deals with the rejection message "ExecuteQuery.execute : SQLException 6134" HAVE successfully placed.  There are the following impacts:

We continue to look out for duplicated trades but if you know are aware that trades have been sent by other methods, please contact us by phone or webchat.

No further updates are planned on this issue.

 

14:00

The Calastone connection is open again and we are no longer generating spurious rejection messages, so the service is operating as expected.

We continue to do the analysis of trading and so far, all trades receiving this rejection reason ("ExecuteQuery.execute : SQLException 6134") HAVE successfully placed.  We continue to do the analysis, including looking out for duplicate trades that may have been received.

Please be aware that where this rejection reason was received, we do not believe that you will receive a ‘pricing message’, even though the trades have placed.  Please use the distributor portal to confirm your deals have been placed and notify us by phone or webchat (not by e-mail please) if anything has been duplicated or is ‘missing’ later this afternoon or Monday morning at the latest.

You should assume that the deals with this rejection have been placed and if you are aware that this will lead to a duplicate, please contact us by phone or webchat as soon as possible.

A further update will be issued at 15:00

 

 

13:00

We are aware of a small volume of deals that have rejected on Calastone with the rejection message "ExecuteQuery.execute : SQLException 6134".

We are currently investigating this but believe that in most cases these deals have been processed (hence the message is incorrect)  We are also aware that a number of trades may also have been instructed twice on Calastone or by fax as a result.  

A further update will be issued at 14:00