cancel
Showing results for 
Search instead for 
Did you mean: 

SP14 ClickOnce PublicKey not correct?

Former Member
0 Kudos

I failed install SP14 runtime by ClickOnce.

Error message in log file is "CRRuntime_32bit_13_0.msi has changed since it was initially published".

I compared following A with B, and I confirmed that they were different.

A) PublicKey attribute in <PackageFile> element in product.xml

B) Public key of the .msi file's certificate signer. (by looking property dialog in explorer.exe)

Is wrong product.xml?

Accepted Solutions (1)

Accepted Solutions (1)

former_member183750
Active Contributor
0 Kudos

Th 0 (zero) in CRRuntime_32bit_13_0 tells me that you are not using SP 14. Else the name would be:

CRRuntime_32bit_13_14

For SP 14 see: 

- Ludek

Senior Support Engineer AGS Product Support, Global Support Center Canada

Follow me on Twitter

Got Enhancement ideas? Use the SAP Idea Place

Answers (2)

Answers (2)

Former Member
0 Kudos

Sorry, I made a mistake in writing 'CRRuntime_32bit_13_0.msi' with 'CRRuntime_32bit_13_0_14.msi' by previous post.

"CRRuntime_32bit_13_0_14.msi has changed since it was initially published" is correct in my log file.

(My original log message is translated into Japanese.)

Public key mismatch is exists product.xml in CRforVS_clickonce_13_0_14.zip with CRRuntime_32bit_13_0_14.msi.

former_member183750
Active Contributor
0 Kudos

A bit over two years ago I suggested this for the same issue with SP 5:

C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86

Then in the registry look for the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0

and delete that.

Now, reinstall CRVS

That question was marked as answered, so give it a try.

- Ludek

0 Kudos

Also, those Certificates only have a 3 year life span so you will need to update your code that is relying on them.

Don

Former Member
0 Kudos

Ludek,

I tried the task told me of you.

But my problem is not resolved.

Please confirm me again,

Is there no problem that following public keys (A) and (B) is not equal?

(A)

1. download ClickOnce module from http://downloads.businessobjects.com/akdlm/cr4vs2010/CRforVS_clickonce_13_0_14.zip

2. extract the zip file, get product.xml file.

3. open product.xml, read line 11, "PublicKey" attribute.

This key is A. 19th letter is "c".

3082010a0282010100c7f9c70fcfa3f3a43aa198b27cb818ed7fe30f1be2e64dd2c50890de5224849a69e7004fb272d62ea9fd682ec47674f59d42165394fe6659846e3f610ba7fb4106ca5de6e54b3bf565e8e203e1a37cf7b98f0bc6bab725143a38932f70823ebcad298c4bbc1a8da93266122e701b85f3609b4e22439c4d31640ca20d738833b0212e2ce1427b96e40a3fd1957c63f355b16f1aee813a18db9129fdf5d29f195818223400d25bc8da1d3c769a69a9db4ac65d85f1c2d9385f2ff3a662cb9bb782c9b1b3fc4757b3d183022cc510a31c2d30d7c6729e5e8c8f3c6eaaba82742cd164b8aad37fdfb23d3f5f0407776b45bf633ddbc1c906553c55a9ddfe4bc412950203010001

(B)

1. read line 10 in the same file. get download url http://downloads.businessobjects.com/akdlm/crnetruntime/clickonce/CRRuntime_32bit_13_0_14.msi from "HomeSite" attribete.

2. download the file.

3. right click the downloaded file on explorer.exe, open properties dialog.

4. select "Digital Signatures" tab, select "SAP SE" and click "Details" button.

5. click "View Certificate" button.

6. select "Details" tab, select "Public key" row.

This key is B. 19th letter is "a".

3082010a0282010100a5f02afcbaf295dd82c482b0aa83782a08ea007635afe2e76b57558d6ad708a1c96b86da81894cdbb42214c26674a5c7f233d8bc76c77b3b2cbc8e38033c3c9c26fc5cd0789a462a2a6b2b19ac9321c851a08544dbf42ce697c97b730964c159d533ba56b835b702aa3f30e96cfd76f60a555ebc862828347e468bf126b9eb345a7e488aea3451e9e9eb8412a600d1db811a2c0144697048cd41f100e10ab8225658e1c3b7613a06835e628e2556c0f8bfd1408a0a5fed97892f6b99f49f2f436a0293aa5562fbbd5ee89dc667261e058aa767e168867ceac2081588c1bd800fc2bfcd98773cefd3266f54eb0dc7daf4d5cd1867ea897d39e6a289a4a75eca890203010001

When I edited product.xml key (A) to (B) for trial, I successed install.

So I concluded that distributed product.xml is incorrect.

0 Kudos

Likely the original releases key expired so they published a new one in some SP.

Lots of updates from the original release so you should install SP 14 on your DEV PC and recompile and rebuild the distribution package also.

Don