Windows Installer Service

  • Thread starter Thread starter Jack Snyder
  • Start date Start date
Click Start, Run and type eventvwr.msc
Select the "Application" log
Look for the recent entries with the source column containing "MsiInstaller"
Double-click the entry for more details.
It may show the product name for which the installation/repair took place

================================================
Sample entry
================================================
Event Type: Information
Event Source: MsiInstaller
Event Category: None
Event ID: 11729
Date: 4/13/2007
Time: 11:30:21 AM
Description:
Product: Windows Live Messenger -- Configuration failed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 35 37 31 37 30 30 46 {571700F
0008: 30 2d 44 42 39 44 2d 34 0-DB9D-4
0010: 42 33 41 2d 42 30 33 44 B3A-B03D
0018: 2d 33 35 41 31 34 42 42 -35A14BB
0020: 35 39 33 39 46 7d 2c 20 5939F},
0028: 31 36 30 32 1602
================================================

In some cases, the application name may not be available, but the ProductCode will be available. You can then map the ProductCode with the actual product name using the steps listed in this article:

Windows Installer: Dealing with installation failures:
http://www.winhelponline.com/articles/68/1/

What exactly did you do with Windows Installer Cleanup Utility?
Also, did you reboot the system once, after updating the ImagePath registry value earlier?

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting http://www.winhelponline.com


Hi. Fixing the ImagePath corrected that problem but re-created a problem
that I wrote about on 1/21/2007 "windows installer starts when right click
desktop icon." So I ran msicuu2.exe to fix the right click problem and the
ImagePath got changed back to WINNT.

Ramesh said:
Okie. That's what has prolonged the case ;)

Open Regedit.exe and go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer

Double-click "ImagePath" and fix the value data. It's pointing to WINNT (which is incorrect)

Close Regedit.exe

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting http://www.winhelponline.com


msiexec.exe is in c:\windows\system32. I made a mistake before.

Ramesh said:
C:\WINNT\system32\msiexec.exe
c:\windows\system32
Click to expand...

WinNT or Windows.. Will the real Windows folder please stand up?

Type in Start, Run:

%systemroot%

Press {ENTER}

Which folder is opened now?

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting http://www.winhelponline.com


msi.dll is in c:\windows\system32

There are lots of entries in Event Viewer with red x and source "service
control manager."

Here's the most recent one.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 7/1/2007
Time: 7:05:05 PM
User: N/A
Computer: DENISE-0497C094
Description:
The Windows Installer service failed to start due to the following error:
The system cannot find the path specified.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Click to expand...
Click to expand...
 
Here is the most recent with source MsiInstaller:

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1015
Date: 7/3/2007
Time: 5:44:26 PM
User: DENISE-0497C094\Denise
Computer: DENISE-0497C094
Description:
Failed to connect to server. Error: 0x80070003

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Does this mean anything to you?

msicuu2.exe fixed the right click problem that I mentioned earlier. Yes I
rebooted after changing the ImagePath. Is there anything else you would
suggest doing about these problems?


Ramesh said:
Click Start, Run and type eventvwr.msc
Select the "Application" log
Look for the recent entries with the source column containing "MsiInstaller"
Double-click the entry for more details.
It may show the product name for which the installation/repair took place

================================================
Sample entry
================================================
Event Type: Information
Event Source: MsiInstaller
Event Category: None
Event ID: 11729
Date: 4/13/2007
Time: 11:30:21 AM
Description:
Product: Windows Live Messenger -- Configuration failed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 35 37 31 37 30 30 46 {571700F
0008: 30 2d 44 42 39 44 2d 34 0-DB9D-4
0010: 42 33 41 2d 42 30 33 44 B3A-B03D
0018: 2d 33 35 41 31 34 42 42 -35A14BB
0020: 35 39 33 39 46 7d 2c 20 5939F},
0028: 31 36 30 32 1602
================================================

In some cases, the application name may not be available, but the ProductCode will be available. You can then map the ProductCode with the actual product name using the steps listed in this article:

Windows Installer: Dealing with installation failures:
http://www.winhelponline.com/articles/68/1/

What exactly did you do with Windows Installer Cleanup Utility?
Also, did you reboot the system once, after updating the ImagePath registry value earlier?

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting http://www.winhelponline.com


Hi. Fixing the ImagePath corrected that problem but re-created a problem
that I wrote about on 1/21/2007 "windows installer starts when right click
desktop icon." So I ran msicuu2.exe to fix the right click problem and the
ImagePath got changed back to WINNT.

