We help IT Professionals succeed at work.

NotificationBroker Client Error every second

Jeremy Sherlock
on
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)"

Open in new window

Comment
Watch Question

System Administrator
BRONZE EXPERT
Distinguished Expert 2018
Commented:
This should be normal behavior for Exchange 2016. I suggest you to use a script that clears the log file regularly. You can create one and use Task Scheduler to run the cleanup process.
Or you can use the existing one.
https://community.spiceworks.com/topic/2202883-exchange-2016-log-files-notificationclient-notificationbroker
Saif ShaikhServer engineer
BRONZE EXPERT
Commented:

As the logs are used for diagnostics only, you can delete the old logs that are no longer used.

Here is a script that helps to remove Exchange logs automatically. The script contains a value Xdays, you can change this to specify the log files that need to be removed.


https://gallery.technet.microsoft.com/Clear-Exchange-2013-Log-71abba44