MSIExec Problem

[Filthy McNasty]

Brief background. After ac complete disk image backup, I installed a web
design APP.MSI. 99.99% through the setup it asked for the location of
PFP.EXE. Being prepared, but inexperienced, I had previously downloaded
the latest PHP, plus the latest Apache Server. So, leaving the setup
waiting, I started PHPxxx.MSI. Rats. 99.98% of the way through that it
asked for my Apache htdocs folder. Leaving that setup waiting, I ran
Apachexxx.MSI. Phew. Went back to PHP setup and entered the htdocs info.
Done. Back to the App, gave it the PHP.EXE location. Great. Ran Apache -
Fine. Ran WebDesignApp - Fine. Reboot. Everything slow as treacle. Tried
running an Apache.MSI repair setup - blah, blah, msiservice.exe "Access
is denied". I had installed msiservice a long while back. Never
interfered with msiexec before. The 3 setups above, all MSI had
proceeded without complaint. I reset file associations so that
"Install" was default, correct command line settings. MSIExec came up
with a window full of command line switches. No installation occurred.
Ran repair, no problem. Ran uninstall, no problem. Ran from DOSBox /i
install - Install no problem. Tried explorer install. Blah
msiservice.exe, "Access is denied". Again reset file associations for
msiexec. Window full of command-switches as before. No install. Checked
services. Ensured Windows Installer service on. No install. AAAAARGH.
Reboot. Restored complete disk image. Back to Windows. No webdesignapp,
no php, np apache. Good. Tried Apachexxx.MSI. Got a replay of the
msiservice.exe/msiexec non-install routine as above

So. If MSI worked before my botched 3 setups, before disk image, Why
does it not work after a restore?

And how can I reset file associations for an MSIExec.Exe /i %1 explorer
install. Command line MSIExec /i %1 no problems. What does your registry
say for default msiexec settings? Help. Please

And thankyou. Save my braincells from meltdown

 

[Ramesh, MS-MVP]

Hi,

I don't seem to have the file msiservice.exe in my XP systems. How did you install the file earlier?


Here it is:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Msi.Package]
"EditFlags"=hex:00,00,10,00
"FriendlyTypeName"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,\
00,6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,\
32,00,5c,00,6d,00,73,00,69,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,34,\
00,00,00
@="Windows Installer Package"

[HKEY_CLASSES_ROOT\Msi.Package\DefaultIcon]
@="C:\\WINDOWS\\system32\\msiexec.exe,0"

[HKEY_CLASSES_ROOT\Msi.Package\shell]
@="Open,Repair,Uninstall"

[HKEY_CLASSES_ROOT\Msi.Package\shell\Open]
@="&Install"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,36,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Open\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,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,22,00,20,00,2f,\
00,69,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Repair]
@="Re&pair"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,37,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Repair\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,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,22,00,20,00,2f,\
00,66,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall]
@="&Uninstall"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,33,00,38,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,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,22,00,20,00,2f,\
00,78,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00


--
Regards,

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


Brief background. After ac complete disk image backup, I installed a web
design APP.MSI. 99.99% through the setup it asked for the location of
PFP.EXE. Being prepared, but inexperienced, I had previously downloaded
the latest PHP, plus the latest Apache Server. So, leaving the setup
waiting, I started PHPxxx.MSI. Rats. 99.98% of the way through that it
asked for my Apache htdocs folder. Leaving that setup waiting, I ran
Apachexxx.MSI. Phew. Went back to PHP setup and entered the htdocs info.
Done. Back to the App, gave it the PHP.EXE location. Great. Ran Apache -
Fine. Ran WebDesignApp - Fine. Reboot. Everything slow as treacle. Tried
running an Apache.MSI repair setup - blah, blah, msiservice.exe "Access
is denied". I had installed msiservice a long while back. Never
interfered with msiexec before. The 3 setups above, all MSI had
proceeded without complaint. I reset file associations so that
"Install" was default, correct command line settings. MSIExec came up
with a window full of command line switches. No installation occurred.
Ran repair, no problem. Ran uninstall, no problem. Ran from DOSBox /i
install - Install no problem. Tried explorer install. Blah
msiservice.exe, "Access is denied". Again reset file associations for
msiexec. Window full of command-switches as before. No install. Checked
services. Ensured Windows Installer service on. No install. AAAAARGH.
Reboot. Restored complete disk image. Back to Windows. No webdesignapp,
no php, np apache. Good. Tried Apachexxx.MSI. Got a replay of the
msiservice.exe/msiexec non-install routine as above

So. If MSI worked before my botched 3 setups, before disk image, Why
does it not work after a restore?

And how can I reset file associations for an MSIExec.Exe /i %1 explorer
install. Command line MSIExec /i %1 no problems. What does your registry
say for default msiexec settings? Help. Please

And thankyou. Save my braincells from meltdown

 

[Filthy McNasty]

Using at least one appendage, the entity known in this space-time

Hi,

