cancel
Showing results for 
Search instead for 
Did you mean: 

Crystal in dot net application

bcla
Participant
0 Kudos

All,

Didn't there used to be a way...debugger of sorts that one could use when trying to display a crystal report in a Dot Net application that would give the true error, not the generic "can't display PDF or the File does not begin with PDF" non helpful error messages....

Thanks for any ideas.

Respectfully.

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Because CR for VS is created with dll's there is no real way to actually get the actual error. All CR can do is pass the error being passed to us and display it. Some errors d o belong to us but the majority of them now are simply being passed to us.

Try Googling that error message, I found this. It's a Adobe Reader error:

https://forums.adobe.com/thread/1196929

CR requires Adobe reader to be installed to be able to generate PDF files.

Don

Answers (2)

Answers (2)

daniel_paulsen
Active Contributor
0 Kudos

it sounds as though you are exporting to PDF and the browser is trying to open the exported file. Then you get the error.

Try using a browser that will not automatically try to display the exported file, but will allow you to download the file (chrome, firefox)

Can you open the file in acrobat reader? (if you cannot download the file, then you should have a temp copy of the file in your %temp% folder since it needs to download before it can open in a browser.

Open the downloaded file in a text editor (ie : notepad)

the first line in the file should be "%pdf" and then the pdf format version number. If the export failed, then you might see an error explaining why in the first line when viewing the file in notepad

Dan

bcla
Participant
0 Kudos

Thanks Dan. I think it has more to do with the crystal engine version on the server and whats expected in the report.

daniel_paulsen
Active Contributor
0 Kudos

yes, you can trap exceptions and get the exception and inner exceptions, but the errors you mentioned are typically PDF errors, not Crystal Errors. The errors you mentioned either mean the PDF is corrupt or not in the correct format.

Are you acutally getting an exported file from your application without any errors?

bcla
Participant
0 Kudos

no, just an error message box.