# SYSPRO reporting API: e.net, SRS server-side reporting, Crystal Reports and SRS preview problems > Source: https://netray.co/erp-help/syspro-reporting-api-srs-preview-not-working-crystal-e-net > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer SYSPRO gives you three reporting routes: the e.net Solutions business object API (XML in, XML out) for programmatic data, SYSPRO Reporting Services (SRS) for designed reports run on the server, and Crystal-based or SQL-based custom reports. If the SRS preview does not work, check the services, the runtime and bitness, the SQL permissions and the client and server versions in that order. ## Kind how-to ## System syspro ## Erp SYSPRO 8 ## Module Reporting / e.net Solutions ## Query syspro reporting api ## Alternate Queries - syspro reporting components - syspro srs preview not working - syspro 8 crystal reports - syspro server side reporting 2024 - syspro api ## Applies To SYSPRO 8 (including recent releases). Product names and architecture of the reporting layer change between releases, so confirm against your release documentation. ## Steps ### Choose the route, then troubleshoot SRS preview **Items:** Decide the need: a data feed or integration (use e.net business objects), a formatted business document or report (use SRS), or ad hoc analysis (use SQL, Power BI or Analytics on a reporting copy). For programmatic access, use the e.net Solutions business objects: query objects such as INVQRY or SORQRY for reading, and post objects for writes, each taking an XML parameters and XML document and returning XML. For SRS, confirm the SYSPRO e.net Solutions and reporting services are running on the application server, and that the report can be run from the server itself. If preview fails on a client, test with a user who has admin rights on that PC to separate permissions from software problems. Check runtime components: matching 32 or 64 bit report runtime, .NET version required by your SYSPRO release, and that client and server are on the same SYSPRO version and patch. Check the database side: the reporting user can read the views and tables the report uses, and the connection settings in the report point to the right company database. Read the SYSPRO and Windows event logs and the e.net diagnostics at the time of the failure, then compare with the release notes and known issues for your version. ## Sections ### e.net business objects as the API **Body:** The e.net Solutions layer exposes SYSPRO functions as business objects. You log on to get a session (GUID), call the object with an XML parameter block and an XML document, then log off. Query objects return data (for example inventory or sales order queries), and transaction objects such as sales order or inventory movement posting change data under the same business rules as the screens. This is what most people mean by the SYSPRO API, including searches such as sypro api or sispro api. Hosting can be via COM, .NET, a web service interface or the REST style services in newer versions. Use the interface your release documents. Always log off, as leaked sessions consume licences and cause logon failures. **Code:** - Typical call pattern (pseudo): - 1. Logon(operator, password, company) -> session id - 2. Query(session id, "INVQRY", xmlIn, xmlParameters) -> xmlOut - 3. Logoff(session id) ### SRS, Crystal Reports and custom reports **Body:** SYSPRO Reporting Services (SRS) is the framework for running and previewing designed reports and operational documents in the application, and it is where server-side reporting runs in recent releases. Crystal Reports has historically been used for designed documents and custom reports, and your SYSPRO 8 version defines which designer and runtime you must use. Check the compatibility notes for your release before you design new reports. For custom reporting that does not need to be part of the application, many companies read from a reporting copy of the SYSPRO SQL database using SQL Server Reporting Services, Power BI or similar, with a read-only account. This avoids load on the live system and lets finance own the reports. ### Why the SRS preview fails: the usual causes **Body:** Most failures are environmental rather than report design problems: the reporting or e.net service is stopped, a runtime bitness mismatch between the report engine and the client, missing or wrong .NET components, firewall or DCOM settings between client and server, an expired or mismatched SYSPRO patch level between server and client, or a database permission that the report user lacks. The report works for one user and not another is a hint for permissions or profile problems. Work methodically: run the same report on the server, then on a clean client, then with an admin user. Change one thing at a time and keep notes. If the problem began after an update, compare the versions and check the vendor release notes and support knowledge base first. ## Pitfalls - Leaving e.net sessions open and exhausting licences. - Writing to SYSPRO tables with SQL instead of using business objects. - Running heavy reports on the live database during peak hours. - Installing a runtime of the wrong bitness on the client. - Fixing the preview on one PC and not documenting the change for others. ## Ai Angle Business users usually want an answer, not a report project. A read-only assistant over SYSPRO data, such as ERPray via e.net queries or a reporting replica, turns questions into queries and shows the SQL or the business object it called. It keeps the reporting load off the live system and runs privately on your servers. ## Faq ### Does SYSPRO have an API? **Answer:** Yes. The e.net Solutions business objects are SYSPRO's integration API. You pass XML parameters and an XML document, and receive XML back, for queries and for posting transactions under SYSPRO business rules. ### What is SRS in SYSPRO? **Answer:** SYSPRO Reporting Services is the reporting framework used to run and preview designed reports and documents. In recent releases it supports server-side reporting. Check the release documentation for its current architecture. ### Why is my SRS preview not working? **Answer:** Typical causes are stopped services, runtime or bitness mismatches, missing .NET components, client and server version mismatch, or database permissions. Test on the server and with an admin user to narrow it down. ### Can I still use Crystal Reports with SYSPRO 8? **Answer:** It depends on your release and the report type. Verify supported designer and runtime versions in the SYSPRO documentation for your version before building or migrating Crystal reports. ## Search terms syspro reporting api, syspro api, syspro e.net business objects, syspro srs preview not working, syspro reporting services, syspro 8 crystal reports, syspro server side reporting, syspro reporting components --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json