Subreport Links Broken

[Former Member]

I'm trying to work with sub reports, but cannot get the Sub Report Links to work when I deploy the report to the server.

We have an old version of Crystal Reports (XI), but I've even downloaded the evaluation copy (Version 14.1.4.1327) and the problem still exists.

I'm trying to deploy to Windows Server 2008 R2 Enterprise which has Microsoft .NET Framework 4.5.1.

Sub Reports run just fine in my development environment.

Suggestions?

[former_member183750 · Accepted solution]

Hi Donna

How are you "deploying" the report? An app created by you or a 3rd party? What version of VS are you using? What version are the CR assemblies referenced in the project? How do you know the links do not work? (E.g.; symptom, behavior, errors?).

- Ludek

Senior Support Engineer AGS Product Support, Global Support Center Canada

Follow us on Twitter

[Former Member · Accepted solution]

We have product lines that are developed in .Net.  In these products, our development team has an area for "reports" which is pretty standard in our various products.  For deployment, I take a .rpt file developed in CR and point the product to the rpt file as a "Custom" report.  Unfortunately, I don't have access to that code.  I use SQL queries and an OLE DB Provider (Microsoft OLE DB Provider for SQL Server) for the query against our product & subsequent connection.

How would I find out about CR assembly versions, as again, I'm not sure?

I know that the links do not work as there are three parameters needed to run the report.  (Application, Start Date, End Date).  Then there are two Subreport Links (Center/Store) that link the report to the "details" of that report, which are in the subreport.  The 'report' is a broad picture of data, and the 'subreport' are the details (essentially, group by two fields and give all the details underneath in the subreport if needed.)

When the report is run in CR test environment, I see only the three necessary parameters, never the linked fields. When I deploy the report rpt file in the product's website outside the test environment, I see the three original parameters and the two that are created/required by CR for the sub report.  So, the report cannot run successfully, as it doesn't understand what to do with the linked parameters:  "Operation illegal on linked parameter".

I have the SAP Crystal Reports runtime engine for .NET Framwork 4 (64-bit) & Microsoft ReportViewer 2010 SP1 Redistributable (KB2549864) installed on the receiving servers.

[former_member183750 · Accepted solution]

Hi Donna

You will have to go to the "development team" and start your investigation there. As it is, we don't know if the app actually uses the CR SDK, the BI SDK, RAS SDK, etc., etc. Nor do we know how the APIs are implemented. So, the issue should be reported to the development team and if they are not able to help you, they should be contacting us for help.

- Ludek

[former_member11696 · Accepted solution]

Do you mean the report does not work in CR 2013 Designer? If so then it is NOT going to work in your application.

Fix the report first in CR Designer, and it is a 32 bit application so be sure you have the 32 bit client

installed and working.

In the Programs and Features you should see "SAP Crystal Reports runtime engine for .NET Framework 4 (64-bit)", scroll across and it should tell you the version, what is that number?

And "Microsoft ReportViewer 2010" has nothing to do with CR products.

Don

[Former Member]

The report works fine in CR 2013 Designer that I downloaded (evaluation version), and my original version, CR XI.  It does not work when deployed.

How would I determine if it's a 32 bit application?  And what do you mean by the 32-bit client?

The SAP Crystal Reports runtime Engine for .NET Framework 4 (64-bit) version number is 13.0.2.469.

Also of note, although I'm not sure if relevant, I have an "application" server, and a "SQL" server for the application that the report is going into.

[former_member11696]

Hi Donna,

I think you need to go talk to your Developers as Ludek suggested.

Also, Crystal for VS is now up to Service Pack 13 so they should update their project also.

To determine if your app is 32 bit you can ask your developers or look in Task Manager, if their is a *32 beside the exe then it's a 32 bit app.

You Database client needs to match the application platform, 32 bit for CR Designer and 64 bit for your app since you say you only have the 64 bit runtime deployed then it will need the 64 bit DB client. ( MAYBE ) talk to your Developers.

Don