ABW version 1.6 - messages sent to ingressqueue rejected

Copper Contributor



We've deployed, and adapted our solidity contracts for the changes required in v1.6, and our contracts work fine when tested under the ABW Web UI.


However, when we send Json serialized CreateContract messages (in the same format as 1.5) to the Service Bus `ingressqueue`, the contract isn't created, and a correlated error response is returned on the `egresstopic`


"ErrorCode":4000,"ErrorMessage":"CreateContractRequest deserialization failed"


Since the error does reference the RequestId specified on the CreateContract, we believe it may that the CreateContract schema has changed somehow in 1.6, as it seems ABW is still able to parse the Json.

The message format we've used is compliant with





"requestId": "4cafbbe3-996d-4619-8276-8fba39ffa673",
"userChainIdentifier": "0x567c401f34dcfdb877548bd38528c199dd35507a",
"applicationName": "MyAppName",
"workflowName": "MyWorkflowName",
"parameters": [
"name": "param1",
"value": "value1"
"name": "param2",
"value": "value2"
"connectionId": 1,
"messageSchemaVersion": "1.0.0",
"messageName": "CreateContractRequest"


With the error response received on the egress Topic:



      "ErrorMessage":"CreateContractRequest deserialization failed"

(Also, noted that the response capitalization is PascalCase, rather than the camelCase suggested on the website)


Any ideas around this would be seriously appreciated






2 Replies
Ok, found the breaking change. There's a new mandatory, undocumented property called `Version` which must match the new column added on table `Application`.
Pity that the MessageSchemaVersion wasn't bumped up.
The Docs and Messaging samples need to be updated.

@Stuart Corrans Thanks Stuart. We've made some updates to our documentation to make things more clear.