no combination of peers can be derived which satisfy the endorsement policy: No metadata was found for chaincode ScoreContract in channel mychannel；no peers available to evaluate chaincode ScoreContract in channel mychannel

[qxm-gxy]

Recently, while learning Fabric, I encountered some issues when trying to interact with the test-network using the Fabric Gateway client API.
My node version is 2.5.11.
The network uses the default configuration of the test network, which includes two organizations, each with one peer node, and the default channel created is "mychannel".
The chaincode has been debugged and runs successfully on my Ubuntu.

Here is my Java code:
public void uploadScoreToChain(ScoreToChainDTO scoreToChainDTO) { .... try (Gateway gateway = builder.connect()){ Network network = gateway.getNetwork(blockChainConfig.getChannelName()); Contract contract = network.getContract(getContractName()); String key = scoreToChainDTO.stateKey(); String scoreToChainDTOStr = JsonUtil.toJsonStr(scoreToChainDTO); contract.submitTransaction(methodName, key, scoreToChainDTOStr); } catch (Throwable e) { .... } }

An error occurs at contract.submitTransaction:

Caused by: org.hyperledger.fabric.client.EndorseException: io.grpc.StatusRuntimeException: FAILED_PRECONDITION: no combination of peers can be derived which satisfy the endorsement policy: No metadata was found for chaincode ScoreContract in channel mychannel

Logs from the peer0.org1.example.com node.

Additionally, performing a contract.evaluateTransaction query also results in an error:

org.hyperledger.fabric.client.GatewayException: io.grpc.StatusRuntimeException: FAILED_PRECONDITION: no peers available to evaluate chaincode ScoreContract in channel mychannel

Logs from the peer0.org1.example.com node.

There are no logs from peer0.org2.example.com, possibly due to some configuration issues, but I am not sure how to solve it, feeling a bit at a loss.

This is my Gateway.Builder Java bean configuration class:
`@Bean
public Gateway.Builder gateway() throws Exception {
// Create client identity based on X.509 certificate.
Reader certReader = Files.newBufferedReader(Paths.get("src/main/resources/peerOrganizations/org1.example.com/users/[email protected]/msp/signcerts/[email protected]"));
X509Certificate certificate = Identities.readX509Certificate(certReader);
Identity identity = new X509Identity("Org1MSP", certificate);

    // Create signing implementation based on private key.
    Reader keyReader = Files.newBufferedReader(Paths.get("src/main/resources/peerOrganizations/org1.example.com/users/[email protected]/msp/keystore/priv_sk"));
    PrivateKey privateKey = Identities.readPrivateKey(keyReader);
    Signer signer = Signers.newPrivateKeySigner(privateKey);

    // Create gRPC client connection, which should be shared by all gateway connections to this endpoint.
    ChannelCredentials tlsCredentials = TlsChannelCredentials.newBuilder()
            .trustManager(Paths.get("src/main/resources/peerOrganizations/org1.example.com/users/[email protected]/tls/ca.crt").toFile())
            .build();
    ManagedChannel grpcChannel = Grpc.newChannelBuilder("... :7051", tlsCredentials)
            .overrideAuthority("peer0.org1.example.com")
            .build();

    // Create a Gateway connection for a specific client identity.
    Gateway.Builder builder = Gateway.newInstance()
            .identity(identity)
            .signer(signer)
            .connection(grpcChannel);
    return builder;
}`

[bestbeforetoday]

My guess is that the chaincode named ScoreContract is not successfully deployed in the channel. You try using the Fabric CLI commands to query the installed, approved and committed chaincodes. You could also check for the Docker container hosting the chaincode, in case it is in a stopped state and the container logs can tell you what went wrong.