Error 1719 Windows Installer Windows 2008
Contents |
a 64-bit OS ★★★★★★★★★★★★★★★ Aaron StebnerJuly 20, 200695 0 0 0 A customer recently contacted me due to a problem they were experiencing while trying to install the .NET Framework 2.0 on the error 1719 windows installer server 2008 x64 version of Windows Server 2003. I took a look at the verbose error 1719 windows installer service could not be accessed windows 2008 r2 log file for this scenario and saw the following error: Action start 9:16:59: CA_InstallAssembly.3643236F_FC70_11D3_A536_0090278A1BB8.MSI (s) (B0:F8) [09:17:03:906]: Product: Microsoft .NET Framework error 1719 windows installer windows 7 2.0 (x64) -- 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 error 1719 windows installer server 2003 support personnel for assistance. Usually when I see error 1719, I recommend that the user try to repair the Windows Installer service. However, in this case, that didn't seem to help, and I had to refer this customer to the Microsoft technical support team for further assistance. Our technical support team looked at this scenario in more detail and found that there was an additional set of steps needed
Error 1719 Windows Installer Service Cannot Be Accessed
to repair the Windows Installer service on a 64-bit OS. Here is a complete set of steps that should allow you to repair the Windows Installer service on a 64-bit OS: Click on the Start menu, choose Run, type cmd and click OK Run this command: %windir%\system32\msiexec.exe /unregister Run this command: %windir%\syswow64\msiexec.exe /unregister Run this command: %windir%\system32\msiexec.exe /regserver Run this command: %windir%\syswow64\msiexec.exe /regserver Restart the computer After executing all of the above steps, you can try to re-run the failing setup and hopefully get better results. Note that this workaround is documented in this knowledge base article, but the extra steps that are needed on 64-bit operating systems are somewhat buried in the middle of that article and can be easy to miss. Tags Setup Issues Visual Studio and .NET Framework Comments (95) Cancel reply Name * Email * Website fadildugolli says: May 1, 2008 at 4:56 am here is the solution when everying else fails: I suddenly became unable to install some applications. Whenever I would try, I would get the following: "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.
service could not be accessed" Error Recently, a friend of mine tried to install a program on his Windows Vista machine and the computer gave the blue screen of death http://helpdeskgeek.com/how-to/how-to-fix-the-windows-installer-service-could-not-be-accessed-error/ error. After he restarted his computer, he tried to run a different program and he got the following message: The Windows Installer service could not be accessed. This can occur if the Windows Installer is not correctly installed. If you are getting this error in Vista, here are a few things you can try to fix it! Method 1 "“ Make sure the Windows Installer error 1719 service is started Sometimes, if the Installer service is disabled, you will get this error. You can turn it on by going to Start, then Run and typing in Services.msc. Then scroll down to Windows Installer and double-click on it. Set the Startup Type to Manual and click Start to start the service. You can also start the service by going to Start, Run and type error 1719 windows in net start MSIServer into the Run box. Method 2 "“ Delete MSIEXEC with no extension Another strange thing that can happen is the creation of a second msiexec file in your C:\Windows\system32 directory. By default, there should only be one msiexec.exe file in that directory, but sometimes another one gets created with no extension and a size of 0 KB. If that is the case, then you should rename the extra msiexec file with a .OLD extension. Once you rename it, then you can restart the Windows Installer service. Again, just go to Services and right click on Windows Installer and choose Restart. Method 3 "“ Modify Remote Procedure Call Service Sometimes the issue can be caused by another service called Remote Procedure Call. Go to the Services section again like mentioned above (Start, Run, services.msc) and right-click on Remote Procedure Call (Not the one that says RPC Locator) and choose Properties. Now click on the Log On tab and under Log on as:, choose Local System Account and tick the Allow this service to interact with the desktop checkbox. Then restart your computer and see if the problem goes away. If that doe