Since upgrading to Crystal 13 ver 29 My Installshield 202 build fails. I finally tracked this issue down to this item:
'Registry.64.40F45FBC.1C75.4AA9.A7FC.681E840B3A9C' in the SAP Crystal Report runtime engine for .NET Framework 4 merge module. I have attempted to set 64 bit = No but in the Edit with Installshield that allows direct edits to the merge module but it is already set to 64 bit = NO. My question is: can I delete this item from the merge module and expect the runtime to still work in this project?
To elaborate further the Installshield error is 5008 and refers to a 64 bit component being required in the Installshield project that is set to 32 bit. The previous version of the Crystal Reports merge module used was ver 13_0_16 (now on 13_0_29). This older version did not include this "Registry.64.40..." item in the merge module and built w/o error in Installshield. Unfortunately Version 29 of the the CR runtime is required for use in Visual Studio 2019 so there is no alternative left and we are unable to built this production product for our custoemrs.
Crystal Reports Developer, for Visual Studio SP 29
To get past this build error do the following:
- Search for “Registry.64.40F45FBC.1C75.4AA9.A7FC.681E840B3A9C”
- Remove entries from Component, ModuleComponents and Registry table by deleting the row identified in search. Save the msm file.
- There are no entries for this language msm’s so no need to modify them.
- Generate the installShield installer with saved msm file.
cr for vs, installshield, Registry.64.40F45FBC.1C75.4AA9.A7FC.681E840B3A9C, error 5008 , KBA , BI-DEV-NET , BI Software Development Kits (SDKs) - .NET or Other , Problem