View Events shows error - At least one receiver for the endpoint is created with epoch of '6'.

Question

What is the meaning of this error and how can I resolve it? I get this error when I use "View Events" option in the "Data Explorer" in the Event Hub instance.

"At least one receiver for the endpoint is created with epoch of '6', and so non-epoch receiver is not allowed. Either reconnect with a higher epoch, or make sure all epoch receivers are closed or disconnected."

Answer 1

Hi @Poonam Deshmukh

Greetings & Welcome to Microsoft Q&A forum! Thanks for posting your query!

What is the meaning of this error - "At least one receiver for the endpoint is created with epoch of '6', and so non-epoch receiver is not allowed. Either reconnect with a higher epoch, or make sure all epoch receivers are closed or disconnected."

This error occurs when you try to use the "View Events" option in the Azure Event Hub's "Data Explorer" and there is an epoch receiver connected to the Event Hub. An epoch receiver ensures that it has exclusive access to the Event Hub partition it is receiving from. If an epoch receiver is connected, non-epoch receivers (like the "View Events" functionality) are not allowed.

• Epoch Receiver - An epoch receiver is created with a specific epoch number (e.g., 6 in your case). It ensures that it has exclusive access to a specific partition of the Event Hub. If a new epoch receiver with a higher epoch value connects, it disconnects any existing epoch receivers with a lower epoch.
• Non-Epoch Receiver - A regular receiver that does not have an epoch number. Non-epoch receivers are not allowed to connect to a partition if there is already an epoch receiver connected.

how can I resolve it? I get this error when I use "View Events" option in the "Data Explorer" in the Event Hub instance.

Here are few steps that might help you in resolving the query:

Stop Conflicting Consumers - Identify and stop any EventProcessorClient or other consumers accessing the Event Hub using the same consumer group. These are likely asserting an OwnerLevel, causing the conflict.

Use a Dedicated Consumer Group - Assign the "View Events" functionality or other consumers to a different consumer group. Consumer groups allow multiple independent applications to process the same events without interfering with each other.

Set OwnerLevel Explicitly - If you control the application using the epoch receiver (e.g., EventProcessorClient), explicitly set the OwnerLevel to a specific value (e.g., 1 or higher) if needed. This can help in asserting priority when debugging or testing.

Retry the "View Events" Feature - Once the conflicting consumers are stopped or isolated to a different consumer group, try using the "View Events" feature again.

For more details, please refer: https://learn.microsoft.com/en-us/azure/developer/java/sdk/troubleshooting-messaging-event-hubs-processor#current-receiver-receiver_name-with-epoch-0-is-getting-disconnected

For similar issue refer this thread: https://stackoverflow.com/questions/69075636/azure-eventhubs-throws-exception-at-least-one-receiver-for-the-endpoint-is-crea

I hope this information helps. Please do let us know if you have any further queries.

Thank you.