What to check
A document-not-opened exception may be a later symptom of an earlier report-load failure. Historical incidents also involved changes in Crystal runtime requirements. Establish the installed versions and the first error before selecting a repair.
Troubleshooting steps
- Capture the complete exception chain and identify whether report loading, parameter assignment, or rendering first failed.
- Compare the SAP build, Crystal runtime, architecture, and calling application's supported requirements, particularly after an upgrade.
- Install or repair only the supported runtime combination and test a known working report before the affected custom layout.
Confirm the result
Verify preview and PDF export under the intended account. Historical compatibility reports do not prove that a particular old runtime is appropriate for a current SAP installation.