A copied and lightly modified Crystal report layout fails with a generic 'no PDF returned' error from Crystal Web Services, even though the original layout it was copied from still works fine with identical print options — how do you find the actual underlying cause?

All FAQ questions / Reporting and analytics

Answer

Enable Crystal Web Service's debug logging and collect the resulting logs — that's the fastest way to see the real underlying error rather than the generic CWS failure message. One easy trap to avoid: make sure the IIS_IUSRS Windows user group has write access to the configured log location first, since without that the debug logs will come back empty (showing only boilerplate placeholder text) even with debug logging turned on, making it look like nothing was captured.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Reporting and analytics questions