Windows Installer Problem

[MrJinje]

I've enabled it, and its created a log file, which is huge, 161Kb text file, and i dont know how to decode it.

So i'm stuck again!

Attach file and someone will take a look.

EDIT: Can you manually start the service. or will the service not start at all.

What about the Application error log (event viewer), are there any entries that could help ?

Edited April 10, 2010 by MrJinje

[ethanmcf]

ok, in the event viewer, there are two entries, one is an error, second is information.

Error:

The description for Event ID ( 11719 ) in Source ( MsiInstaller ) 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: Product: Microsoft ISA Server 2006 -- Error 1719.The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance., (NULL), (NULL), (NULL), (NULL), , .

Event ID: 11719

Second is:

The description for Event ID ( 1033 ) in Source ( MsiInstaller ) 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: Microsoft ISA Server 2006, 5.0.5720, 1033, 1603, (NULL), , .

Event ID: 1033.

The log is attached to the post.

MSIbbe1f.txt

Edited April 10, 2010 by ethanmcf

[Guest]

There are simple fixes for that. You can either:

1. Install KB979302. But this hotfix has known problems.
   
2. Add a registry entry using the following command line as described at RyanVM.net.
   

   Reg.exe ADD "HKLM\SYSTEM\CurrentControlSet\Services\EventLog\Application\MsiInstaller" /v "EventMessageFile" /t REG_EXPAND_SZ /d "%%SystemRoot%%\system32\msi.dll" /f

Edited July 18, 2011 by Tripredacus

[cluberti]

Those errors are important, but the text simply means that the proper .dll information isn't registered properly or doesn't exist on your system (which is probably a hint in and of itself as to what the problem is), hence the generic "no text for this error" text in the event viewer. However, the MSI log *does* give us a clue as to what's wrong - the MSI error thrown in the log is here:

MSI © (10:0C) [02:01:44:634]: Attempting to enable all disabled privileges before calling Install on Server
MSI © (10:0C) [02:01:44:634]: Connected to service for CA interface.
MSI © (10:BC) [02:01:44:644]: Closing MSIHANDLE (1) of type 790542 for thread 776
MSI © (10:08) [02:01:44:664]: Note: 1: 1719 

It is indeed only *partially* registered correct (or appears so to the client-side msiexec binary when attempting to connect securely to the MSI service executable) as referenced by the above. Assuming you did do the following:

- msiexec.exe /unregister

- msiexec.exe /regserver

- Gone into the registry under HKLM\System\CurrentControlSet\Services\MSIServer and verified all of the reg values here match a "working" server (if not, export this key, rename the .reg to .txt, and post here, and we can take a look).

One of these things is incorrect on the system, according to WHERE it's failing (the installation routine handle hand-off from client to server service). The fact we have a log file is promising, but the fact we have event viewer errors and a failure here means the service registration information is munged somewhere, somehow. The above *should* fix it, technically, but if not export the key and we'll check.

[ethanmcf]

Sorry for being a while in replying.

Right Okay, once again I've done msiexec.exe commands, and successfully unregistered then registered it again.

and have attached the Reg key to this post.

All seems normal to me.

reg.txt

[ethanmcf]

Just realised something guys,

basically I'm not able to install MSI's when using the server over Terminal Services, if I'm physically on the server, all is well, and installs fine.

is this normal?

[Guest]

Apparently, this is normal for non-administrators.

Edited April 11, 2010 by 5eraph