SyteLine SSRS Report Server Setup Checklist

0%

0 of 28 items complete

10 critical items still open - these are the highest-risk gaps.

Download checklist:

Server (SQL Server Reporting Services)

Confirm from the installation guide for your SyteLine release whether standard reports render on the utility server through TaskMan or are published to an SSRS report server, and which SQL Server and Reporting Services versions are supportedCRITICALSSRS edition and version installed match the supported list for the SyteLine release and the SQL Server engine versionReport server database (ReportServer and ReportServerTempDB by default) created in Report Server Configuration Manager and included in the SQL backup planCRITICALSSRS encryption key backed up from Report Server Configuration Manager and the key file and password stored outside the serverCRITICALSSRS service account set to a domain or virtual service account, not a personal loginWeb Service URL and web portal URL reservations configured and tested from the TaskMan (utility) serverHTTPS binding with a valid certificate on the Web Service URL if credentials or report data cross the network

SyteLine side

Utility server hosts TaskMan for this configuration and the TaskMan Reports folder contains the RDL files for the releaseCRITICALReport Options form: output format set for each report that runs in the background (for example PDF or Excel)Document Types form: one entry per Output Format used on Report Options, with the matching file extension, before any TaskPostPerform event handler emails or stores report outputCRITICALTaskMan service account has rights to the report server URL (Browser role or higher on the folders it uses) when a report server is usedPrinters used for report output are installed for the TaskMan service account on the utility server, not only for interactive usersCRITICALIntranets form: report preview and TaskMan related paths for the intranet used by this site checked against the server names (field names vary by release)

Deploy

Standard SyteLine report RDLs deployed exactly as the release or update instructions describe, not copied from another environmentData source credentials stored on the report server or data source, never typed into individual reportsCustom reports kept in a separate folder from Infor-shipped reports so updates do not overwrite themCRITICALCustom report RDLs and their stored procedures held in source control with a version numberFonts used by reports (including barcode fonts) installed on the server that renders the report

Test

Run five representative reports through the background queue: one simple list, one with subreports, one large date range, one barcode label, one emailedCRITICALPreview output in the report viewer from a client workstation, not only on the serverEmail and print outputs arrive with the expected format and file extensionBackground Task History shows each test task completed with no error messageCRITICALReport rendered under a restricted user returns only the data that user's site and groups allow

Operations

SSRS execution log (ExecutionLog3 view in the report server database) reviewed for slow or failed executionsReport execution timeout set high enough for month-end reports but not unlimitedReport snapshots, cached reports and TaskMan output files cleaned up on a scheduleOwner named for report server patching, certificate renewal and encryption key custodyRestore of report server database and encryption key rehearsed on a test serverCRITICAL

Critical items protect report output and recovery. A missing encryption key backup or a printer that only exists for interactive users is the usual reason report output stops after a server rebuild. Score yourself on the critical items first, then the rest.

Get your report server checklist reviewed

Send us your completed checklist and release number and we will point out gaps against your SyteLine version.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use it

Work top to bottom. The Server group is pure Microsoft SSRS configuration and belongs to the DBA; the SyteLine side group belongs to the ERP administrator. Tick an item only when you have seen the evidence: the backup file, the form record, the test output. Export the ticked list to PDF and attach it to the change record so the next rebuild starts from a known state. If a group does not apply, for example because your release renders standard reports locally through TaskMan and you only use a report server for custom reports, mark it reviewed rather than deleting it.

Where this lives in SyteLine

Background reports are queued in Active Background Tasks, picked up by the TaskMan service on the utility server, rendered from RDL definitions and written as files or sent to a printer. Output format per report comes from the Report Options form. If an event handler on the TaskPostPerform framework event emails or stores the output, the Document Types form needs an entry for every Output Format used, with the matching extension (a PDF document type for Acrobat format). The result of each run lands in Background Task History.

Report Options: output format per report
Document Types: required before TaskPostPerform handlers use output
Background Task History: run result and error message
Report Server Configuration Manager: SSRS URLs, database, keys

Version differences and gotchas

How report rendering is split between TaskMan and an SSRS report server has changed across SyteLine releases, and some sites use a report server only for custom or ad hoc reports. Check the installation guide for your exact release before deciding which group of this checklist is mandatory. The most common gotchas are printers installed per user rather than for the TaskMan service account, the SSRS encryption key never backed up, custom RDLs overwritten by an update because they shared a folder with standard reports, and a second TaskMan instance pointing at the same database and consuming tasks.

How to check the result in the system

Submit a report, open Background Task History and confirm the row shows completion with no error text. Open the file in the TaskMan output folder or the emailed attachment and check the extension matches the Document Types entry. On the report server, query the ExecutionLog3 view for the same time window to see render time and status. If History shows completion but no file appears, rule out another TaskMan instance monitoring the same database before anything else.

Frequently Asked Questions

What is the SQL Server report server database?

SSRS stores report definitions, folders, subscriptions, snapshots and execution logs in a SQL Server database, named ReportServer by default, with ReportServerTempDB for session and cache data. It is created from Report Server Configuration Manager. Back it up with your SQL jobs and back up the encryption key separately, because a restored database without its key cannot decrypt stored credentials.

Why does a SyteLine report run but no output arrives?

Check Background Task History first. If it shows completion, look for a second TaskMan instance watching the same database, a printer that is not installed for the TaskMan service account, or a missing Document Types entry when a TaskPostPerform handler emails the file. If there is no history row at all, the task never reached the queue.

Does SyteLine need a full SSRS report server?

It depends on the release and on how you run custom reports. Standard background reports are produced by TaskMan on the utility server from RDL files, while some sites also publish custom or ad hoc reports to an SSRS report server. Confirm the supported layout in the installation guide for your release rather than assuming one model.

Where do I set the report output format in SyteLine?

The Report Options form holds the output format for each report that runs in the background, such as PDF or Excel. If you change formats and an event handler sends the output by email, add or update the matching Document Types entry with the right extension, otherwise the TaskPostPerform handler cannot attach the file correctly.

If you want your team to ask SyteLine for report data in plain English on your own servers, without waiting on the background queue, we can set that up.

Talk to an Expert Explore More Free Tools

Related Tools

Infor SyteLine

More Infor SyteLine tools

See all