DLL Version Error

[Former Member]

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

[former_member200290 · Accepted solution]

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

[Former Member · Accepted solution]

I am downloading and trying the MSI now ... I guess I'm confused why it works fine on one computer and not another ... and also concerned if this is addessing it in the GAC or the SQL Assemblies ...

I installed full CR XIr2 sp4 on Computer A, write code ... I copied those 2 DLL's to computer B - code runs fine, copy those 2 DLL's to computer C, gives me this error. I would have expected computer B to choke as well ...

[former_member183750 · Accepted solution]

Only way I see this working as described for computer B, is if computer B already had the runtime on it. There is no way for it to have worked via copy or xcopy.

We'd have a lot of happy customers that want to use ASPs if we could do that.

Ludek

[Former Member · Accepted solution]

Was just talking it through with a colleague .. computer B does have CR 10 on it so that probably is why it works.

I downloaded the crxir2sp4_net_si.zip file and it gives me 2 msm files. Are those MSI files? BTW - haven't been adeveloper for many years so learning anew here ...

I see 2 msm file ... CrystalReports11_5_NET.msm and CrystalReports11_5_NET_2005.msm. Do I need both of these? I also see the PDF doc and it is broken into two sections FixPack 4.1 and 4.2 ...

None of that really looks relevant for me ... kind of hesitant to proceed.

[Adam_Stone · Accepted solution]

You will want to use CrystalReports11_5_NET_2005.msm to create your setup package as it is used for applications created using VS2005 and the 2.0 framework.

CrystalReports11_5_NET.msm is for use with applications developed with the .NET 1.1 Framework.

[Former Member · Accepted solution]

I see. Well I truly don't use the framework, although SSIS uses 2.0 so I guess I should use the _2005 version. Now my question is ... what do I do with this MSM file? Never seen one before nor does my colleague know what to do with it. Should I also be applying that to my dev machine (it looks like it applies updated fix packs too) in order to keep consistent?

[former_member183750 · Accepted solution]

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

[former_member183750]

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