Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 285
  • Last Modified:

Running .Net 1.1 as .Net 2.0 CR throws "Load Report Failed"

I am currently trying to run a .Net 1.1 application under the .Net 2.0 Framework (by modifying the application's config file) but now when I call the Load method of the CrystalDecisions.CrystalReports.Engine.ReportDocument object I get the
above mentioned error "Load Report Failed". I converted the solution to the 2.0 framework and all of my reports open without error (just like the reports did when compiled with the 1.1 Framework and then run under the 1.1 Framework). I need to figure out why there is a problem with Crystal when trying to force a .Net 1.1 app to run as a .Net 2.0 app.

Any ideas? Thanks for any help in advance.

Cheers,

Mike Gorgone
Software Engineer
Blackbaud Inc.
0
mgorgone
Asked:
mgorgone
  • 2
  • 2
2 Solutions
 
mlmccCommented:
What version of Crystal?

What Windows version?

mlmcc
0
 
mlmccCommented:
Crystal provides different merge modules for the 2.0 framework so there may be differences or incompatibilites between the 1.1 modules and .net 2.0

mlmcc
0
 
mgorgoneAuthor Commented:
Crystal version 9 and my dev box is running XP w/ SP2
0
 
frodomanCommented:
Hi Mike,

Interesting question - I suppose the answer would be because of poor design?  There are incompatibilities between the Crystal components for the 1.1 and 2.0 .Net frameworks.  Not only will you find this with the ReportDocument object, but the ReportViewer and CrystalEngine objects seem to have problems as well.

I ran into this situation when I moved apps to a new web server and didn't install the 1.1 framework at all (erroneously assuming it would work under 2.0).  I can't give you a more complete answer as to the 'why' w/out digging into the guts of the Crystal objects but I can confirm that it's nothing you're doing wrong - you need to either continue running it under 1.1 or upgrade the project to 2.0.

frodoman
0
 
mgorgoneAuthor Commented:
The answer has finally been found... it looks like updating the MSM files (getting them from businessobjects.com) did the trick.

Thanks for the replies I guess this can be closed
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now