Skip to main content

SQL Agent & FeneVision Agent Jobs

Lynne Whitmore
  • Updated

This article explains what the SQL Agent and FeneVision Agent jobs do, with tips for troubleshooting stopped jobs and common job errors.  Some SQL Agent jobs and FeneVision Agent jobs only appear in more recent versions of FeneVision, so they might not exist in your version.

SQL Agent Jobs

  • Database Maintenance Jobs
    • Nightly - Performs cleanup tasks, database integrity check, verifies correct database settings and creates database backups.  This job is critical to verify the health of the databases and provide backups, to ensure your plant operations continue to run smoothly.
    • Throughout the Day - These are incremental backups that can be merged with the nightly backup, to get the most up to date data.  This is often disabled, due to lack of ability of many IT departments to perform the merge.
    • Weekly - Typically set to run on the weekend at a time when the system is less busy.  Performs index optimization on tables to safeguard database performance/speed.  This is a critical job.
  • Performance Monitor Jobs - these jobs gather performance and error data, to aid in solving performance issues.
  • Poller Jobs - periodically check for specific conditions or data changes, allowing for automated actions to be triggered based on these detected changes.
    • Scheduler Poller - Populates data needed in the Scheduling module, such as line item options and exceptions, work cells, and purchased quantities.
      • If you do not see the new order/item you are looking for in Scheduler, try the refresh icon in Scheduler.
      • If new order/items continue to be absent from Route Builder, check the status of the Scheduler Poller job.
    • Completion Poller - Responsible for updating completion for capacity and shipping.  Various actions can cause a unit to complete, shipping, order closed, accepting a part at its last work cell.
    • Inventory Poller - Responsible for updating inventory quantities, including Quantity On Sales Order.
    • Route Builder Poller - Gathers data for the top grid in Route Builder.
      • If you do not see the order/item you are looking for in Route Builder, try the refresh icon in Route Builder.
      • If new order/items continue to be absent from Route Builder, check the status of the Route Builder Poller job.
  • Monitor Jobs
    • eServer Monitor - Detects overdue eServer requests and emails operator.
    • Accounting Monitor - Detects timed out accounting requests.  If a timed out request is found, the operator will be emailed.
    • Reject Monitor - In versions 11.4 and earlier.  Processes rejected items, moving them to the Opti Remakes queue or the FeneVision Core Remake queue as designated by the configuration.

Determining if a SQL Job is Successful

On the FeneVision database server, open SQL Server Management Studio, and expand the SQL Server Agent and then Jobs nodes.  Right Click on the job and select View History.  If a green checkmark appears by the last run, it was successful.  If not, then the Message field in the log history will provide more information.

Additional Method for Determining if Weekly Maintenance Job Ran

This is helpful for those situations where the SQL Server Management Studio history is not showing anything for this job.  Run a SQL Query against the master database in SQL Server Management Studio.  This is an example for the "FeneVision Database Maintenance - Weekly" job.  Be sure to correct StartTime values to recent dates for the past weekend!
 

SELECT StartTime, DatabaseName, ObjectName, IndexName, 
DATEDIFF(MILLISECOND, StartTime, EndTime) As Duration, Command FROM CommandLog 
WHERE Command like '%REBUILD%' 
AND StartTime >= '2025-07-18 01:00:00.000' AND StartTime <= '2025-07-21 05:00:00.000' 
ORDER BY Duration

This query will show you each index rebuild operation that occurred.  It also tells you how long the index took to rebuild. 

FeneVision Agent Jobs 

The AgentJobs table is found in the FVMaster database prior to version 12.2, and the FVPerformance database afterwards. 

The Enabled field of this table is set to 1 if the job is enabled, 0 if it is disabled. 

The FeneVision Agent service must be running so that the following jobs will run. Check the status of FeneVision Agent in Windows Administrative Tools - Services.

  • Activation Job - Runs periodically.  Used to activate new modules and server (extend FeneVision license).
  • Accounting Poller - Automatically runs accounting tasks that are configured for automatic syncing.
  • Reject Monitor - Moved to FeneVision Agent Job in versions after 11.4.  Processes rejected items, routing them to the Opti Remakes queue or the FeneVision Core Remake queue as designated by the configuration.
  • Performance Monitor - return performance and error data to a FeneVision server off site, to aid in solving performance issues.

Determining if a FeneVision Agent Job is Running and Successful

  • Check Event Viewer on the database server for errors from the FeneVision Agent service.
  • The AgentJobHistory in the FVPerformance database can be queried to see more details.  If the Status field = 1, then the job was successful.  If the Status field is not 1, then the job was not successful and the cause listed in the Message field.  Then query below selects the 50 most recent records in the AgentJobHistory table for the FeneVision Reject Monitor job, run the query against FVPerformance.
SELECT TOP 50 * FROM AgentJobHistory 
WHERE JobName = 'FeneVision Reject Monitor'
ORDER BY StartDateTime DESC

Known Tips and Issues

  • Ensure any copies of the FV databases do not include the letters "FV" (like "MyFVMasterTest"). That causes them to be picked up by the nightly maintenance plan, which causes the plan to fail when there's no corresponding FVWarehouse database.
    • Name them something else, like "MyFenMasterTest"
  • The SQL Server Agent service must be running in order for the FeneVision SQL Agent jobs to run.  Check the status of SQL Server Agent in Windows Administrative Tools - Services.
  • The FeneVision Agent service must be running so that the FeneVision Agent Jobs can run.  Check the status of FeneVision Agent in Windows Administrative Tools - Services.
  • If a FeneVision Agent job is not executing and the FeneVision Agent service is running, verify the job's Enabled field is 1 in the AgentJobs table in FVPerformance.  Verify the NextRunDateTime is not in the past, if it is in the past, update NextRunDateTime to a future date and time.
  • Database Mail Setup - the jobs will send an email upon failure.  This notification is often critical, especially for the Database Maintenance Jobs.  If the person responsible changes, then the new email must be setup.  See SQL Database Mail for more information. 

Related articles