on 11-02-2011 9:55 AM
During the installation of Crystal Report fo VS2010 version 13.0.1 (CRforVS_13_0_1) i have this error message :
Error 1402 Could not open key : HKEY_LOCAL_MACHINE\SOFTWARE\SAP Business Objects\Crystal Reports for .NET Framework 4.0
Crystal Reports. Verify that you have sufficient access to that key, or contact your support personnel.
I have verify minimun requirement for installation and the user that is logged on is Administrator of PC; operating system is XP Pro SP3.
Can you help me
Thanks
Luca Rinaldoni
Entering "Error 1402: in the search box at the top right corner of this web page produces the following KBase:
[1535811 - Error 1402 when installing CRVS2010 running CRRuntime_32bit_13_0.msi|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333533333335333833313331%7D.do]. See if that helps.
Ludek
Follow us on Twitter http://twitter.com/SAPCRNetSup
Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you.
Luca
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have a customer that just ran into the same issue.
The text in the Knowledgebase:
"This error is caused by double backslash characters in the registry table of the MSI."
indicates the problem is due to a mistake in the msi file provided by SAP.
May I ask if that problem has been fixed in a later build of the msi? If so, what is the download link of the fixed version?
It turns out that this problem (bad registry table entries in the msi file provided by SAP) persists even in the service pack 2 version of the install: CRRuntime_32bit_13_0_2.msi
This means that Click-Once installations using the msi file at the SAP web site may fail.
Given that SAP has been aware of the issue, is there expected due date for a fixed version?
Looks like I posted information about this in the wrong thread:
After using ORCA to manually correct the bad registry table entries in the msi file (as suggested in the KBase) leads to invalidating it. Using the modified msi file in a local Install package as a prerequisite causes the install to fail with an error message of:
Setup has detected that the publisher of file '...\CRforVS_clickonce_13_0_2\CRRuntime_32bit_13_0_2.msi' cannot be verified.
I hope this information leads to expediting the release of a fixed version.
Edited by: Ido Millet on Feb 13, 2012 8:13 AM
| User | Count |
|---|---|
| 3 | |
| 3 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.