cancel
Showing results for 
Search instead for 
Did you mean: 

CRRuntime_12_1_MLB.MSI certificate expired

Former Member
0 Kudos

When installing applications using ClickOnce, the installation fails at this time. Ran good for a long time, but no more.

The download still runs smoothly but the verification step fails with the message:

Setup has detected that the publisher of file '......CRRuntime_12_1_mlb.msi cannot be verified. Click OK to retry the download, or Cancel to exit setup.

When checking the certificate I indeed notice that the Thawth Certificate has expired on the 14th of August.

Is this what is now causing the ClickOnce to fail?????

Please SAP. Address this as I need to deploy my applications using ClickOnce.

Hopefully you can resign and update CR2008 without too many difficulties on your end.

Accepted Solutions (1)

Accepted Solutions (1)

former_member183750
Active Contributor
0 Kudos

Well, the "official" answer, from Product Development is something like this:

It looks like all files in SP1 that require a certificate are expired. In order to fix the problem, all of CR 12 runtime distribution files (not just the redist msi) will need to be rebuilt with a new certificate and re-releasedu2026which is not going to happen!

The solution is to use the latest version (SP2) runtime which has an updated certificate. SP 2 runtimes are here:

MSI:

https://smpdl.sap-ag.de/~sapidp/012002523100009159002009E/cr2008sp2_redistinstall.zip

MSM:

https://smpdl.sap-ag.de/~sapidp/012002523100009159092009E/cr2008sp2_mm.zip

ClickOnce:

https://smpdl.sap-ag.de/~sapidp/012002523100009158992009E/cr2008sp2_clickonce.zip

Ludek

Former Member
0 Kudos

Though it looked like a good resolution of the problem it in fact has a big underlying problem.

All the Date Functions on reports fail on machines that only have the SP2 runtimes installed.

On older PCs that also have SP1 this is not a problem but when deploying applications to new clients with clean machines, none of the reports that include dates function.

My team and I analysed the situation quite seriously to look for a workaround, but unfortunately there are no simple and easy solution. The only one seems to be not to use andy dates.

Maybe updates are forthcoming to correct, fix and address this rather important issue.

/people/ludek.uher/blog/2009/06/23/topic-of-the-week--crystal-reports-report-application-server-business-objects-enterprise

I can demonstrate the problem and error message if you like since it occurs even within Studio 2008 in fact.

My number is 917 929 5343 if you wish to see or discuss this in person.

former_member183750
Active Contributor
0 Kudos

Unfortunately, if you want to discuss the issue over the phone, you will have to create a phone case here:

http://store.businessobjects.com/store/bobjamer/DisplayProductByTypePage&parentCategoryID=&categoryI...

Only other option will be to give me detailed steps to duplicate the issue here. Preferably with a database such as pubs or nwind from MS SQL Server.

Ludek

Former Member
0 Kudos

Thanks for your quick reply Ludek.

There error is very clear and obvious and I have prepared a little app (with source) to reproduce the error on your side.

I have prepared a zip with the Report, XSD and XML files as well an example of app of what we have a problem with.

The zip with source, App and screen captures can be downloaded from: http://www.birchesgroup.net/sap/

The way we use reports is that we produce the DataSet in Code, and then assign the ReportSource to the report.

This is of since we use a Domain Driven Model and not a SQL or Connected solution.

Our application works Offline using our object model and there is no need for SQL server on the Client PC this way.

The report inthe download fails in our application with the following message: (See screen capture as well)

"This field name is not known. Error in File temp_...Error in formula ExMonth: Month({dsExchangeRates_ExchangeRates.EffDAte}). This field name is not known. Details: errorKind"

It occurs only on PC's on which NET2.0 and CrystalReports SP2 is installed (and nothing else)

When SP1 is installed as well, the error disappears and the report works normally.

Further analysis revealed that not a single Date or Data Formatting function actually works with only SP2.

Once you remove the date function (and only use strings for example) all is fine. Format a Date Field and this error immediately shows up again.

Hope this is clearer now and of course hope to see an SP2 update soon since our clients are literally all falling over and into the license key, SP1 trap. No exceptions, ClickOnce is totally not functioning because of SAP at this time and I already had to guide, explain and instruct manual installation at the State Department, Ericsson, Coca Cola Company and others.

Before leaving you to test this out I have 2 more small questions:

Workaround? Maybe I can roll back to an Older version of Crystal. Before 2008 maybe.

Is there a procedure to make our reports work with older versions of Crystal (such as XI or the one from Studio?)

(Finally, and I know this is not your field or specialty probably, but I would like to inform you that I currently have to compile my applications as 32 Bit apps in order to support of Crystal Reports on X64 machines. Any other compile methods fail the installation will not allow the use (on a x64) to open a report. Just a reminder of something that may (or may not) have been addressed by the team when compiling the next Service Pack.

Again I cannot state enough that I appreciate your feedback and I know that these are tough questions and challenges that your team is facing. Crystal has always been a difficult tool, but it is the only and best one in terms of print results.

Hopefully your team gets a better grip on it than did Business Objects and this can lead to an even better tool hopefully.

Already I like the robustness of Crystal 2008 (and the simple installation), but there are a few wrinkles still to iron out.

Looking forward to hearing from you. Many thanks in advance for the effort put into this issue. (From my entire team)

former_member183750
Active Contributor
0 Kudos

The issue is being tracked by QA. For details, pelase see the following htread:

Ludek

former_member183750
Active Contributor
0 Kudos

For a work-around for this issue see the following thread:

Ludek

former_member183750
Active Contributor
0 Kudos

Issue is reported to be resolved in SP 2.3 for CR 2008. The SP is available from here;

https://smpdl.sap-ag.de/~sapidp/012002523100015892592009E/cr2008v1_sp2fp23.exe

I have not tested this SP.

Ludek

Follow us on Twitter http://twitter.com/SAPCRNetSup

Answers (0)