There’s a number of Web Pages about this issue, including official Microsoft Support pages but EventID.NET has the best one.
This is because EventID.NET breaks down the Event ID of the error into specific OS-level error codes, each of which has a different fix. You can find the underlying OS error from Event Viewer in your Computer Management Console under Control Panel.
Finding The Specific OS-Error
Microsoft Installer “Windows Installer Service cannot be accessed throws Event ID 1015. Hunt for this in your Application Event Viewer.
Double click the Event 1015 entry to see the specific OS error:
Take the Event ID to EventID.NET
Go to EventID.NET, type in the EventID you discovered, find the section for MSInstaller, click that, and read through the entries until you find one that refers to your specific OS error.
Either that or just Google on the error message/code you found in the Event Properties and pick the EventID.NET link.
Looks like I was a victim of Failed to connect to server. Error: 0x800706BA. Thanks to the EventID.NET page linked above, and Dmitry Zavgorodniy, who described the fix, I found that this was because:
Dmitriy Zavgorodniy (Last update 4/25/2005):
– Error code: 0x800706BA (Error code 0x800706BA) – This problem occurred when I tried to Add/Remove options for Office 2003 SP1. Check the status of the service “DCOM Server Process Launcher”, if it’s disabled, change the mode to automatic, and start it
I followed Dmitriy’s advice and Windows Installer Service perked up better than Collagen lip-implants.
I also checked that the Windows Installer Service mode was ‘Automatic’. It was ‘Manual’ with a Status of Stopped which would have left it decidedly inert.
Am I MCSA yet ?
The Long Way
Before encountering the shining brilliance of EventID.NET I Googled the Microsoft Support pages and tried method 1, method 2, regedit this, reboot that, rubbing the eyelids of two-headed Cane Toads across the DVD Drive, all to no avail, except for letters of protest from Friends Of Deformed Noxious Vermin Inc..
Get the specific OS error out of the Event Viewer, that’s the trick.