SyteLine TaskMan Troubleshooting Checklist

0%

0 of 25 items complete

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

Download checklist:

Service

TaskMan service is running on the utility server and set to start automaticallyCRITICALTaskMan is defined in Service Configuration Manager for the configuration (database) you are troubleshootingOnly one TaskMan instance monitors this database; a second instance will consume tasks and write output elsewhereCRITICALTaskMan service account has rights to the output folders, report location and any report server it callsPrinters the report uses are installed for the TaskMan service account on the utility server

Queue

Task is visible in Active Background Tasks (ActiveBGTasks table)CRITICALNote the age of the oldest queued task; if everything is waiting, the problem is the service, not the reportLook for duplicate submissions of the same report by impatient usersCheck whether a long-running utility ahead in the queue is holding it up

History

Background Task History has a row for the submissionCRITICALNo 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 upReturn status checked (0 normally means success) and the error message text read in fullStart and end times compared with the normal run time for that report

Report specifics

Report Options output format is set and valid for that reportReport files for the release are present where TaskMan expects themReport server reachable from the utility server if your setup uses oneDocument Types entry exists for the output format if a TaskPostPerform handler emails or stores the outputCRITICALOutput file appears in the TaskMan output folder when the history row says completed

Logs

LogMonitor running on the utility server while you resubmit the taskWindows Application event log on the utility server checked for TaskMan and .NET errors at the run timeEvent Status checked if event handlers run on TaskOnPerform, TaskPostPerform or TaskOnPerformFailed

Data and SQL

Identify the stored procedure behind the task and run it in a test database with the same parametersCheck for blocking while the task runs (sys.dm_exec_requests blocking_session_id) and find the head blockerCRITICALCheck statistics and index maintenance on the tables the procedure readsIf the task is a utility that updates data, confirm it did not partially commit before rerunning

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.

Stuck on a background task?

Send us the Background Task History error text and your release and we will tell you where to look next.

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

Was this tool useful?

How to use it

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

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.

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

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

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.

Frequently Asked Questions

How do I run a report in SyteLine?

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?

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?

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?

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.

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.

Talk to an Expert Explore More Free Tools

Related Tools

Infor SyteLine

More Infor SyteLine tools

See all

SyteLine TaskMan and Background Task Troubleshooting Checklist