To retrieve a more meaningful error message, install a copy of Crystal Reports XI R2 Professional onto the BOE XI R2 Server and try running the report again in CR.
Some possible causes could be:
1) Incorrect data source configuration on the server.
2) Corrupt report file (Do any other reports with the same data source schedule ok?)
What happens if you try to run the report on demand?
The other schduled reports are working fine which uses the same data source and configuration. Sometimes same report is working fine when scheduled and fails sometimes even when i run it on demand. So i am in dilemma what is the actual error. I have Crystal Reports XI R2 Professional installed on BOE XI R2 Server only.
I have checked the event logs and didnot find any problems and errors. So, I added a trace command in report job server after the report failed to check for the logs when i got the same error next time.
I presume you have read KBase Article ID:463766 at support.businessobjects.com which advises to add the following trace command.
To resolve the behavior, add -crpetrace 7 and -trace to the command line parameters for the Crystal Reports Job Server, which handles scheduled reports, or the Crystal Reports Page Server, which handles on-demand reports, in order to enable advanced tracing.
Let us know what it shows. Beware though, tracing slows down processing and creates large log files.
What i observed is somehow when the schduled report is running it is taking all the memory space available on the server and other reports running at the same time are not able to get the memory to run the reports, bcos of this reason the reports are started failing. And one more error i found by going through logs is
"The function PEOpenPrintJobWithAPSInfo failed. Reason: Not enough memory for operation."
i dont know what it is. Any suggestions would be greatly helpful.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.