Windows Develop Bookmark and Share   
 index > ClickOnce and Setup & Deployment Projects > Launch condition issue while running on Windows server 2008 (64 bit)
 

Launch condition issue while running on Windows server 2008 (64 bit)

Hi,

I have created a setup package in VS 2008 setup and deployment project. I have added a launch condition using registry search for MSCRM 4.0. Setup works fine on 32 bit operating system but MSCRM 4.0 pre requisite fails on Windows Server 2008(64 bit) operating system. It shows the message forpre requisite while MSCRM is installed and registry values also exist. i have tried to create setup x64 too. but same issue appears.

Thanks in advance

Farhan
Farhan A. Siddiqi  Thursday, August 27, 2009 12:19 PM
Setup projects only ever do a registry search in the 32-bit part of the registry, even if they are built for x64. Internally, the RegLocator table does not have the msidbLocatorType64bit bit set in the Type field on x64 builds. So on an x64 system the MSCRM registry item might exist only in the 64-bit part of the registry, and not in the 32-bit view, the Wow6432Node, and both x86 and x64 setups would fail to find it. If you look at the registry and that's the issue, then I'm not sure what you'd do exzcept use Orca to update your x64 MSI file in the RegLocator table:

http://msdn.microsoft.com/en-us/library/aa371171(VS.85).aspx
Phil Wilson
PhilWilson  Thursday, August 27, 2009 11:55 PM
Setup projects only ever do a registry search in the 32-bit part of the registry, even if they are built for x64. Internally, the RegLocator table does not have the msidbLocatorType64bit bit set in the Type field on x64 builds. So on an x64 system the MSCRM registry item might exist only in the 64-bit part of the registry, and not in the 32-bit view, the Wow6432Node, and both x86 and x64 setups would fail to find it. If you look at the registry and that's the issue, then I'm not sure what you'd do exzcept use Orca to update your x64 MSI file in the RegLocator table:

http://msdn.microsoft.com/en-us/library/aa371171(VS.85).aspx
Phil Wilson
PhilWilson  Thursday, August 27, 2009 11:55 PM

You can use google to search for other answers

Custom Search

More Threads

• Get Rid of Warning Screen in Setup Program
• Application manifest has either a different computed hash
• Removing Visual J# dependency
• version of MSDE
• Accepting digital certificate with xbap app
• Where to temper
• Get opened associated file problem
• VS2005 hangs when I create a new Setup and Deployment Project
• How can i install a MSI as a patch ?
• Windows Installer and upgrades