logonlarry
asked on
An API call exited abnormally. Failed to open Document
Hi Experts,
I've recently upgraded a client to Crystal Reports 2008 from Crystal 9. Nothing special about these reports.
However, some of the reports are giving the following error:
An API call exited abnormally. Failed to open Document
I have no idea what this means and no amount of searching the web has turned up anything similar.
I'd be very greatful for a fix as the client has no backups and my master reports are years old.
Larry
I've recently upgraded a client to Crystal Reports 2008 from Crystal 9. Nothing special about these reports.
However, some of the reports are giving the following error:
An API call exited abnormally. Failed to open Document
I have no idea what this means and no amount of searching the web has turned up anything similar.
I'd be very greatful for a fix as the client has no backups and my master reports are years old.
Larry
Try opening reports in CR08 and save with different name. This will prompt you about compatibility. (new report may not be compatible with 9) and then use new report instead of old ones.
How are you running the reports?
mlmcc
mlmcc
ASKER
Hi all,
I'm using CR 2008 Developer 12.0.0.683
Thanks
I'm using CR 2008 Developer 12.0.0.683
Thanks
Are you running in the designer or is there an application that calls the reports?
mlmcc
mlmcc
ASKER
Thanks for the question, just running it in the designer. No application should be calling the report.
I don't know what that means.
Does this occur when you open a report or when you try to preview it?
Have you tried a VERIFY DATABASE?
mlmcc
Does this occur when you open a report or when you try to preview it?
Have you tried a VERIFY DATABASE?
mlmcc
ASKER
Thanks for trying, I cant even open the report to verify. Maybe its possible that the report has been corrupted.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi All,
I've ultimately had to recreate the report again. Could not find what the cause of this issue was. Thanks as always for your assistance.
Larry
I've ultimately had to recreate the report again. Could not find what the cause of this issue was. Thanks as always for your assistance.
Larry
ASKER
The response was great as always except never did get to the root of the problem, had to remake the report