Restart Scheduler OnPrem

All Munis Scheduler jobs are not running. The Scheduler status may be Waiting to Exit, Shutdown, Paused, or Online. 

If the Scheduler status is Online and other jobs are running successfully, please contact the appropriate Software Support team for individual job failures.

• Munis Scheduler

• Scheduler

• Scheduler Engine

The Scheduler Engine or Scheduler Service needs to be restarted

Prior to restarting the Scheduler, review pending jobs

1. Log into the affected environment with an administrative account

2. Open Tyler Menu and navigate to System Administration > Scheduler Administration > Scheduler Queue

3. Select the job you wish to delete

   1. Jobs scheduled for dates/times prior to when you are restarting the Scheduler typically should be deleted. If they are not deleted, they will attempt to run once the Scheduler is online.

   2. Jobs stuck running for more than 2 days should be deleted

   3. Only delete a single instance instead of the entire job, unless instructed by Munis support or if you wish to recreate the job entirely

4. Select Job in the ribbon

5. Select Delete

   1. If the Job is running you may receive an additional prompt. Click Continue

   2. Click Single Instance

6. Repeat for all jobs necessary

Version 2019+ deployed via Tyler Deploy

• This Scheduler is environment specific and will be listening on a port defined during a Munis ERP update

Scheduler status is Shutdown, Waiting to Exit, or Online and no jobs are running:

1. Review pending jobs via the Scheduler Queue prior to restarting the Scheduler

2. Log into the Application Server with tylerservice or an administrative account

3. Open Services (services.msc)

4. Locate Munis Scheduler Monitor [env], Port=xxxx

   1. If the service Startup Type is Disabled, please see How to Enable Scheduler Monitor Service From Tyler Deploy

   2. If the service is not running, proceed to next step

   3. If the service is running, right click on the service name and click Stop

5. Launch SQL Server Management Studio (SSMS)

6. Right click on the Munis database in question and select New Query

7. Run the following to force the scheduler engine into a Shutdown state

   1. UPDATE skedecfg

      SET skec_mode_current='Shutdown'

8. Return to Services > Munis Scheduler Monitor [env], right click on the service name and click Start

9. After a few minutes, the Scheduler status should be Online in the Scheduler Queue

   1. To update the status in the Scheduler Queue select View > Refresh

Scheduler status is Paused or Paused Indefinitely:

1. Review past due jobs and delete as necessary

2. In the top left corner, select Scheduler > Resume

   1. To update the status in the Scheduler Queue select View > Refresh

3. Review Scheduler Engine Properties by selecting Scheduler > Properties

   1. Note: This requires Scheduler Engine Administrator Permissions

4. Check if Initial engine startup mode is set to Online

   1. If it is set to Paused, change to Online and review Scheduler Engine Configuration

Version 2017, 2018, 11.3, and earlier; Version 2019 deployed without Tyler Deploy

1. Log into the Application Server with tylerservice or an administrative account

2. Launch MunisSchedulerMgr.exe

3. Select File > Open

   1. Browse to C:\Users\tylerservice\AppData\Roaming\Munis\MunisScheduler

   2. Select Config.xml

   3. Select Open

4. Verify all connections pass by selecting Test Connection for each environment

5. Select Stop and wait for the box to display Stopped

   1. This should stop the Windows Service Munis Scheduler Monitor

6. Launch Task Manger

   1. Click the Details tab and end any gdc.exe processes

   2. Right click on gdc.exe > End Task

   3. Do you want to end gdc.exe? > Click End process

7. Launch SQL Server Management Studio (SSMS)

8. Run the following query against all environments that exist in the Munis Scheduler Monitor Manager

   1. Right click > New Query

   2. UPDATE skedecfg

      SET skec_mode_current='Shutdown'

9. Ensure there is no GDC.exe running in the system tray on the Windows toolbar

10. On the server desktop, double click the Scheduler shortcut

    1. The GDC scheduler should now be running on port 6499

11. Return to MunisSchedulerMgr.exe and click Start

12. The Scheduler Engine for each environment will now open 

    1. Note: Depending on how many environments are configured, the engines could take up to 20 minutes to open

13. One the Scheduler Engine opens, quickly select Pause Engine

    1. Select Indefinitely

14. If not already done, review pending jobs and delete as necessary (see above)

15. Once all jobs have reviewed, click Resume Engine and close the engine window

16. Go to the system tray, select the GDC icon > right click > Quit

17. After a few minutes, the Scheduler status will be Online in the Scheduler Queue in Munis

    1. Run the following SQL query against an environment to obtain the current status

       1. SELECT skec_engine, skec_mode_current FROM skedecfg

• Run the following SQL query against an environment to obtain the current status

  • SELECT skec_engine, skec_mode_current FROM skedecfg

• To test Scheduler functionality, run an Invoice Aging Report at a scheduled time

  • From the menu, open Invoice Aging Report (Financials > Accounts Payable > Invoice Inquiry and Reports > Invoice Aging Report)

  • Click Define

  • Change Execute this report to At a scheduled time

  • Click Accept

  • Select time to run. For testing purposes, schedule it a few minutes out.

  • Click OK

  • Click OK to schedule this job

• If the Munis Scheduler Monitor service is not starting up on it's own after a server reboot, change the service startup type to Automatic (Delayed Start) 

  • Right click on the service name

  • Select Properties

  • Change Startup type to Automatic (Delayed Start)

  • Click Apply

  • Click OK