?
Solved

Cannot Install SQL Server 2005 on Windows Server 2008

Posted on 2010-08-17
4
Medium Priority
?
1,224 Views
Last Modified: 2013-11-14
I am trying to install MS SQL Server 2005 on Windows Server 2008 x64 SP2, and the installer fails at the beginning of the install (Microsoft SQL Native Client) with the message :-

MSI (s) (BC:08) [11:46:41:405]: Product: Microsoft SQL Server Native Client -- 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.

I can confirm that the the server is not in safe mode, and that the Windows Installer service is on Manual and started. I have attempted to unregister/reregister windows installer using the recommended procedure:-
%windir%\system32\msiexec.exe /unregister
%windir%\system32\msiexec.exe /regserver
%windir%\syswow64\msiexec.exe /unregister
%windir%\syswow64\msiexec.exe /regserver
and rebooted the server. No change.

Another kb article suggested renaming the msi.dll's and reinstalling Windows Installer. I have remotely logged onto the server using the Administrator account in RDP (the server is at a remote site) and note that the required files in Windows\System32 have only Read & Execute and Read permissions, and the Oo/s won't allow me to modify the permissions so I can rename them.  Since I am new to Windows Server 2008 security, I don't know how to change the policy settings to allow this.

If anyone can help with any of these items, I would be very grateful.
0
Comment
Question by:cwruck
[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
4 Comments
 
LVL 40

Assisted Solution

by:Vadim Rapp
Vadim Rapp earned 400 total points
ID: 33460377
check the ideas in this thread:
http:Q_26395673.html
0
 

Author Comment

by:cwruck
ID: 33460611
I tried all those suggestions already - none helped.
0
 
LVL 14

Assisted Solution

by:Dhanasekaran Sengodan
Dhanasekaran Sengodan earned 400 total points
ID: 33462771
0
 

Accepted Solution

by:
cwruck earned 0 total points
ID: 33470311
Thanks to those who responded.  We managed to fix the problem as follows:-

The version of Windows Installer 4.5 installed with Windows Server 2008 SP2 was damaged.  We were able to rename the files:-
%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

after turning UAC off, taking ownership of the files as Administrator, and setting write access to the files We then requested, download and installed the hot fix from Microsoft at http://support.microsoft.com/kb/981929. This installed a later, patched and working version of Windows Installer 4.5.  We were then able to install SQL Server 2005 successfully.

I hope this solution helps someone else.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…
Suggested Courses

777 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