Exchange 2016 Event 8676 Repeating

Thomas Grassi
Thomas Grassi used Ask the Experts™
on
Exchange 2016 CU9 DAG2 Node
Windows 2016 Datacenter

Log Name:      Application
Source:        MSExchange Common
Date:          8/28/2018 4:00:57 PM
Event ID:      8676
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      SRV021-N1.mynet.com
Description:
The description for Event ID 8676 from source MSExchange Common cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

26236 w3wp: SerializationTypeBinder load fields on type Microsoft.Exchange.Transport.MessageResubmission.RequestBrokerListenerComponentImpl+<>c failed: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Exchange.Common.RequestBrokerSettings, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.Exchange.Common.RequestBrokerSettings, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
   at System.Signature.GetSignature(Void* pCorSig, Int32 cCorSig, RuntimeFieldHandleInternal fieldHandle, IRuntimeMethodInfo methodHandle, RuntimeType declaringType)
   at System.Signature..ctor(IRuntimeFieldInfo fieldHandle, RuntimeType declaringType)
   at System.Reflection.RtFieldInfo.get_FieldType()
   at Microsoft.Exchange.Data.SerializationTypeBinder.<>c__DisplayClass17_0.<ExpandSerializableTypes>b__0(FieldInfo x)
   at System.Linq.Enumerable.WhereArrayIterator`1.MoveNext()
   at Microsoft.Exchange.Data.SerializationTypeBinder.ExpandSerializableTypes(HashSet`1 serializableTypes, Type type)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
.

the message resource is present but the message is not found in the string/message table

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchange Common" />
    <EventID Qualifiers="0">8676</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-08-28T20:00:57.943324900Z" />
    <EventRecordID>952884</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SRV021-N1.mynet.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>26236 w3wp: SerializationTypeBinder load fields on type Microsoft.Exchange.Transport.MessageResubmission.RequestBrokerListenerComponentImpl+&lt;&gt;c failed: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Exchange.Common.RequestBrokerSettings, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.Exchange.Common.RequestBrokerSettings, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
   at System.Signature.GetSignature(Void* pCorSig, Int32 cCorSig, RuntimeFieldHandleInternal fieldHandle, IRuntimeMethodInfo methodHandle, RuntimeType declaringType)
   at System.Signature..ctor(IRuntimeFieldInfo fieldHandle, RuntimeType declaringType)
   at System.Reflection.RtFieldInfo.get_FieldType()
   at Microsoft.Exchange.Data.SerializationTypeBinder.&lt;&gt;c__DisplayClass17_0.&lt;ExpandSerializableTypes&gt;b__0(FieldInfo x)
   at System.Linq.Enumerable.WhereArrayIterator`1.MoveNext()
   at Microsoft.Exchange.Data.SerializationTypeBinder.ExpandSerializableTypes(HashSet`1 serializableTypes, Type type)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
.</Data>
  </EventData>
</Event>

Open in new window


I get this event serveral times on both Nodes.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Edward van BiljonMessaging and Collaboration Technical Lead (Exchange MVP & MCT)

Commented:
Hi

Same as my other comment. Any updates applied?
Pavel MarinovCommercial Technical Support

Commented:
Hi,

DO you have any negative results from this warning?
 Seems like issues with uninstalled software, or something which has modified the files?
If you do not have any issues with the server I would advise that you just leave it be.

If you insist you can contact MS Premier Support, as professional support won't take the case if you do not have issues.

As Edward said, if you have modified software on the machine it may be as result. Typically MS Common events can be disregarded.

Best regards,

Pavel
Systems Administrator
Commented:
No Answer on this one closing this

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial