Blockchain Hyperledger Fabric — Errors & Solutions

Source: Google(iStock)

Error No 1:

Error: Error trying to ping. Error: 2 UNKNOWN: make sure the chaincode test-registry has been successfully instantiated and try again: could not find chaincode with name ‘test-registry’

Error No 2:

Error:
docker: Error response from daemon: Conflict. The container name “/composer-playground” is already in use by container “9f224b04663a4fa65f50843e5f7e28f7e7df662507a9b42ae5dfc72fd3433405”. You have to remove (or rename) that container to be able to reuse that name.
See ‘docker run — help’.

Error No 3:

Error: Chaincode already exists error

Error No 4:

Error: NG Serve Error

Error No 5:

Error: Authorisation error REST-API

Error No 6:

Discovering types from business network definition …
Connection fails: Error: Error trying to ping. Error: 2 UNKNOWN: make sure the chaincode ‘network-name’ has been successfully instantiated and try again: could not find chaincode with name ‘network-name’

ERROR No 7:

ERROR: for couchdb Cannot create container for service couchdb: Conflict. The container name “/couchdb” is already in use by container “de8ceaf8f21b53bb4c9883eb618448f6f07c7690bea8ab122ef3b689e846eab4”. You have to remove (or rename) that Creating orderer.example.com … error

Error No : 8

Error: Cannot find module ‘fabric-client’

Error No : 9

Error: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm WARN Local package.json exists, but node_modules missing, did you mean to install?

Error No: 10

Error: Angular2 app generated by “yo fabric-composer” does not have UI for Transactions

Solution Update :

Go to <transaction>.component.html file in src/app/<transaction> folder and check for line
<button type=”button” class=”btn btn-primary invokeTransactionBtn” data-toggle=”modal”>Invoke</button>

Error No: 11

Error: Connection fails: Error: Error trying to ping. Error: Composer runtime (0.19.8) is not compatible with client (0.19.5)
It will be retried for the next request.

Error No 12:

ERROR: curl: (7) Failed to connect to localhost port 49160: Connection refused

Error No 13:

ERROR: network composer_default id b1067bdec4ca1800510fc9cc1f5d3500736e48920693b03831df0d8d8472ffac has active endpoints

Error No 14:

Error: Node.JS Error: ENOSPC

Error NO 15:

Error: failed to create deliver client: orderer client failed to connect to orderer.example.com:7050: failed to create new connection: context deadline exceeded

Error No 16:

Error No : 17

Error: container is marked for removal and cannot be started

Error No : 18

Error: sendPeersProposal — Promise is rejected: Error: chaincode with name ‘chain-code-name’ already exists

Error No : 19

CRIT 008 Error on outputBlock: Error writing genesis block: open ./channel-artifacts/genesis.block: no such file or directory

Error No : 20

Error: readBlock -> DEBU 00a Got status: &{FORBIDDEN} Error: can’t read the block: &{FORBIDDEN}

Error No : 21

grpc: addrConn.createTransport failed to connect to {peer0.org1.example.com:7051 0 <nil>}. Err :connection error: desc = “transport: Error while dialing dial tcp: lookup peer0.org1.example.com on 127.0.0.11:53: no such host”. Reconnecting…

Error No : 22

Error: Network Not found issue

Error No : 23

Error: Sending the Instantiate Proposal ..
error: [Peer.js]: sendProposal — timed out after:45000

Error No : 24

Error: could not assemble transaction: ProposalResponsePayloads do not match — proposal response: version:1 response:<status:200 >

Error No :25

Error: Calling enrollment endpoint failed with error [Error: connect ECONNREFUSED 127.0.0.1:7054]

Error No : 26 instantiate-chaincode-Instantiate proposal was bad

This error would mostly occur when you try to instantiate the Chaincode.

  • Bundling the code together
  • Trying to create a container with chaincodename-chaincode version

Error 27: instantiate-chaincode — Error: ChannelEventHub has been shutdown

Solution: Mostly this occurs in “instantiate-chaincode” section, eventhub will get disconnect when it finds more than one chaincode version (when you upgraded with multiple version of same chaincode). Just kill all the containers, just keep the one that’s the latest version then try install & instantitate the chaincode

Error 28: instantiate-chaincode — Error: ChannelEventHub has been shutdown

Solution: Mostly this occurs in “instantiate-chaincode” section, eventhub will get disconnect when it finds more than one chaincode version (when you upgraded with multiple version of same chaincode). Just kill all the containers, just keep the one that’s the latest version then try install & instantitate the chaincode

Error 29: Cannot use encKey (type string) as type []byte in argument to entities.NewAES256EncrypterEntity

Error 30: instantiate Proposal was bad — Chaincode

Solution: When you find this error,

Coinmonks

Coinmonks is a technology-focused publication embracing decentralize technologies. We are Non-profit and education is our core value. Learn, Build and thrive. Our other project— https://coinmonks.com, https://cryptofi.co, https://coincodecap.com

Logeswaran Audhikesavan

Written by

www.zuiverinfotech.com

Coinmonks

Coinmonks

Coinmonks is a technology-focused publication embracing decentralize technologies. We are Non-profit and education is our core value. Learn, Build and thrive. Our other project— https://coinmonks.com, https://cryptofi.co, https://coincodecap.com