Smart Contract can't be deployed - eachOfLimit.js : 61 TypeError: finished is not a function RRS feed

  • Question

  • Hi,

    I try to deploy the simple tutorial smart contract to a private PoA Ehtereum blockchain on azure. After I updated the truffle-config.js to 0 gas und 0x0 gasPrice it seems to be better but I still see this error:

    Starting migrations...
    > Network name:    'poa'
    > Network id:      ...
    > Block gas limit: 0x2faf080


       Deploying 'Migrations'
       > transaction hash:    ...
       > Blocks: 0            Seconds: 0
       > contract address:    ...
       > block number:        8181
       > block timestamp:     1569996776
       > account:             ...
       > balance:             0
       > gas used:            261393
       > gas price:           0 gwei
       > value sent:          0 ETH
       > total cost:          0 ETH

       ⠦ Saving migration to chain.
    TypeError: finished is not a function
        at C:\ETH\node_modules\web3-provider-engine\index.js:157:9
        at C:\ETH\node_modules\web3-provider-engine\node_modules\async\internal\once.js:12:16
        at replenish (C:\ETH\node_modules\web3-provider-engine\node_modules\async\internal\eachOfLimit.js:61:25)
        at C:\ETH\node_modules\web3-provider-engine\node_modules\async\internal\eachOfLimit.js:71:9
        at eachLimit (C:\ETH\node_modules\web3-provider-engine\node_modules\async\eachLimit.js:43:36)
        at C:\ETH\node_modules\web3-provider-engine\node_modules\async\internal\doLimit.js:9:16
        at end (C:\ETH\node_modules\web3-provider-engine\index.js:134:5)
        at C:\ETH\node_modules\web3-provider-engine\subproviders\provider.js:18:32
        at XMLHttpRequest.request.onreadystatechange (C:\ETH\node_modules\web3-providers-http\src\index.js:96:13)
        at XMLHttpRequestEventTarget.dispatchEvent (C:\ETH\node_modules\xhr2-cookies\xml-http-request-event-target.ts:44:13)
        at XMLHttpRequest._setReadyState (C:\ETH\node_modules\xhr2-cookies\xml-http-request.ts:219:8)
        at XMLHttpRequest._onHttpResponseEnd (C:\ETH\node_modules\xhr2-cookies\xml-http-request.ts:345:8)
        at IncomingMessage.<anonymous> (C:\ETH\node_modules\xhr2-cookies\xml-http-request.ts:311:39)
        at IncomingMessage.emit (events.js:203:15)
        at endReadableNT (_stream_readable.js:1129:12)
        at process._tickCallback (internal/process/next_tick.js:63:19)

    Has someone an idea? Is this maybe a firewall issue?



    • Edited by iMoe Wednesday, October 2, 2019 6:27 AM the codeblock didn't look well
    Wednesday, October 2, 2019 6:25 AM

All replies

  • Thanks for your feedback iMoe. We are leveraging this issue with Product Team. Can you please confirm the link to the tutorial you are following?


    Monday, October 7, 2019 2:24 PM
  • I followed this link: https://docs.microsoft.com/de-de/azure/blockchain/templates/ethereum-poa-deployment

    If I do it locally evertyhing works. With Azure Cloud it doesn't work. Do I need some specific firewall settings?

    Wednesday, October 9, 2019 12:25 PM
  • Hello iMoe,

    Thank you for your patience. I am still researching internally with our Product Team.

    Appreciate your time in advance.

    Monday, October 14, 2019 3:22 PM
  • Hallo iMoe,

    Apologies for the delayed response. To help us narrow down the issue, can you attempt a migration using Truffle version 5.0.3? There may be incompatibilities with the latest version of Truffle.

    Truffle v5.0.3 (core: 5.0.3)
    Solidity v0.5.0 (solc-js)
    Node v10.13.0

    If that doesn't work, can you share the contract you're testing with?


    Microsoft Azure Blockchain Team

    Saturday, October 26, 2019 12:31 PM