Problem with ❝Delivering Data from IoT Hub to Azure Blockchain Workbench❞ RRS feed

  • Question

  • We just followed the steps described in
    but couldn't get the device message to ABW.

    Would you please refer to this link for details?


    Thursday, November 14, 2019 7:51 AM

All replies

  • @mesgar.net

    We are checking on this and meanwhile could you please check the logs by following Azure Blockchain Workbench Preview troubleshooting guide and see it helps to identify the root cause? 

    Friday, November 15, 2019 7:13 AM
  • Thank you for your feedback response. 
    We executed the power-shell script and 
    how do we identify the root cause now?

    There are some execptions in [exceptions.csv].
    No error reported in [servicelogs_telemetry-collector.csv].
    And here is top errors reported in [summary.txt].

    [3] Top Errors, Last 18 hours

    Cannot insert duplicate key row in object 'dbo.Block' with unique index 'Block_BlockHash'. The duplicate key value is (0xa2d65b965b5864f62ec91fe270fe7d110ea09f14c08cf4085d0e88481520f8ed)...

    Monday, November 18, 2019 7:13 AM
  • Hi mesgar,

    Before we debug into Workbench, could you please use Azure portal to test following to ensure messages have been delivered to IoT Hub, then Service Bus and Logic App? Any steps failed in the middle may cause ABW doesn't receive message.

    • Testing delivery of messages from device to IoT Hub
    • Testing delivery of messages from IoT Hub to Service Bus
    • Testing receipt and usage of messages by the Logic App

    Microsoft Azure Blockchain Team

    Tuesday, November 19, 2019 1:50 AM
  • Hi,

    Thank you for your reply.

    I wrote a small program using [Microsoft.Azure.ServiceBus] and pulled data from service bus queue.

    Everything seems to be fine there.

    Here is the message pulled from "ingressqueue".

    Recv@:2019-11-19 13:47:44.883313 Seq:13510798882111527


        "Parameters": [

    • Edited by mesgar.net Tuesday, November 19, 2019 4:55 AM
    Tuesday, November 19, 2019 4:54 AM
  • Interesting behavior.
    We created a new contract and confirmed that telemetry data from device are ingesting into contract.
    In the meantime, we created another contract for another device, and right after data delivery for first device seemed to be stopped!
    So, there was nothing wrong with logic apps and the message itself.
    Is this an expected behavior?

    Tuesday, November 19, 2019 5:50 AM
  • Hi,

    Since i'm not able to upload link or image here, 

    I updated the ticket below with screenshots for better understanding.


    Friday, November 22, 2019 3:58 PM