Archive for the ‘Computer Management’ Category

The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer.

June 1, 2009

While running a MSI, the Installer tried to start a service and failed, thus aborting the install. It wrote the following message to the Windows Application Event Log.

The description for Event ID ( 0 ) in Source ( PCMConcentrator ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: The service could not determine the name of this machine. This is critical for service discovery to work, hence the service will now terminate..

The critical part of the error was in final two lines The service could not determine the name of this machine.

I chatted to Product Support for the publishers of the service and they told me that the problem was that the computer I was installing the Service on was not part of the correct Domain.

As it happens, I was installing the product on to a Virtual Machine created from a template and indeed had not specified any Domain. The VM was part of WORKGROUP. So I added the VM to the correct domain and the Service was able to start.

HTH.

Windows Installer Service Cannot Be Accessed

January 20, 2009

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.

eventid105

Double click the Event 1015 entry to see the specific OS error:

eventproperties

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.

Finally

If your DVD Drive should stench of decayed Cane Toad giblets, try this.
More info on DCOM Process Launcher Service here and here and of course here