Ramesh said:
I made a mistake before.
Click to expand...

Okie. That's what has prolonged the case ;)

Open Regedit.exe and go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer

Double-click "ImagePath" and fix the value data. It's pointing to WINNT (which is incorrect)

Close Regedit.exe

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting http://www.winhelponline.com


msiexec.exe is in c:\windows\system32. I made a mistake before.

Ramesh said:
C:\WINNT\system32\msiexec.exe
c:\windows\system32

WinNT or Windows.. Will the real Windows folder please stand up?

Type in Start, Run:

%systemroot%

Press {ENTER}

Which folder is opened now?

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting http://www.winhelponline.com


msi.dll is in c:\windows\system32

There are lots of entries in Event Viewer with red x and source "service
control manager."

Here's the most recent one.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 7/1/2007
Time: 7:05:05 PM
User: N/A
Computer: DENISE-0497C094
Description:
The Windows Installer service failed to start due to the following error:
The system cannot find the path specified.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Click to expand...
Click to expand...
Click to expand...
 
Here is the most recent with source MsiInstaller:

Clear the Application logs. Try to simulate the problem now (right clicking on a file?). Now, open the event logs to see if there are any events registered.

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting http://www.winhelponline.com


Here is the most recent with source MsiInstaller:

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1015
Date: 7/3/2007
Time: 5:44:26 PM
User: DENISE-0497C094\Denise
Computer: DENISE-0497C094
Description:
Failed to connect to server. Error: 0x80070003

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Does this mean anything to you?

msicuu2.exe fixed the right click problem that I mentioned earlier. Yes I
rebooted after changing the ImagePath. Is there anything else you would
suggest doing about these problems?


Ramesh said:
Click Start, Run and type eventvwr.msc
Select the "Application" log
Look for the recent entries with the source column containing "MsiInstaller"
Double-click the entry for more details.
It may show the product name for which the installation/repair took place

================================================
Sample entry
================================================
Event Type: Information
Event Source: MsiInstaller
Event Category: None
Event ID: 11729
Date: 4/13/2007
Time: 11:30:21 AM
Description:
Product: Windows Live Messenger -- Configuration failed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 35 37 31 37 30 30 46 {571700F
0008: 30 2d 44 42 39 44 2d 34 0-DB9D-4
0010: 42 33 41 2d 42 30 33 44 B3A-B03D
0018: 2d 33 35 41 31 34 42 42 -35A14BB
0020: 35 39 33 39 46 7d 2c 20 5939F},
0028: 31 36 30 32 1602
================================================

In some cases, the application name may not be available, but the ProductCode will be available. You can then map the ProductCode with the actual product name using the steps listed in this article:

Windows Installer: Dealing with installation failures:
http://www.winhelponline.com/articles/68/1/

What exactly did you do with Windows Installer Cleanup Utility?
Also, did you reboot the system once, after updating the ImagePath registry value earlier?

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting http://www.winhelponline.com


Hi. Fixing the ImagePath corrected that problem but re-created a problem
that I wrote about on 1/21/2007 "windows installer starts when right click
desktop icon." So I ran msicuu2.exe to fix the right click problem and the
ImagePath got changed back to WINNT.

Ramesh said:
I made a mistake before.
Click to expand...

Okie. That's what has prolonged the case ;)

Open Regedit.exe and go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer

Double-click "ImagePath" and fix the value data. It's pointing to WINNT (which is incorrect)

Close Regedit.exe

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting http://www.winhelponline.com


msiexec.exe is in c:\windows\system32. I made a mistake before.

Ramesh said:
C:\WINNT\system32\msiexec.exe
c:\windows\system32

WinNT or Windows.. Will the real Windows folder please stand up?

Type in Start, Run:

%systemroot%

Press {ENTER}

Which folder is opened now?

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting http://www.winhelponline.com


msi.dll is in c:\windows\system32

There are lots of entries in Event Viewer with red x and source "service
control manager."

Here's the most recent one.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 7/1/2007
Time: 7:05:05 PM
User: N/A
Computer: DENISE-0497C094
Description:
The Windows Installer service failed to start due to the following error:
The system cannot find the path specified.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Click to expand...
Click to expand...
Click to expand...
 
msicuu2.exe fixed the right click problem that I mentioned earlier.

Missed that note. My question still remains.

What exactly did you do with Windows Installer Cleanup Utility?

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting http://www.winhelponline.com



