Possible Reasons for Required Reboot after Upgrading JAMS


When upgrading JAMS from any version, a reboot may be required after the upgrade if one or more of the following conditions has occurred:

  • A Job was executing at the time of the upgrade
  • Someone is running the JAMS Client on the machine that is being upgrading
  • Someone was in a PowerShell session that had the JAMS Module loaded.

Note: If you are the person running the client or the PowerShell session, Windows Installer will detect that and ask if you want to close the applications. If someone using the JAMS Client is accessing the JAMS Scheduler on the machine that you are upgrading, the machine will not require a reboot. The JAMS Client will stop receiving a response from the JAMS Scheduler.

Have more questions? Submit a request