# SYSPRO SRS Print Error and Print Preview Troubleshooting Checklist > Source: https://netray.co/tools/syspro-srs-printing-troubleshooting-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A structured checklist for SYSPRO 8 Reporting Services problems: reports or documents that will not print, preview or email, after an install, upgrade or hotfix. ## Category other-erp ## Erp SYSPRO ## Audience - ERP administrator - SYSPRO consultant - IT support ## Tool **Kind:** checklist **Groups:** #### 1. Services and connectivity **Items:** **Text:** The SYSPRO 8 Reporting Host Service is running on the reporting server and set to start automatically **Critical:** true The SYSPRO e.net communications services used by your site are running on the application server The service account running the Reporting Host Service has rights to the SYSPRO Base folder, the report folders and the SQL databases Ports between client, application server and reporting server are open in Windows Firewall and network firewalls Services were restarted after the last SYSPRO hotfix or reporting software update The reporting server can resolve the SQL Server name used by SYSPRO #### 2. Reporting software and configuration **Items:** **Text:** The Additional Reporting Software version installed is the one the SYSPRO Installer lists for your SYSPRO 8 release and hotfix level **Critical:** true Client-side machines have the matching SAP Crystal Reports runtime and SYSPRO 8 Reporting Components installed The previous reporting software version was removed through the SYSPRO Installer before the newer version was installed Server and clients were restarted after the reporting software update and SYSPRO was relaunched once by an administrator Setup Options reporting settings: client-side or server-side reporting and the server-side configuration are set as intended The SQL Server connection used by the reporting server for SYSPRO data is correct for the company being reported Servers and workstations meet the operating system and .NET Framework prerequisites listed for your SYSPRO 8 release #### 3. Document printing and email **Items:** **Text:** For server-side printing, the target printer is installed on the reporting server for the service account, not only on the user's PC **Critical:** true The document format for invoices, delivery notes or purchase orders points at an existing report file and the right print method The operator's default printer and printer selection in the document print program are valid The report archive folder exists and the service account can write to it Email and SMTP settings in Setup Options are complete for the company and the system The SMTP server accepts relay from the reporting server address If documents route through Document Flow Manager, its service is running and its queue is not stuck #### 4. Preview and client checks **Items:** **Text:** The SYSPRO 8 client release and hotfix level matches the server **Critical:** true A standard, unmodified SRS report previews correctly for the same operator If only a customised report fails, open it in the designer and verify it against tables and columns that changed in the upgrade Custom reports were saved with the Crystal version used by the current reporting software The problem was retested on a second workstation and as a second operator Antivirus or application control is not blocking the Crystal runtime on the client Local client cache and temporary files were cleared and SYSPRO restarted #### 5. Logs and evidence **Items:** Windows Event Viewer (Application log) on the reporting and application servers was checked at the time of failure Reporting service log files in the SYSPRO installation were checked for the matching timestamp The exact error text, report name, operator and print method are recorded SYSPRO diagnostics output was captured before raising a support call Recent changes (hotfix, Windows update, printer driver, certificate) are listed against the date the problem started **Scoring Note:** Work top to bottom. Most SRS failures after an upgrade come from three items: the reporting service not running, a Crystal Reports version that does not match the SYSPRO release, or a server-side printer that exists only on the user's PC. ## Content **Intro:** This checklist walks through SYSPRO 8 Reporting Services (SRS) failures in the order that finds the cause fastest: services, reporting software and setup, document printing, client and preview, then logs. It is built for on-premises SYSPRO 8 sites using SAP Crystal Reports through the SYSPRO Additional Reporting Software. **Sections:** #### How to use it **Body:** 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. **Bullets:** - 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. #### Where this lives in SYSPRO **Body:** Reporting options sit in Setup Options, which holds the choice between client-side and server-side reporting, the server-side configuration and the email settings used when documents are emailed. Document formats for invoices, delivery notes and purchase orders are set per document type, and each points at a report file and a print method. The reporting software itself (the SAP Crystal Reports components and the SYSPRO 8 Reporting Host Service) is installed, updated and removed through the SYSPRO Installer as additional reporting software. Server-side jobs run on the reporting server under the Reporting Host Service account, so folder, database and printer rights are checked for that account, not the user. #### Version differences and gotchas **Body:** 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. #### How to check the result **Body:** A fix is confirmed when the same report and document print, preview and email for the original operator on the original workstation, and a standard report works server-side and client-side if you use both. Then run one high-volume document job, such as an invoice print run, to make sure the service account and printer mapping hold under load. Keep the completed checklist with the hotfix record so the next upgrade starts from known-good settings. **Cta:** If you want SYSPRO report and document questions answered in plain English from your own servers, with no data leaving site, we can set that up. **Faq:** #### Why does SYSPRO print preview not work after an upgrade? **Answer:** The usual causes are a reporting software version that no longer matches the SYSPRO release, client components not updated to the same version as the server, or a customised report that references columns changed in the upgrade. Check the version mapping first, then test a standard report for the same operator. #### What is SYSPRO Reporting Services? **Answer:** SRS is SYSPRO's reporting layer built on SAP Crystal Reports. Reports and documents can render client-side, using the Crystal runtime on the user's PC, or server-side through the SYSPRO 8 Reporting Host Service. The choice and the server-side configuration sit in Setup Options, and the reporting software is installed through the SYSPRO Installer. #### Which Crystal Reports version does my SYSPRO 8 release need? **Answer:** Each SYSPRO 8 release and hotfix level is tied to one Additional Reporting Software version, which bundles a specific SAP Crystal Reports version for the server and matching client components. The SYSPRO Installer and the release notes for your release name it. Install the same version on the reporting server and every client, and remove the old one first. #### Why do server-side SYSPRO documents not reach the printer? **Answer:** With server-side printing the reporting server does the printing under its service account, so the printer must be installed and reachable on that server for that account. A printer mapped only on the user's PC will not work. Check the document format, archive folder rights and Windows Event Viewer on the server too. ## Search terms syspro srs print error, syspro print preview not working, syspro reporting services, syspro server side reporting, syspro crystal reports, syspro reporting host service, syspro additional reporting software --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json