Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Firewall Security Manager (FSM) > Scheduled tasks take too long to complete or crash the FSM client

Scheduled tasks take too long to complete or crash the FSM client

Table of contents
No headers

Scheduled tasks, such as running batch reports, take too long to complete or crash the FSM client. This is a known issue and we are investigating a permanent fix for a future release.

Complete the following procedure to update applicationContext.xml and resolve this issue.

To fix update applicationContext.xml

  1. Close the FSM client.
  2. Backup the user workspace to a temporary location, and then remove the original user workspace. The user workspace folder is found in the following location, depending on the type of FSM installation:
    • For FSM 6.4 servers:
      homeDirectory\SolarWinds\SolarWinds FSM Server\workspace\
    • For FSM 6.4 remote clients:
      homeDirectory\SolarWinds\SolarWinds FSM\workspace\
    • For FSM 6.3.x servers:
      homeDirectory\SolarWinds\AthenaFirePAC Server\workspace\
    • For FSM 6.3.x remote clients:
    • For Windows Vista, Windows 7, and Windows 2008:
    • For Windows XP and Windows Server 2003:
      C:\Documents and Settings\userName
  3. where homeDirectory is:
  4. Backup the applicationContext.xml file to a temporary folder. The file is found in the following location, depending on the type of FSM installation: fsmInstallationFolder/dbconfig/applicationContext.xml, where fsmInstallationFolder is:
    • For FSM 6.4 servers:
      C:\Program Files\SolarWinds\SolarWinds FSMServer\dbconfig\applicationContext.xml
    • For FSM 6.4 remote clients:
      C:\Program Files\SolarWinds\SolarWinds FSMClient\dbconfig\applicationContext.xml
    • For FSM 6.3.x servers:
      C:\Program Files\SolarWinds\AthenaFirePACServer\dbconfig\applicationContext.xml
    • For FSM 6.3.x remote clients:
      C:\Program Files\SolarWinds\AthenaFirePACClient\dbconfig\applicationContext.xml
    • For FSM servers upgraded from earlier FirePAC versions:
      C:\Program Files\AthenaSecurity\AthenaFirePACServer\dbconfig\applicationContext.xml
    • For FSM remote clients upgraded from earlier FirePAC versions:
      C:\Program Files\AthenaSecurity\AthenaFirePACClient\dbconfig\applicationContext.xml
  5. Open Notepad as administrator: Right-click Notepad in the "Accessories" program group, and then select Run as administrator.
    Note: This part of the procedure requires administrator permissions to work.
  6. In Notepad, open ~/dbconfig/applicationContext.xml from the installation folder noted in Step 3.
  7. In applicationContext.xml, find the 2 lines that contain isRuleDocAlreadyExists, and then add the following line above each line:
    <prop key="getRulesCount">PROPAGATION_REQUIRED, ISOLATION_REPEATABLE_READ, readOnly, -Exception</prop>
  8. Save and close the file.
  9. Open the FSM client.
  10. Create the scheduled tasks and check to ensure they run appropriately as scheduled.
Last modified
14:58, 13 Nov 2015