Solved

MsiInstaller error 1719 when trying to install Rollup 10 for Exchange 2007 SP1 on SBS 2008

Posted on 2011-09-28
3
1,619 Views
Last Modified: 2012-05-12
Hi there, hoping for some help with this.  

We are supporting a SBS 2008 x64 SP2 box running Exchange 2007 SP1 and are trying to install Rollup 10.  The installation gets to the "copying files" phase before aborting with the error "The Windows Installer service cannot be accessed.  This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed.  Contact your support personnel for assistance."   The following application events are logged;

First an event 1000, application Error;
Faulting application msiexec.exe, version 4.5.6002.18005, time stamp 0x49e02783, faulting module msi.dll, version 4.5.6002.18005, time stamp 0x49e041bc, exception code 0xc0000005, fault offset 0x000000000016ba90, process id 0x24ec, application start time 0x01cc7da1a5646331.

Then an event 11719, MsiInstaller;
Product: Microsoft Exchange Server -- Error 1719. The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed. Contact your support personnel for assistance.

Finally event 1023, MsiInstaller;
Product: Microsoft Exchange Server - Update 'Update Rollup 10 for Exchange Server 2007 Service Pack 1 (KB981407) 8.1.436.0' could not be installed. Error code 1603. Additional information is available in the log file C:\Users\KHA\AppData\Local\Temp\1\MSIe7466.LOG.

The contents of MSIe7466.LOG are identical to the event 11719 in the application log.

So far I have tried the following;
Re-register the windows installer in safe mode using the msiexec /regserver command.
Import HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer from another SBS2008 box on which we had recently installed the rollup without issues.
Checked permissions on HKEY_CLASSES_ROOT, HKEY_CURRENT_USER, HKEY_LOCAL_MACHINE, HKEY_USERS, HKEY_CURRENT_CONFIG and verified the SYSTEM account has full control.  
Verified the Windows Installer service is set to manual startup and that I can start it.
Delete the Enum subkey; however when the installer fails I notice the subkey returns.
Tried to run the Windows installer 4.5 redistributable (Windows6.0-KB942288-v2-x64.msu) however I receive the message that this update is not for this system.
Run sfc /scannow which completed without error.
Uninstall Sophos antivirus, and then reinstalled it when it became apparent that it was not the cause of the problem.
For the sake of it I also tried to install rollup 9 which fails with the same error.  

I have noticed a few forums where people mention changing HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer\WOW64
from a 1 to a 0 resolves the problem, however I don't have the WOW64 subkey on this server.  The working SBS 2008 box doesn't have it either, so I haven't yet bothered to add it.

Any help with this one is very much appreciated :)
 
0
Comment
Question by:CSSROSS
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 2

Accepted Solution

by:
berry_rijnbeek earned 400 total points
ID: 36715832
I found this Microsoft article, maybe it is usefull:
http://support.microsoft.com/kb/315346
0
 

Author Comment

by:CSSROSS
ID: 36720596
Hmmm...  I haven't yet tried method 2 of that article as I wasn't sure how applicable it is to Server 2008; though it makes sense I would need to rename the msiexec files before installing Windows6.0-KB942288-v2-x64.msu.  Will give it a go when I'm able to reboot this server and let you know.  
0
 

Author Comment

by:CSSROSS
ID: 36812906
Thanks for your response, method 2 of that article did actually point me in the right direction.  What I ended up doing was;

Renaming the following files (need to take ownership and assign full control of them first):
%windir%\system32\msi.dll, msi_dll.old
%windir%\system32\msiexec.exe, msiexec_exe.old
%windir%\system32\msihnd.dll,msihnd_dll.old
%windir%\syswow64\msi.dll,msi_dll.old
%windir%\syswow64\msiexec.exe,msiexec_exe.old
%windir%\syswow64\msihnd.dll,msihnd_dll.old

Then installed the Windows Vista x64 hotfix at http://support.microsoft.com/kb/981929.  I then found that the hotfix didn't replace msiexec.exe so I replaced it anyway with a copy from another SBS 2008 box.  After a reboot rollup 10 finally installed.

Hopefully this info helps someone else as well.
0

Featured Post

Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
Suggested Courses

630 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question