How to Disable CM Mass Process When Full Client is Inaccessible

Owned by Knowledge Assistant
Last updated: Jul 24, 2024 by Moriah Yorkey
1 min read
Description of Issue

After an upgrade, the Content Manager (CM) full client fails to load. Apache service is using a lot of memory. Attempting to restart the Apache service fails to fix the issue, as the service is consuming a large amount of CPU.

Context

  • Tyler Content Manager

  • Content Manager

  • CM

  • TCM

  • SaaS

  • On-Premises

Cause

After a version upgrade, CM can automatically queue up certain Mass Process jobs. As a result, this can cause CM to consume system resources - potentially rendering the application unusable for hours.

Resolution

  1. Log in, and connect, to the SSMS instance on the database server that holds the CM database

  2. Expand the CM database > Tables

  3. Scroll down and right click on the MassProcessStartAndRunTime table

    1. Select Edit Top 200 Rows

  4. Find the row for the Mass Process that needs to be stopped based on the ProcessID column and value within the DayOfWeekInt column (e.g., Sunday = 1, Monday = 2, etc.)

  5. Set the RunHours and RunMinutes values to 0 for the row

  6. Press Enter to commit the changes

  7. Restart the Apache Tomcat service

Additional Information

See Restarting Apache Tomcat Services for additional information on rebooting a site's service(s). 

SaaS Clients: Reach out to EERP TSM SaaS for assistance.

Â