1. Windows Installer launches (I assume other applications
that I have successfully loaded does not use this) and
displays "Preparing to Install".
2. The program then seems to "hang".
3. The installation is stopped with the following
message: "The Windows Installer Service could not be
accessed. This can occur if you are running windows in
safe mode (which I am not), or if the Windows Installer is
not correctly installed."
I tried to download another version of Installer, but it
was unsuccessful as it stated I already had the program
installed.
Any suggestions?
Thanks much, Curt
> When I go into windows explorer and click on File windows
> installer wants to start.
Hi
See "Every time I launch my application, Windows Installer performs an
installation. How can I determine the cause of the on-demand installation?"
in the FAQ at
http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx
To access the Application Log in the Event viewer,
run the following command from Start/Run:
eventvwr.msc
If you are running Windows XP (or have access to a Windows XP computer, you can
copy MSIZAP.EXE over to your Win2k computer):
If a product code is listed there and this product is not really installed,
MSIZAP.EXE is maybe able to fix this issue, it is included as a utility in
the support tools installation package (on your WinXP CD) with some additional
documentation included in suptools.chm (installed by suptools.msi).
It will remove all Windows Installer entries for a product key that you feed
it with.
Based on the documentation in
http://msdn.microsoft.com/library/en-us/msi/setup/msizap_exe.asp
this is what you should run:
msizap T {product code}
an example:
msizap T {FFB37294-1155-17D3-A809-0250BAAFB1AB}
--
torgeir
Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of the 1328 page
Scripting Guide: http://www.microsoft.com/technet/scriptcenter
> (snip)
>
> 3. The installation is stopped with the following
> message: "The Windows Installer Service could not be
> accessed. This can occur if you are running windows in
> safe mode (which I am not), or if the Windows Installer is
> not correctly installed."
Hi
Take a look here:
http://groups.google.com/groups?selm=3F678E30.87A7AEB8%40hydro.com