troubleshooting Question

NotificationBroker Client Error every second

Avatar of Jeremy Sherlock
Jeremy Sherlock asked on
Exchange
2 Comments2 Solutions281 ViewsLast Modified:
Since we installed Exchange 2016 on premise in March 2019 it has been generating an error every second in the NotificationBroker Client Log. It does not appear to be causing any issues, the only reason we discovered this was the amount of logs that are being generated. We migrated from Exchange 2010 but have decommissioned this and so now just have a single 2016 server. Is it possible to resolve this?
2020-02-24T09:14:41.994Z,zzzEX01,ReceiveNotification,"S:CsmId=OData;S:Sts=UnknownError;S:L=0;S:Ex=Microsoft.Exchange.Rpc.RpcException: Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from ClientAsyncCallState.CheckCompletion: RpcAsyncCompleteCall \r\nEEInfo: ComputerName: \r\nEEInfo: ProcessID: 27252\r\nEEInfo: Generation Time: 24/02/2020 09:14:41\r\nEEInfo: Generating component: 2\r\nEEInfo: Status: 0x000006D9\r\nEEInfo: Detection location: 950\r\nEEInfo: Flags: 0\r\nEEInfo: NumberOfParameters: 0\r\n\r\n\r\n   at Microsoft.Exchange.Rpc.ClientAsyncCallState.CheckCompletion()\r\n   at Microsoft.Exchange.Rpc.NotificationsBroker.ClientAsyncCallState_GetNextNotification.End(String& notification)\r\n   at Microsoft.Exchange.Rpc.NotificationsBroker.NotificationsBrokerRpcClient.EndGetNextNotification(ICancelableAsyncResult asyncResult, String& notification)\r\n   at Microsoft.Exchange.Data.Notification.NotificationClient.<>c__DisplayClass36_0.<OnNotification>b__0(NotificationClientLogEvent logEvent)"
2020-02-24T09:14:42.995Z,zzzEX01,ReceiveNotification,"S:CsmId=OData;S:Sts=UnknownError;S:L=0;S:Ex=Microsoft.Exchange.Rpc.RpcException: Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from ClientAsyncCallState.CheckCompletion: RpcAsyncCompleteCall \r\nEEInfo: ComputerName: \r\nEEInfo: ProcessID: 27252\r\nEEInfo: Generation Time: 24/02/2020 09:14:42\r\nEEInfo: Generating component: 2\r\nEEInfo: Status: 0x000006D9\r\nEEInfo: Detection location: 950\r\nEEInfo: Flags: 0\r\nEEInfo: NumberOfParameters: 0\r\n\r\n\r\n   at Microsoft.Exchange.Rpc.ClientAsyncCallState.CheckCompletion()\r\n   at Microsoft.Exchange.Rpc.NotificationsBroker.ClientAsyncCallState_GetNextNotification.End(String& notification)\r\n   at Microsoft.Exchange.Rpc.NotificationsBroker.NotificationsBrokerRpcClient.EndGetNextNotification(ICancelableAsyncResult asyncResult, String& notification)\r\n   at Microsoft.Exchange.Data.Notification.NotificationClient.<>c__DisplayClass36_0.<OnNotification>b__0(NotificationClientLogEvent logEvent)"
2020-02-24T09:14:43.996Z,zzzEX01,ReceiveNotification,"S:CsmId=OData;S:Sts=UnknownError;S:L=0;S:Ex=Microsoft.Exchange.Rpc.RpcException: Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from ClientAsyncCallState.CheckCompletion: RpcAsyncCompleteCall \r\nEEInfo: ComputerName: \r\nEEInfo: ProcessID: 27252\r\nEEInfo: Generation Time: 24/02/2020 09:14:43\r\nEEInfo: Generating component: 2\r\nEEInfo: Status: 0x000006D9\r\nEEInfo: Detection location: 950\r\nEEInfo: Flags: 0\r\nEEInfo: NumberOfParameters: 0\r\n\r\n\r\n   at Microsoft.Exchange.Rpc.ClientAsyncCallState.CheckCompletion()\r\n   at Microsoft.Exchange.Rpc.NotificationsBroker.ClientAsyncCallState_GetNextNotification.End(String& notification)\r\n   at Microsoft.Exchange.Rpc.NotificationsBroker.NotificationsBrokerRpcClient.EndGetNextNotification(ICancelableAsyncResult asyncResult, String& notification)\r\n   at Microsoft.Exchange.Data.Notification.NotificationClient.<>c__DisplayClass36_0.<OnNotification>b__0(NotificationClientLogEvent logEvent)"
2020-02-24T09:14:45.006Z,zzzEX01,ReceiveNotification,"S:CsmId=OData;S:Sts=UnknownError;S:L=0;S:Ex=Microsoft.Exchange.Rpc.RpcException: Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from ClientAsyncCallState.CheckCompletion: RpcAsyncCompleteCall \r\nEEInfo: ComputerName: \r\nEEInfo: ProcessID: 27252\r\nEEInfo: Generation Time: 24/02/2020 09:14:45\r\nEEInfo: Generating component: 2\r\nEEInfo: Status: 0x000006D9\r\nEEInfo: Detection location: 950\r\nEEInfo: Flags: 0\r\nEEInfo: NumberOfParameters: 0\r\n\r\n\r\n   at Microsoft.Exchange.Rpc.ClientAsyncCallState.CheckCompletion()\r\n   at Microsoft.Exchange.Rpc.NotificationsBroker.ClientAsyncCallState_GetNextNotification.End(String& notification)\r\n   at Microsoft.Exchange.Rpc.NotificationsBroker.NotificationsBrokerRpcClient.EndGetNextNotification(ICancelableAsyncResult asyncResult, String& notification)\r\n   at Microsoft.Exchange.Data.Notification.NotificationClient.<>c__DisplayClass36_0.<OnNotification>b__0(NotificationClientLogEvent logEvent)"
ASKER CERTIFIED SOLUTION
Hello ThereSystem Administrator
Join our community to see this answer!
Unlock 2 Answers and 2 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 2 Answers and 2 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros