Faulting application name: MsiExec.exe, version: 5.0.9600.16384, time stamp: 0x52158c02

What is the significance of this error in the microsoft event viewer?

Prior to this this was a small blue circle with no response with control alt delete and requiring the power to be turned off.

Upon restart there was a very slow opening to the screen requesting the country of origin for the keyboard.

SFC /scannow was ran and found no integrity violations.

This is what was displayed in the microosft event viewer:

Log Name:      Application
Source:        Application Error
Date:          11/10/2013 1:40:28 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      a
Description:
Faulting application name: MsiExec.exe, version: 5.0.9600.16384, time stamp: 0x52158c02
Faulting module name: MSI7372.tmp, version: 1.0.0.1, time stamp: 0x5232568a
Exception code: 0xc0000005
Fault offset: 0x00009320
Faulting process id: 0xb80
Faulting application start time: 0x01cedde81ffbcd5b
Faulting application path: C:\Windows\syswow64\MsiExec.exe
Faulting module path: C:\WINDOWS\Installer\MSI7372.tmp
Report Id: 5e06ae21-49db-11e3-beaa-f4b7e2ac6ce4
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-11-10T07:40:28.000000000Z" />
    <EventRecordID>8426</EventRecordID>
    <Channel>Application</Channel>
    <Computer>a</Computer>
    <Security />
  </System>
  <EventData>
    <Data>MsiExec.exe</Data>
    <Data>5.0.9600.16384</Data>
    <Data>52158c02</Data>
    <Data>MSI7372.tmp</Data>
    <Data>1.0.0.1</Data>
    <Data>5232568a</Data>
    <Data>c0000005</Data>
    <Data>00009320</Data>
    <Data>b80</Data>
    <Data>01cedde81ffbcd5b</Data>
    <Data>C:\Windows\syswow64\MsiExec.exe</Data>
    <Data>C:\WINDOWS\Installer\MSI7372.tmp</Data>
    <Data>5e06ae21-49db-11e3-beaa-f4b7e2ac6ce4</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Faulting application name: MsiExec.exe, version: 5.0.9600.16384, time stamp: 0x52158c02
Faulting module name: MSI7372.tmp, version: 1.0.0.1, time stamp: 0x5232568a
Exception code: 0xc0000005
Fault offset: 0x00009320
Faulting process id: 0xb80
Faulting application start time: 0x01cedde81ffbcd5b
Faulting application path: C:\Windows\syswow64\MsiExec.exe
Faulting module path: C:\WINDOWS\Installer\MSI7372.tmp
Report Id: 5e06ae21-49db-11e3-beaa-f4b7e2ac6ce4
Faulting package full name:
Faulting package-relative application ID:


The error prior was:

Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          11/10/2013 1:24:41 AM
Event ID:      10016
Task Category: None
Level:         Error
Keywords:      Classic
User:          LOCAL SERVICE
Computer:      a
Description:
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
 and APPID
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
 to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
    <EventID Qualifiers="0">10016</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2013-11-10T07:24:41.737939300Z" />
    <EventRecordID>11576</EventRecordID>
    <Correlation />
    <Execution ProcessID="876" ThreadID="1392" />
    <Channel>System</Channel>
    <Computer>a</Computer>
    <Security UserID="S-1-5-19" />
  </System>
  <EventData>
    <Data Name="param1">machine-default</Data>
    <Data Name="param2">Local</Data>
    <Data Name="param3">Activation</Data>
    <Data Name="param4">{C2F03A33-21F5-47FA-B4BB-156362A2F239}</Data>
    <Data Name="param5">{316CDED5-E4AE-4B15-9113-7055D84DCC97}</Data>
    <Data Name="param6">NT AUTHORITY</Data>
    <Data Name="param7">LOCAL SERVICE</Data>
    <Data Name="param8">S-1-5-19</Data>
    <Data Name="param9">LocalHost (Using LRPC)</Data>
    <Data Name="param10">Unavailable</Data>
    <Data Name="param11">Unavailable</Data>
  </EventData>
</Event>

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
 and APPID
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
 to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.





 

Question Info


Last updated January 27, 2020 Views 15,124 Applies to:
Answer
Answer

Hi,

 

·         What is the exact issue you are facing with Windows?

 

 

This is a generic error and it doesn't tell much about what caused it. Some applications may fail with this error when the system is left unstable by another faulty program. Usually, a reboot is recommended when this type of error is showing up. If the error is persistent, then one can start digging further (i.e. update the application that is listed in the event), install latest hotfixes, check for viruses and so on.

 

MSIEXEC is related to Windows installer. Unregister and re-register the Windows Installer and check if it helps.

  1. Press Windows key + R, type MSIEXEC /UNREGISTER, and then click OK. Even if you do this correctly, it may look like nothing occurs.
  2. Press Windows key + R, type MSIEXEC /REGSERVER, and then click OK. Even if you do this correctly, it may look like nothing occurs, or you may briefly see an hourglass. After you run this command, the operation is complete.

 

Hope this helps. If you need further assistance with Windows, let us know and will be glad to help.

John Rubdy
Forum Moderator | Microsoft Community

3 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.