- Running CRRuntime_32bit_13_x.msi or CRRuntime_64bit_13_x.msivia Group Policy Objects produces the following error:
Error 1402. Could not open key: HKEY_LOCAL_MACHINE\SOFTWARE\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\\Crystal Reports. System error 87
- Same error is produced when running the Crystal Reports for Visual Studio 2010 ClickOnce deployment
Crystal Reports for Visual Studios 2010.
- This error is caused by double backslash characters in the registry table of the MSI
- The issue has been identified and logged under Problem Report ID ADAPT01613182
- Download Orca MSI editor from the Microsoft Developer Network (MSDN).
- Open the CRRuntime_32bit_13_x.msi file with the Orca editor. (or CRRuntime_64bit_13_x.msi)
- Find and click the Registry table.
- Right click and export the Registry Table.
- Open the Registry Table with any text editor.
- Do a find for all double backslash characters.
- Remove one backslash character where you find double backslash.
- Save the File.
- Open the CRRuntime_32bit_13_x.msi file again. ( (or CRRuntime_64bit_13_x.msi)
- Right click and drop Table Registry.
- Right click and choose Import Table.
- Import the table you exported and updated above.
- You now have the package that will work via GPO
- Issue has been resolved in Service Pack 3 for Crystal Reports for Visual Studio 2010
cr4vs2010 2010 vs2010 crforvs 13 NET2010 deployment install GPO click once , KBA , BI-DEV-NET , BI Software Development Kits (SDKs) - .NET or Other , Problem