I don't seem to have the file msiservice.exe in my XP systems. How did
you install the file earlier?

Oddly enough, it is an MSI installation. It installed itself with no
apparent ill effect on the main MSI functions, merely adding an "Edit
With MSIService" option to the .MSI context menu. It is a small app
which allows any .EXE to be made to run as a Service in XP. I forgot to
mention that I run XP Pro SP2

Have just added your Registry info to my Registry. Will reboot and come
back with results

Thankyou for your help. Back soon - I hope :{

 

[Filthy McNasty]

Using at least one appendage, the entity known in this space-time

Have just added your Registry info to my Registry. Will reboot and
come back with results

As many thankyous as you could ever wish for. Everything back to normal.
It's not too surprising that I should have probably corrupted the .MSI
Registry settings by trying to run 3 .MSI installs virtually
simultaneously. I was aware of the stupid risk at the time, but thought
I'd chance it. Surprisingly though, all 3 installations ran perfectly.
What DOES baffle me is that, having restored the system from an
absolutely up to date Acronis TrueImage backup - The entire partition,
not just a partial restore - Why then was there a failure of the .MSI
settings? Everything should have been back to the status quo. And,
despite the fact that MSIService had previously co-existed quite happily
with the Windows Installer Service, I shall not be re-installing it, and
have kept a copy of your .Reg file for use if such a situation should
ever, Bill Gates forbid, happen again due to my stupidity. It WON'T

Add another thankyou for good luck, though luck had nothing to do with
it

And if you can solve the mystery of the TrueImage restore NOT restoring
my .MSI settings, please come back. I have 3 partitions - C, D and E. C
is the main System partition - Windows and programs; D is Archives,
Resources such as Persoal Settings Backups, MP3s, Image files, EBooks,
other similar non-system resources, and a folder for small apps which do
not write to the Registry; E is SwapFile, IE Cache folders, Temp and
sundry App TempFolders. I only restored C and E. Would Windows have
recognised that D had been last shut down at a different, later time
than the restored C & E? Perhaps causing it to do something to the good
restored Registry that conflicted with the good data it contained? I am
very curious, because I have restored from image in the past without any
visible problems, and I would hate to mistrust Acronis TrueImage - Which
is my main backup routine

 

[Ramesh, MS-MVP]

Glad that helped. No idea why ATI did not restore the correct settings for MSI. I wonder if the ATI backup that you have, already has an incorrect data in "[HKEY_CLASSES_ROOT\Msi.Package]"..

--
Regards,

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


Using at least one appendage, the entity known in this space-time
continuum as Filthy McNasty <[email protected]> revealed in

Have just added your Registry info to my Registry. Will reboot and
come back with results

As many thankyous as you could ever wish for. Everything back to normal.
It's not too surprising that I should have probably corrupted the .MSI
Registry settings by trying to run 3 .MSI installs virtually
simultaneously. I was aware of the stupid risk at the time, but thought
I'd chance it. Surprisingly though, all 3 installations ran perfectly.
What DOES baffle me is that, having restored the system from an
absolutely up to date Acronis TrueImage backup - The entire partition,
not just a partial restore - Why then was there a failure of the .MSI
settings? Everything should have been back to the status quo. And,
despite the fact that MSIService had previously co-existed quite happily
with the Windows Installer Service, I shall not be re-installing it, and
have kept a copy of your .Reg file for use if such a situation should
ever, Bill Gates forbid, happen again due to my stupidity. It WON'T

Add another thankyou for good luck, though luck had nothing to do with
it

And if you can solve the mystery of the TrueImage restore NOT restoring
my .MSI settings, please come back. I have 3 partitions - C, D and E. C
is the main System partition - Windows and programs; D is Archives,
Resources such as Persoal Settings Backups, MP3s, Image files, EBooks,
other similar non-system resources, and a folder for small apps which do
not write to the Registry; E is SwapFile, IE Cache folders, Temp and
sundry App TempFolders. I only restored C and E. Would Windows have
recognised that D had been last shut down at a different, later time
than the restored C & E? Perhaps causing it to do something to the good
restored Registry that conflicted with the good data it contained? I am
very curious, because I have restored from image in the past without any
visible problems, and I would hate to mistrust Acronis TrueImage - Which
is my main backup routine

 

[Filthy McNasty]

Using at least one appendage, the entity known in this space-time

Glad that helped. No idea why ATI did not restore the correct settings
for MSI. I wonder if the ATI backup that you have, already has an
incorrect data in "[HKEY_CLASSES_ROOT\Msi.Package]"..

I don't see how. The 3 installs were all made 3 hours after the backup,
they were all .MSI, and they were all successful. So at that point MSIExec
was working perfectly, and therefore the backup should have included
correct .MSI settings in it's Registry. Any foul-ups made after the backup
should have been overwritten by the restored image

Oh well, all's well that ends well. A smack on the head for me, and a peck
on the cheek for you. Right. Butchest voice:

Thankyou again