Different versions of crystal reports

[dilipkumbhar]

I am using SAP B1 9.2 PL:08. As per the SAP, this is the requirement,

SAP Crystal Reports runtime engine for .NET Framework (version: 13.0.16.1954)

SAP Crystal Reports for SAP Business One (version 14.1.8.2060)

Only CR 2013 SP8 for SAP Business One is supported. See SAP Note 1966132.

I have configured SAP cloud server as per above requirement and default crystal reports of sales order are running perfectly.

Now I have developed an addon in VS 2015. I have used crystal report in this addon. The crystal runtime for this addon is 13.0.31.4010. So there are two different runtime i.e. 13.0.16.1954 and 13.0.31.4010 .

When I deploy the addon on the server, the crystal report is not running. It is giving error as ,

An error occurred creating the form. See Exception.InnerException for details. The error is: Retrieving the COM class factory for component with CLSID {C0C99FA5-E1D3-494E-BE0C-73C19424F91C} failed due to the following error: 8007007f The specified procedure could not be found. (Exception from HRESULT: 0x8007007F).

On my development PC, crystal report from addon is running but default crystal reports of sales order is not running.It is giving error as,

Error while connecting to SAP Crystal Reports 2011; check that SAP Crystal Reports 2011 was installed correctly

I want to run both default crystal reports of sales order and addon crystal report. How do I resolve this problem ?

[dilipkumbhar]

Today I have installed crystal report runtime on Azure SAP server i.e. CRRuntime_32bit_13_0_31.msi . After installing this runtime, addon worked properly. Crystal reports from the addon were working properly but the default print layouts developed using crystal report gave error.

For fixing this error I again restored CRRuntime_32bit_13_0_16.

[dilipkumbhar]

I have updated the addon. I have changed the framework to 3.5 and used this in config file,

<bindingRedirect oldVersion="13.0.3500.0" newVersion="13.0.4000.0"/>

Now I am getting error as,

An error occurred creating the form. See Exception.InnerException for details. The error is: Retrieving the COM class factory for component with CLSID {C0C99FA5-E1D3-494E-BE0C-73C19424F91C} failed due to the following error: 8007007f.

I searched and found that I am running 32 bit application on 64 bit OS. We have installed 32 bit SAP client on 64 bit OS. I can not execute 64 bit addon. So all the addons are developed as 32 bit.

How to resolve this error ?

[dilipkumbhar]

I have checked the version of crystal report on my local PC and Azure cloud SAP server. The version is as follows -

Local PC- 13.0.31

SAP Server- 13.0.16

This is my code from app.config

<bindingRedirect oldVersion="13.0.2000.0" newVersion="13.0.4000.0"/>

What should I specify here as per this scenarion ?

[dilipkumbhar]

Sir,

I have updated the addon. I have updated the app.config , but it gave error as ,

An error occurred creating the form. See Exception.InnerException for details. The error is: Could not load file or assembly 'CrystalDecisions.Windows.Forms, Version=13.0.4000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.

Line= at Sales_MIS.My.MyProject.MyForms.Create__Instance__[T](T Instance)

In the app.config, I have added this data,

 <dependentAssembly>
      <assemblyIdentity name="CrystalDecisions.CrystalReports.Engine" publicKeyToken="692fbea5521e1304" culture="neutral"/>
      <bindingRedirect oldVersion="13.0.16.1954" newVersion="13.0.4000.0"/>
    </dependentAssembly>
In the tried other combinations such as 3500 and 4000, but it did not work.

[DellSC]

Take a look at the information in the Crystal for VS wiki. In particular, look for the WinFormCRViewer.zip download. Just above it, there is a link to KBA Article 2719939, which explains what the zip file contains and how to configure applications so that those compiled with older versions of the runtime will work with newer versions of the runtime. Also, I highly recommend that you update your add-on to use SP32 instead of SP31 - SP31 had a number of memory and viewer issues that have been fixed in SP32.

-Dell