Skip to Content

crystal reports export to RPT or RPTR crashes, all other formats work

On one client's pc, the save or export from a crystal report crashes when saving to ExportFormatType.Crystalreport or ExportFormatType.RPTR. All other exports/saves work as expected. We work with Crystal reports 2013 for VS.

EDIT: crashes = stacktrace starting at ExportToDisk and ending in CrystalDecisions.ReportAppServer.ConvertDotNetToErom.ThrowDotNetException(Exception e) , INNEREXCEPTION = Com error 0x800003e5 (Failed to open report).

We already uninstalled and reïnstalled the crystal 2013 runtime, checked the persmissions on de %temp% folter (where a set of temp files is being created) and the windows\temp folder, giving everyone full control. EDIT: also already tried altering the TEMP path,

Any other suggestions as where to search, as the client now cannot print anything from our application, since we save the rpt with data and print all generated reports together.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Mar 16, 2017 at 05:48 PM

    Suggesting to try SP 19 because we do not patch CR for VS, only full builds.

    The actual location of the temp files is under the users temp folder:

    C:\Users\%USER%\AppData\Local\Temp

    See if that had the temp files in it and clean those out.

    Don

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 31, 2017 at 07:29 PM

    Are you using any Try/Catch in various blocks of code to capture exceptions?

    What SP are you using?

    SP 19 is now available from this link:

    https://wiki.scn.sap.com/wiki/display/BOBJ/Crystal+Reports%2C+Developer+for+Visual+Studio+Downloads

    From the error is appears the user is not able to open the report selected.

    Try deleting all files in the temp folder, could be some leftover temp file is causing issues.

    Don

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 01, 2017 at 06:17 AM

    Don,

    Thanks for the reply , unfortunately:

    - We have our code in try-catch blocks

    - We're using SP 16, which works fine with the exact same reports at this moment in an install base of about 2.500 other customers/pc's, is there any specific reason to try SP19, or is it just a try? for the sake of conformity we'd like to keep all of our customers on the same version

    - Already tried cleaning up the temp folder

    Add comment
    10|10000 characters needed characters exceeded