SAP Knowledge Base Article - Preview

1312623 - Error: "The viewer could not process an event. Error in File: xxx Call Timing Max processing time or Max records limit reached []---- Error code:0 [CRWEB00000119]"

Symptom

  • Error: "Crystal Reports: Print Engine Error" displays on BI Launch pad or CMC.
  • Error: "The viewer could not process an event. Error in File xxx:  Call Timing Max processing time or Max records limit reached" displays on BI Launchpad or Central Management Console (CMC).
  • Error: "The viewer could not process an event. Error in File xxx: File too large for attachment. [] ---- Error code:0 [CRWEB00000119]" while viewing Crystal Report in BI Launch Pad or CMC.
  • Error: "Error in File <name of a report>: Max processing time or Max records limit reached" displays on InfoView or CMC.
  • Error: "../cserrinf.cpp:<line number>,Creating new error object,Error message,"Memory full."" is captured in boe_crprocd_crpe.bin_<PID>_Diagnostics.0.log when -crpetrace 7 is added to the command-line parameter on CrystalReportsJobServer.


Read more...

Environment

  • SAP BusinessObjects Business Intelligence platform 4.x 

Product

SAP BusinessObjects Enterprise XI 3.1

Keywords

-MaxDbResultRecords 0, Max records limit reached., limitation, memory full, maximum, large report, big report , KBA , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.