Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

Possible cause of error code 1719 or 1723 when installing a 64-bit MSI

Possible cause of error code 1719 or 1723 when installing a 64-bit MSI

Rate This
  • Comments 17

I have heard from a few people in the past who have run into setup failures with error code 1719 or 1723 while installing the 64-bit version of the .NET Framework on a 64-bit version of Windows.  I want to describe the underlying issue in a little more detail and provide a couple of possible workarounds in case you run into this type of issue in the future.

How to diagnose this issue

If you are encountering this issue, you will see one of the following errors in the verbose MSI log file for the failing installation:

MSI (s) (DC:FC) [12:34:56:023]: Invoking remote custom action. DLL: C:\Windows\Installer\MSICE44.tmp, Entrypoint: SchedSecureObjects
MSI (s) (DC:B8) [12:34:56:024]: Generating random cookie.
MSI (s) (DC:B8) [12:34:56:051]: Created Custom Action Server with PID 1884 (0x75C).
MSI (s) (DC:98) [12:34:56:092]: Running as a service.
MSI (s) (DC:98) [12:34:56:094]: Custom Action Server rejected - Wrong Context
MSI (s) (DC:B8) [12:34:56:097]: CA Server Process has terminated.
Action start 12:34:56: SchedSecureObjects_x64.
MSI (s) (DC:94) [12:34:56:098]: Note: 1: 1719
CustomAction SchedSecureObjects_x64 returned actual error code 1601 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (DC:94) [12:34:56:738]: Product: Microsoft .NET Framework 4 Client Profile -- 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.

MSI (s) (B4:74) [12:34:56:098]: Note: 1: 1723
CustomAction SchedSecureObjects_x64 returned actual error code 1157 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (B4:74) [12:34:56:738]: Product: Microsoft .NET Framework 4 Client Profile -- Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor.  Action SchedSecureObjects_x64, entry: SchedSecureObjects, library: C:\Windows\Installer\MSIE8C8.tmp

The underlying problem in this scenario is that Windows Installer is incorrectly configured to run in 32-bit mode.  64-bit custom actions cannot run in 32-bit mode, and so any 64-bit MSI that includes a 64-bit custom action (including, but not limited to, all 64-bit versions of the .NET Framework starting with 2.0) will fail in this way the first time it tries to run a 64-bit custom action. 

How to work around this issue

If you are encountering this issue, you can remove the following registry value to prevent Windows Installer from trying to run 64-bit custom actions in 32-bit mode:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msiserver]
WOW64=1

If the above registry value does not exist on your computer, then there is another possible root cause and workaround described in this blog post from Robert Flaming.

  • registry is already set to 1 and still its not installing

  • i check the [this blog post from Robert Flaming] it will not give me any clue. we just did a repair install in windows 7 and still its not installing i tried to check the version of windows installer both in syswow64 and system32, it has version 5.0 im confuse on how will i install this update in a 64 bit computer.

  • i check the HKLM\Software\Microsoft\Windows\CurrentVersion\Installer ! MsiExecCA32

    the registry key is right same goes with the HKLM\Software\Microsoft\Windows\CurrentVersion\Installer ! MsiExecCA64 can i have a much deeper troubleshooting step for this error thanks

  • Hi Ryoko - This blog post only describes one possible cause for this type of error.  Do you have a verbose MSI log file from the failing installation, and if so, can you please upload it to a file server (such as http://skydrive.live.com) and post a link back here so I can download it and take a closer look?

  • Ryoko

    "registry is already set to 1 and still its not installing"

    Read the post again:

    If you are encountering this issue, you can "!remove!" the following registry value to prevent Windows Installer from trying to run 64-bit custom actions in 32-bit mode:

  • Hi,

    I have just changes "wow64=1" to "wow64=0" and all my problems are gone.

    BR.

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msiserver]

    WOW64=0

  • hey it would be nice if you could help me regarding windows installer issue it says it's not installed right and i am running windows 8 and tips/solutions ?

  • Hi John - Could you please provide more detail about the error that you're seeing in this scenario?  What is the exact error message you see, and when do you see it (for example, do you see it when you boot your computer, when you try to launch a specific program, etc)?

  • hey i cheacked  but in my version of windows seven i didint find the folder called msiserver isthat a problem, everything is according except that folder, its just not there.  

  • Hi salman - The msiserver value is a registry sub-key name, not a folder name.  You need to open regedit.exe and look at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msiserver to find it.

  • Hi Aaron

    We are encountering the 1723 error. I"ve got the log files. Unfortunately I've not been able to get access to the systems where this error is encountered.

    I've tried the above steps to reproduce the error in a different Win 8 64 bit machine but not able to reproduce it.

    Could you please help?

    Thanks

    kajal

  • Hi Kajal Biswas - The issue described in this blog post is only one possible cause of a 1723 error.  It isn't the only possible cause.  If you're not able to reproduce the failure by manually changing that registry key, then you're likely hitting a different problem than the one described here.  There is another possible root cause described at blogs.msdn.com/.../439834.aspx.  If that doesn't help either, then I'd suggest doing a web search for Windows Installer error 1723 and trying some of the other things suggested in the forum posts that will appear in the search results.

  • hi Aaron - thanks for the quick response. I'd checked Rob's link also before posting the problem here.

    the error message is ---->

    CustomAction VerifyIfBetaVersionIsInstalled returned actual error code 1157 (note this may not be 100% accurate if translation happened inside sandbox)

    Error 1723.There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action VerifyIfBetaVersionIsInstalled, entry: VerifyIfBetaVersionIsInstalled, library: C:\Windows\Installer\MSIB6F1.tmp

    MSI (s) (AC:94) [12:40:33:424]: Product: QuickBooks -- Error 1723.There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action VerifyIfBetaVersionIsInstalled, entry: VerifyIfBetaVersionIsInstalled, library: C:\Windows\Installer\MSIB6F1.tmp

    Does this give you any hint? its returns 1157 error code. Could not find much on this return code.

    thanks

    Kajal

  • Hi Kajal Biswas - Error code 1157 means ERROR_DLL_NOT_FOUND (One of the library files needed to run this application cannot be found.)  If you're getting that error code from the custom action, it means that there is a problem with the custom action DLL itself, not a problem with Windows Installer like the one described in this blog post.

    In your case, the custom action DLL has a dependency on some other component that is missing from the customer's computer that is seeing this error.  I'd suggest checking what dependencies your custom action DLL has using a tool like dumpbin.exe or Dependency Walker (http://dependencywalker.com/) to see if you can narrow down what might be missing from the customer's computer.

  • Hi

    I use windows 8.1 and when I want to install office 2013,it gives me this error

    error 1719.the windows installer service could not be accessed.

    what can I do??

Page 1 of 2 (17 items) 12
Leave a Comment
  • Please add 7 and 2 and type the answer here:
  • Post