Skip to main content
btan
Staff & Editor
Staff & Editor
Oct 17, 2024 9:35 AM UTC

Troubleshooting Tip: Certain FortiClient EMS services failed to run after EMS upgrade is completed

  • Apr 16, 2026 11:52 AM UTC
  • 0 replies
  • 1034 views
  • Translate All
Description This article describes how to troubleshoot FortiClient EMS fail to run after the EMS version upgrade is completed.
Scope FortiClient EMS 7.0.x and 7.2.x.
Solution

After the FortiClient EMS upgrade is completed, certain FCEMS services fail to run:


oct-portkb2.PNG

 

'Right-click' on FCEMS services and Start: it shows the error 'service cannot be started'.

 

To fix this:

  1. Open Windows Powershell command prompt, run:

    netsh int ipv4 show dynamicport tcp

  2. Check the 'Number of Ports' output:

    Protocol tcp Dynamic Port Range
    ---------------------------------
    Start Port : 49152
    Number of Ports : 255 <--

 

oct-1001.PNG

 

  1. If the 'Number of Ports' is showing very little, for example, 255, this means the network ports are insufficient in this Windows Server.

     

  2. Run the command:

    netsh int ipv4 set dynamicport tcp start=1024 num=64512

     

  3. This will increase the number of Dynamic Ports to the Windows Default value, which will fix the issue:

    PS C:\Users\Administrator> netsh int ipv4 show dynamicport tcp

    Protocol tcp Dynamic Port Range
    ---------------------------------
    Start Port : 1024
    Number of Ports : 64512

    oct-1002.PNG

     

  4. In Task Manager, run the FCEMS services again, they should be able to be up and run now.

Risk and Resilience in the Age of AI. An OT Thought Leadership Summit for Houston's Critical Infrastructure Leaders. Date: Thursday, December 3, 2026. Time: 8:30 am - 1:30 pm (CT). Location: The Westin Houston, Memorial City | 945 Gessner Road, Houston, TX 77024