# SyteLine TaskMan and Background Task Troubleshooting Checklist > Source: https://netray.co/tools/syteline-taskman-background-task-troubleshooting-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Step-by-step checks for background reports and utilities that sit in the queue, fail, or produce no output in SyteLine 9 and CSI 10 on-prem. ## Category syteline ## Erp Infor SyteLine ## Audience - ERP administrator - SyteLine support analyst - SQL Server DBA ## Tool **Kind:** checklist **Groups:** #### Service **Items:** **Text:** TaskMan service is running on the utility server and set to start automatically **Critical:** true TaskMan is defined in Service Configuration Manager for the configuration (database) you are troubleshooting **Text:** Only one TaskMan instance monitors this database; a second instance will consume tasks and write output elsewhere **Critical:** true TaskMan service account has rights to the output folders, report location and any report server it calls Printers the report uses are installed for the TaskMan service account on the utility server #### Queue **Items:** **Text:** Task is visible in Active Background Tasks (ActiveBGTasks table) **Critical:** true Note the age of the oldest queued task; if everything is waiting, the problem is the service, not the report Look for duplicate submissions of the same report by impatient users Check whether a long-running utility ahead in the queue is holding it up #### History **Items:** **Text:** Background Task History has a row for the submission **Critical:** true No history row: the trigger on ActiveBGTasks did not create one, so the task never reached the queue (a form submission problem) or TaskMan never picked it up Return status checked (0 normally means success) and the error message text read in full Start and end times compared with the normal run time for that report #### Report specifics **Items:** Report Options output format is set and valid for that report Report files for the release are present where TaskMan expects them Report server reachable from the utility server if your setup uses one **Text:** Document Types entry exists for the output format if a TaskPostPerform handler emails or stores the output **Critical:** true Output file appears in the TaskMan output folder when the history row says completed #### Logs **Items:** LogMonitor running on the utility server while you resubmit the task Windows Application event log on the utility server checked for TaskMan and .NET errors at the run time Event Status checked if event handlers run on TaskOnPerform, TaskPostPerform or TaskOnPerformFailed #### Data and SQL **Items:** Identify the stored procedure behind the task and run it in a test database with the same parameters **Text:** Check for blocking while the task runs (sys.dm_exec_requests blocking_session_id) and find the head blocker **Critical:** true Check statistics and index maintenance on the tables the procedure reads If the task is a utility that updates data, confirm it did not partially commit before rerunning **Scoring Note:** Work the groups in order and stop when you find the cause. The two questions that split almost every case are: is there a row in Background Task History, and is only one TaskMan watching this database. ## Content **Intro:** This checklist isolates why a SyteLine 9 or CSI 10 on-prem report or utility is stuck in the queue, fails, or completes with no output. It follows the path a task takes: submission, Active Background Tasks, TaskMan, rendering, output and history. **Sections:** #### How to use it **Body:** Resubmit the failing task once with LogMonitor open, then walk the groups in order. Each group answers one question: is the service up, did the task enter the queue, did TaskMan record a result, did the report render, what do the logs say, and is SQL the bottleneck. Stop at the first group that explains the symptom. Export the ticked list with your notes and attach it to the support ticket so the next person sees what was already ruled out. #### Where this lives in SyteLine **Body:** Submitting a report writes a row to ActiveBGTasks, which TaskMan polls. A trigger on ActiveBGTasks creates the Background Task History record, so a task that runs but has no history row points to a submission problem in the form rather than a TaskMan fault. TaskMan runs the task, renders the report and records the result. Task framework events (TaskOnPerform, TaskPostPerform, TaskOnPerformFailed) let handlers act on outcomes, such as emailing the output. **Bullets:** - Active Background Tasks: the live queue - Background Task History: result, return status, error text - Service Configuration Manager: TaskMan configuration - LogMonitor: live runtime messages #### Worked example **Body:** Users report that the daily shipping report shows completed but nobody gets the PDF. History shows completion with no error. The output folder has no new file. Stopping the TaskMan service and resubmitting still updates history, which proves another TaskMan instance on an old utility server is watching the same database. Disabling that instance fixes it. A second site has a different cause: the PDF exists but the email never goes, because the format on Report Options was changed to Excel and no matching Document Types entry existed for the TaskPostPerform handler. #### Common mistakes **Body:** Restarting TaskMan repeatedly without reading the error message in history. Installing printers for an administrator login instead of the service account. Rerunning a data utility that partly committed. Treating every slow report as a TaskMan problem when SQL blocking is holding the stored procedure. Forgetting that old utility servers left running after a migration can still poll the database. **Cta:** If your team spends time chasing report output, we can put a private AI assistant on your own servers that answers the same questions from SyteLine data directly. **Faq:** #### How do I run a report in SyteLine? **Answer:** Open the report form, fill in the parameters and choose Print, Preview or the background option your form offers. The request is queued in Active Background Tasks and TaskMan on the utility server runs it. Check the result in Background Task History, where completion, return status and any error message are recorded. #### Why does my SyteLine report stay in the queue? **Answer:** Usually the TaskMan service is stopped, is configured for another database in Service Configuration Manager, or is busy with a long task ahead of yours. Check the age of the oldest queued task in Active Background Tasks. If every task is waiting, fix the service; if only yours is, look at that task's data and SQL blocking. #### What does it mean when there is no Background Task History record? **Answer:** History rows are created by a trigger on ActiveBGTasks. If a task appears to run but leaves no history row, Infor documentation for on-prem environments points at the order of form events used when the form submitted the task, so the task never reached the queue as expected. Check the form customization before TaskMan. #### Which form shows printers in SyteLine? **Answer:** Printer names available to background reports are the Windows printers installed for the TaskMan service account on the utility server, so start by checking that account's printers on that server. The exact SyteLine form used to pick printers varies by release, so confirm it in your release help before documenting it for users. ## Search terms how to run a report in syteline, syteline report, syteline report viewer, syteline taskman, syteline background task history, syteline report not printing, syteline active background tasks --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json