SYSPRO SRS Print Error and Print Preview Troubleshooting Checklist

How to use it

Start with one failing case and write it down: the report or document, the operator, the workstation, client-side or server-side, and the exact error. Tick items in order and stop to retest after each fix. If a standard report previews but a customised one fails, skip to the preview group; if nothing prints anywhere, the services and configuration groups are where the cause almost always sits. Export the checklist with your notes so the next person does not repeat the same steps.

• Test one standard report and one document (for example an invoice) every time.
• Retest on a second PC to separate client faults from server faults.
• Record the time of each failed attempt so logs can be matched.

Version differences and gotchas

SYSPRO ties each SYSPRO 8 release to a specific Additional Reporting Software version, and the SYSPRO Installer shows which one applies to your release and hotfix level. Moving to a newer SYSPRO 8 release can therefore mean a new Crystal Reports version on the reporting server and on every client. Mixing versions between server and clients is a common cause of preview errors, and custom reports saved in an older designer version can fail even when standard reports work. Read the release notes for the target release before the upgrade weekend, and plan the reporting software update as its own step with its own test of a standard report, a custom report and one emailed document.