Deploy CR on WIndows 7 64 bit

[Former Member]

Hello,

We have a desktop (windows form, .net 4.5) application which contains reports that were developed using SAP CR 13.0.14.1720.

Questions:

1. Can the application target 64 bit CPU when using CR? If yes, what libraries should we reference? - We can only find 32 bit CR libraries.

2. What files should be included in our installer, in order for the reports to run on the target machine?

Thank you,

Ken

[former_member183750 · Accepted solution]

Hi Ken

In your project you reference the CR assemblies. VS, being a 32 bit programming tool, will use the 32 bit CR references. On compile, Visual Studio will automatically select 32 or 64 bit - depending on if you compile as 32 bit or 64 bit. You then have to use 32 bit or 64 bit assemblies to deploy your project. You can use the MSM file (32 bit only), or the MSI (32 or 64 bit).

Remember that by definition, "Any CPU" compile will require 64 bit runtime on 64 bit OS. Links to the runtime files are in the same doc as the CRVS downlod (SAP CR 13.0.14.1720):

Do not "include files" individually in deployment projects. Use the MSM or MSI.

- Ludek

Senior Support Engineer AGS Product Support, Global Support Center Canada

Follow me on Twitter

[Former Member · Accepted solution]

Hi Ludek,

Thank you for your answer. Can you please clarify the following:

1. Should we run the MSI on every target machine?

2. We take the dll to reference from from ...\Common\SAB BusinessObjects Enterprise XI 4.0\win32_x86\dotnet\ . We can't find any dll in the win64 folder. Is it OK to reference the above even for win64 deployment?

3. When we try to run VS with target CPU = x64, we can't run the reports. The same happens when we try to run the executable from outside VS. The reports would only work from within VS. Any clue why? Could it be related to item 2 above?

Thank you,

Ken

[former_member183750 · Accepted solution]

1. Should we run the MSI on every target machine?

The MSI is typically used for web deployments or possibly silent installs. So, be it the MSM, or MSI or ClickOnce, they all have to be run on all computers that will have the app installed on them. E.g.; a web app will only be on the server, so run the MSI on the server only. Web app clients do not need the runtime.

2. We take the dll to reference from from ...\Common\SAB BusinessObjects Enterprise XI 4.0\win32_x86\dotnet\ . We can't find any dll in the win64 folder. Is it OK to reference the above even for win64 deployment?

This is all taken care of by VS when you choose the compile option. You just have to reference the assembly(s). Note that when you add the CR viewer to your project, VS automatically adds the necessary CR assemblies. If you do not use the viewer, you have to add these in the VS environment.

3. When we try to run VS with target CPU = x64, we can't run the reports. The same happens when we try to run the executable from outside VS. The reports would only work from within VS. Any clue why? Could it be related to item 2 above?

Can't say as I need more info on "we can't run the reports". Why not? What's the error? Behavior? Symptoms?

- Ludek

[Former Member · Accepted solution]

Hi Ludek and thank you again - your answers are very helpful to us.

With regards to item 3 above, the error we get is: "Failed to load database information. Error in File [report_file_name + GUI ID].rpt: Failed to load database information."

Our reports are using text files as DB:

As you may see, the location is the full path and not a relative one so I don't understand why the report wouldn't find it.

Thank you,

Ken

[ido_millet · Accepted solution]

Perhaps the DAO data connectivity driver is only 32-bit.

Try to switch to ODBC as the connectivity method (in Crystal designer, use the menu option of Database, Set Datasource Location...).

[Former Member · Accepted solution]

Hi Ido,

Thank you but we would like to use text files. We're doing a rewrite of a VB6 app and trying to keep costs down by reusing the existing reports - which are writing text files. Do you know for a fact that the text option is just for 32 bit?

Thank you,

Ken

[ido_millet · Accepted solution]

Yes, according to this: Jet for Access, Excel and Txt on 64 bit systems - ConnectionStrings.com , the suspicion above is correct.

The link above provides an alternative, but keep in mind that you can connect to a text file using ODBC.