hyperledger/fabric · error

Channel does not exist: %s

Error message

Channel does not exist: %s

What it means

SupportImpl.GetTxSimulator was asked for a transaction simulator for a ledger name that does not exist on this peer. Peer.GetLedger returned nil, so the endorser cannot create a tx simulator and returns this error instead of proceeding with endorsement simulation.

Source

Thrown at core/endorser/support.go:64

func (s *SupportImpl) NewQueryCreator(channel string) (QueryCreator, error) {
	lgr := s.Peer.GetLedger(channel)
	if lgr == nil {
		return nil, errors.Errorf("channel %s doesn't exist", channel)
	}
	return lgr, nil
}

func (s *SupportImpl) SigningIdentityForRequest(*pb.SignedProposal) (endorsement.SigningIdentity, error) {
	return s.SignerSerializer, nil
}

// GetTxSimulator returns the transaction simulator for the specified ledger
// a client may obtain more than one such simulator; they are made unique
// by way of the supplied txid
func (s *SupportImpl) GetTxSimulator(ledgername string, txid string) (ledger.TxSimulator, error) {
	lgr := s.Peer.GetLedger(ledgername)
	if lgr == nil {
		return nil, errors.Errorf("Channel does not exist: %s", ledgername)
	}
	return lgr.NewTxSimulator(txid)
}

// GetHistoryQueryExecutor gives handle to a history query executor for the
// specified ledger
func (s *SupportImpl) GetHistoryQueryExecutor(ledgername string) (ledger.HistoryQueryExecutor, error) {
	lgr := s.Peer.GetLedger(ledgername)
	if lgr == nil {
		return nil, errors.Errorf("Channel does not exist: %s", ledgername)
	}
	return lgr.NewHistoryQueryExecutor()
}

// GetTransactionByID retrieves a transaction by id
func (s *SupportImpl) GetTransactionByID(chid, txID string) (*pb.ProcessedTransaction, error) {
	lgr := s.Peer.GetLedger(chid)
	if lgr == nil {

View on GitHub (pinned to 2736b63f8f)

Solutions

1. Fix the channel name in the client/SDK configuration to match a joined channel
2. Join the peer to the channel if it should participate (peer channel join)
3. Check 'peer channel list' and peer logs to verify channel availability and startup completion
4. Retry after the peer finishes opening ledgers if the request raced startup

Example fix

// before
const channel = network.getChannel('mychannel-typo');
// after — match the joined channel name exactly
const channel = network.getGateway().getNetwork('mychannel');

if (!peer.channels?.includes(ledgername)) throw new Error(`skip ${peer.name}: not joined to ${ledgername}`);

try {
  await contract.submitTransaction(...);
} catch (e) {
  if (e.message.startsWith('Channel does not exist')) {
    // fix channel name / join peer, do not blind-retry
  }
  throw e;
}

When it happens

Trigger: Validate/ProcessProposal path calling Support.GetTxSimulator(ledgername, txid) where the proposal's ChannelID is not a channel this peer has joined, or the ledger has not been opened yet at peer startup.

Common situations: Client submitting a proposal to the wrong peer or with a wrong channel name; peer freshly started still loading channels; application config (channelName) mismatched with deployed network; peer joined the channel via config rather than join and genesis block invalid.

Related errors

• failed obtaining channel state
• channel %s doesn't exist
• transient store for channel %s was not initialized
• failed to look up the ledger for Channel %s
• Could not retrieve ledger for channel %s

AI-assisted analysis of hyperledger/fabric@2736b63f8f (2026-09-04). Data as JSON: /api/errors/e4809f53b4615a99. Report an issue: GitHub.