Clear the Application logs. Try to simulate the problem now (right clicking on a file?). Now, open the event logs to see if there are any events registered.

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting http://www.winhelponline.com


Here is the most recent with source MsiInstaller:

Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1015
Date: 7/3/2007
Time: 5:44:26 PM
User: DENISE-0497C094\Denise
Computer: DENISE-0497C094
Description:
Failed to connect to server. Error: 0x80070003

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Does this mean anything to you?

msicuu2.exe fixed the right click problem that I mentioned earlier. Yes I
rebooted after changing the ImagePath. Is there anything else you would
suggest doing about these problems?


Ramesh said:
Click Start, Run and type eventvwr.msc
Select the "Application" log
Look for the recent entries with the source column containing "MsiInstaller"
Double-click the entry for more details.
It may show the product name for which the installation/repair took place

================================================
Sample entry
================================================
Event Type: Information
Event Source: MsiInstaller
Event Category: None
Event ID: 11729
Date: 4/13/2007
Time: 11:30:21 AM
Description:
Product: Windows Live Messenger -- Configuration failed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 35 37 31 37 30 30 46 {571700F
0008: 30 2d 44 42 39 44 2d 34 0-DB9D-4
0010: 42 33 41 2d 42 30 33 44 B3A-B03D
0018: 2d 33 35 41 31 34 42 42 -35A14BB
0020: 35 39 33 39 46 7d 2c 20 5939F},
0028: 31 36 30 32 1602
================================================

In some cases, the application name may not be available, but the ProductCode will be available. You can then map the ProductCode with the actual product name using the steps listed in this article:

Windows Installer: Dealing with installation failures:
http://www.winhelponline.com/articles/68/1/

What exactly did you do with Windows Installer Cleanup Utility?
Also, did you reboot the system once, after updating the ImagePath registry value earlier?

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting http://www.winhelponline.com


Hi. Fixing the ImagePath corrected that problem but re-created a problem
that I wrote about on 1/21/2007 "windows installer starts when right click
desktop icon." So I ran msicuu2.exe to fix the right click problem and the
ImagePath got changed back to WINNT.

Ramesh said:
I made a mistake before.
Click to expand...

Okie. That's what has prolonged the case ;)

Open Regedit.exe and go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer

Double-click "ImagePath" and fix the value data. It's pointing to WINNT (which is incorrect)

Close Regedit.exe

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting http://www.winhelponline.com


msiexec.exe is in c:\windows\system32. I made a mistake before.

Ramesh said:
C:\WINNT\system32\msiexec.exe
c:\windows\system32

WinNT or Windows.. Will the real Windows folder please stand up?

Type in Start, Run:

%systemroot%

Press {ENTER}

Which folder is opened now?

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting http://www.winhelponline.com


msi.dll is in c:\windows\system32

There are lots of entries in Event Viewer with red x and source "service
control manager."

Here's the most recent one.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 7/1/2007
Time: 7:05:05 PM
User: N/A
Computer: DENISE-0497C094
Description:
The Windows Installer service failed to start due to the following error:
The system cannot find the path specified.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Click to expand...
Click to expand...
Click to expand...
 
Hello Ramesh,

I have almost the same problem as Denise!! I redid all the steps and
recorded the Fault messages.
I run W2k prof..
I used to have a Software modem ( isdn Fritzcard) but now I moved and
uninstalled the card! Could that be it??
Somewhere along I read something about Vancouver, BC: I studied Biology at
UBC, and now I'm an MD. But what about it.
The problem is so bad, that I couldn't even install the msicuu2.exe!! Could
You help? Should I post it also where I found the tips?

Follows last HELP letter:

I encountered often a problem, while uninstalling a program: Mistake
description:"Fehler 1719. Auf den Windows Installer-Dienst konnte nicht
zugegriffen werden" beim Hinzufügen oder Entfernen von Programmen

Produkte anzeigen, auf die sich dieser Artikel bezieht

Artikel-ID : 315346

Geändert am : Samstag, 30. Dezember 2006

Version : 14.0

Dieser Artikel wurde zuvor veröffentlicht unter D315346

Dieser Artikel ist eine Ãœbersetzung des folgenden englischsprachigen
Artikels der Microsoft Knowledge
Base:315346--(http://support.microsoft.com/kb/315346/EN-US/) "Error 1719: The
Windows Installer service could not be accessed" error message when you try
to add or remove a program.

Even the programm msicuu2.exe, which is needed to remove the windows
installer, couldn't be installed. What can I do????

I would really appreciate Your help!

Yours sincerely

Dr. Ludwig Winter

cmd /k sc qc msiserver:::Answer ( in almost 100 cases the same!):

Der Befehl "sc" ist entweder falsch geschrieben oder

konnte nicht gefunden werden.


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer]

