none
How to Resolve Xbap download instead of running and triggers: Event 10032, COMRuntime - An unmarshaling policy check was performed when unmarshaling a custom inproc handler and the class {4B181F0F-4E80-A2AF-E3099AAC069B} was rejected RRS feed

  • Question

  • A web based case management software we run is producing the following Windows Application error when ever an xbap file is called upon that is supposed to pull in MS Word to edit documents within Internet Explorer. The exact same Application error (same error code and details) appears when running the app on its host server (WS 2012 R2) and on an end user desktop (Windows 10). The apps' developers have not encountered this before and were unable to offer a solution. Based on a search of the web, no one has had this exact error message (specifically the 'inproc handler' part) occur and reported it. The Microsoft link cited in the error is dead.

    Instead of using the xbap to pull in MS Word, the Internet Explorer tries to download the xbap file instead.

    Given the error occurs on Win 10 and WS 2012 R2, a previous thread noting this error and MS14-051 is Not Applicable (MS14-051 only applies to WS 2012 R2. I tried removing this update from the server just to be sure and it did not change how the XBAP file was handled by IE).

    Can anyone offer a solution to this error?

    Below are the details:

    Log Name:      Application
    Source:        Microsoft-Windows-COMRuntime
    Date:          4/24/2019 8:34:14 AM
    Event ID:      10032
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      server.subdomain.domain.com
    Description:
    An unmarshaling policy check was performed when unmarshaling a custom inproc handler and the class {4B181F0F-48C8-4E80-A2AF-E3099AAC069B} was rejected
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-COMRuntime" Guid="{bf406804-6afa-46e7-8a48-6c357e1d6d61}" EventSourceName="COM" />
        <EventID Qualifiers="0">10032</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2019-04-24T13:34:14.843117500Z" />
        <EventRecordID>7475764</EventRecordID>
        <Correlation />
        <Execution ProcessID="2896" ThreadID="4344" />
        <Channel>Application</Channel>
        <Computer>MGM-WSS-302.test.efoia.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>{4B181F0F-48C8-4E80-A2AF-E3099AAC069B}</Data>
      </EventData>
    </Event>

    Wednesday, April 24, 2019 5:01 PM

All replies

  • Have you had any luck fixing this issue? I am seeing the same problem while trying to open WPF applications.
    Monday, June 3, 2019 10:20 PM