Skip to Content
avatar image
Former Member

DLL Version Error

I am using CR XI sp4 - trying to use these in SQL Server Integration Services Script Component - basically VB.net.

I copied the CrystalDecisions.CrystalReports.Engine.dll and CrystalDecisions.Shared.dll to the SQL Assemblies directory C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies.

I right clicked and found the file version number to be 11.5.9710.1263 however, when I go to Add Reference to my code, the version is shown as 11.5.3700.0.

I have copied these exact same DLL's to another server where I'm trying to run (test environment) and I am getting the following error:

Error: 2008-09-03 10:54:52.13

Code: 0xC0047062

Source: DFT USF Generate Invoices Script Component [106]

Description: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileNotFoundException: Could not load file or assembly 'CrystalDecisions.CrystalReports.Engine, Version=11.5.3700.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.

File name: 'CrystalDecisions.CrystalReports.Engine, Version=11.5.3700.0, Culture=neutral, PublicKeyToken=692fbea5521e1304'

at ScriptComponent_747a507ebf4f448ba138d8dfecfb1899.ScriptMain..ctor()

I have confirmed the DLL's on each of my platforms. Not sure where to go or what to do here.

Ideas?

Thanks.

Scott

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Best Answer
    Sep 04, 2008 at 04:44 PM

    Hi,

    11.5.9710.1263 is the DLL version and 11.5.3700.0 is the assembly version. You cannot just copy these to another machine, you will have to create a setup/install project that includes our merge modules and install them to the new machine.

    https://smpdl.sap-ag.de/~sapidp/012002523100007532242008E/crXIr2sp4_net_mm.zip

    Alternatively you can run this MSI on the other machine to get the DLLs there.

    https://smpdl.sap-ag.de/~sapidp/012002523100007532232008E/crxir2sp4_net_si.zip

    Trevor

    Add comment
    10|10000 characters needed characters exceeded

    • The MSM and MSI file contain all the fixes available in Service Packs, so there should not be a need to run these on your Dev box - as long as it is up to date.

      Now, as for MSM / MSI. They essentially do the same thing; Install the CR runtime. Only difference is, the MSM can be added to your own deployment project that you'd build in say, InstallShield. That way you can make a pretty install interface for your deployment. If all you want to do is deploy once to a server, MSI is the way to go. Double click on it, it asks for a keycode, enter that and off it goes installing the runtime, GAC, reg entries, etc., etc.

      Ludek

  • Sep 04, 2008 at 04:36 PM

    You can not copy the CR runtime. The CR.NET component relies on COM Interop for the backend report processing engine, so XCopy deployments won't work. You must use CR MSM or MSI files.

    MSM and MSI can be downloaded from here:

    http://resources.businessobjects.com/support/additional_downloads/runtime.asp#06

    Ludek

    Add comment
    10|10000 characters needed characters exceeded