"Type"=dword:00000120

"Start"=dword:00000003

"ErrorControl"=dword:00000001

"ImagePath"=hex(2):43,00,3a,00,5c,00,57,00,49,00,4e,00,4e,00,54,00,5c,00,73,00,\

79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,73,00,69,00,65,00,78,\

00,65,00,63,00,2e,00,65,00,78,00,65,00,20,00,2f,00,56,00,00,00

"DisplayName"="Windows Installer"

"DependOnService"=hex(7):52,00,70,00,63,00,53,00,73,00,00,00,00,00

"DependOnGroup"=hex(7):00,00

"ObjectName"="LocalSystem"

"Description"="Fügt Anwendungen, die als ein Windows Installer-Paket (*.msi)
angeboten werden, hinzu bzw. ändert oder entfernt sie. Wenn dieser Dienst
deaktiviert ist, können alle Dienste, die explizit davon abhängen, nicht
gestartet werden."



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer\Security]

"Security"=hex:01,00,14,80,a0,00,00,00,ac,00,00,00,14,00,00,00,30,00,00,00,02,\

00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\

00,00,02,00,70,00,04,00,00,00,00,00,18,00,fd,01,02,00,01,01,00,00,00,00,00,\

05,12,00,00,00,20,02,00,00,00,00,1c,00,ff,01,0f,00,01,02,00,00,00,00,00,05,\

20,00,00,00,20,02,00,00,00,00,00,00,00,00,18,00,8d,01,02,00,01,01,00,00,00,\

00,00,05,0b,00,00,00,20,02,00,00,00,00,1c,00,fd,01,02,00,01,02,00,00,00,00,\

00,05,20,00,00,00,23,02,00,00,00,00,00,00,01,01,00,00,00,00,00,05,12,00,00,\

00,01,01,00,00,00,00,00,05,12,00,00,00



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer\Enum]

"0"="Root\\LEGACY_MSISERVER\\0000"

"Count"=dword:00000001

"NextInstance"=dword:00000001





eventvwr.msc, Answer:

Ereignistyp: Fehler

Ereignisquelle: Service Control Manager

Ereigniskategorie: Keine

Ereigniskennung: 7000

Datum: 14.07.2007

Zeit: 08:44:12

Benutzer: Nicht zutreffend

Computer: LUDWIG

Beschreibung:

Der Dienst "Microsoft Legacy Modem Driver" wurde aufgrund folgenden Fehlers
nicht gestartet:

Der angegebenen Dienst kann nicht gestartet werden. Er ist deaktiviert oder
nicht mit aktivierten Geräten verbunden.

%systemroot%: C:\WINNT


Many thanks for Your helP?
Ludwig Winter


Ramesh said:
Click Start, Run, and type SERVICES.MSC. In the right pane, right-click Windows Installer, and then click Start. Also, set the service "Startup Type" to Manual.

"The Windows Installer Service Could Not Be Accessed" error message when you install a program in Windows XP:
http://support.microsoft.com/?kbid=315353
http://support.microsoft.com/?kbid=314810
http://support.microsoft.com/?kbid=315346
http://support.microsoft.com/?kbid=324516

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting http://www.winhelponline.com


I have windows Xp Home Edition w/SP2. I can't install any programs because
I keep getting error message stating either my PC is in safe mode or the
Installer Service isn't installed right. Any suggestions?

Thanks,

Hacksaw
Click to expand...
 
LudwigW said:
Because many problems in W2K can be solved similar to XP,
Click to expand...


Although that's true, many others can not, and that means that asking here
increases the risk that you will get wrong advice. Moreover, Windows 2000
questions are off-topic and inappropriate here. Off-topic posts are likely
to either be ignored, or responded to grumpily, as above.

and I havn't
found yet the w2k group.
Click to expand...


That's because you are using the awful web interface to participate in this
newsgroup. It's the slowest, clunkiest, most error-prone method there is. It
makes it harder to do everything, even find existing groups. Do yourself a
favor and switch to a newsreader, such as Outlook Express, which comes with
Windows.
See http://www.michaelstevenstech.com/outlookexpressnewreader.htm
 
Back
Top