Windows Installer Service 2

[eaglei]

I have recently developed a problem. I have a P-4, 1.8 with 512ram running Windows 2000 pro. I cannot open some of the programs that are on my computer, nor can I access them via a small LAN. When I try to access the program, I receive the following message, "Windows installer service could not be accessed". I also cannot install any new software as I receive the same installer message. I receive this in my user profile, with administrator rights, as well as the administrator profile. I have contacted my MIS department and they have no ideas what is causing this. They performed a "Repair" of Windows 2000, but this did not solve the problem.
I have downloaded the new "InstMsiW" but I am unable to install it. When I try to install, I receive a message that say that it is already installed. When I try to install from the RUN command, I receive "MSIEXE.EXE ver 2.00.2600.0 Incorrect Command line". When I try to install from SERVICES, I receive "Error5, Access Denied".
I looked in the Registry to locate the "Windows Installer Service" but fould several entries. Does anyone know which one to remove? Or do you have any other ideas?

Thanks,
eaglei

 

[Jasen]

First, have you checked to see if the installer service is disabled in the services control panel?
Second, are there any entries in Event Viewer? ________
Remember, you're unique... just like everyone else.

 

[whythis]

Hi, I also have encountered this phenomenon several times. It usually manifested itself after installing Windows Service Packs (particularly SP3). I tried to correct the problem from Administrative Tools/Services, but that was disabled. I tried using the command line, which was also disabled. To make a very long story very short, everything which could have been used to correct the problem had been disabled. I know SP3 caused it (happened more than once), and I think it was because I had installed Microsoft Office on the machine on two separate OS's, and dear old Micros__t saw it as a license violation, although I doubt that would be necessary to keep an MS servicepack from taking out your system.
I hope you can find someone with the programming knowledge (it's more than registry problems) that can answer this, because I've had to reinstall entire systems at least three times this past year thanks to this scenario. If you can get the answer, I WANT IT TO! Thanks
whythisagainwhythisagainwhythisagainwhythisagainwhythisagain

 

[John Lewis]

This looks a whole lot like what you are describing:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;319624

 

[whythis]

Thanks and KUDOS! I have tried repeatedly to find this info. As this problem has shut down my systems repeatedly, I am sure this is eventually going to save me a few days' reinstituting a system. The article does not specify 2K however, although it specifies XP....hmmmmmm....I remember once when my command prompt in 2K was disabled, I was overjoyed to actually find a TechNet article pertaining to the exact problem. I opened the article and read "We are aware that this is an issue", etc.
whythisagainwhythisagainwhythisagainwhythisagainwhythisagain