Skip to main content
Solved

Licensing Manager init FAILED

  • May 13, 2026
  • 3 replies
  • 104 views
janet
Contributor

I was looking to upgrade FME Flow 2024 to FME Flow 2026 and ended up getting an impassable situation. I was following this process, which I’ve done in previous upgrades (ie. to version 2024):

https://docs.safe.com/fme/html/FME-Flow/AdminGuide/Upgrade-in-Place-Same-Machine.htm - I am stuck after step #4.

 

Here are my specific steps:

  1. Uninstall FME Flow 2024 from Add or Remove Programs
  2. Run FME Flow 2026.1.1, using Express install
  3. Open http://<host>/fmeserver/ -> “ERR_CONNECTION_REFUSED”

From fmeserver.log:

INFORM   main   401970 : FME Flow is not licensed for this machine. For assistance, contact sales@safe.com or your local Safe Software reseller. (-1)

INFORM   main   401972 : Total number of available engines is 0

INFORM   main   401961 : Licensing Manager init FAILED

INFORM   requesthandler   401831 : Accepted new engine connection from /127.0.0.1 on port 7070

INFORM   fme-engine-registration-1   401937 : Accepted new FME Engine connection.

INFORM   fme-engine-registration-1   401950 : Registering FME Engine...

ERROR    fme-engine-registration-1   401979 : Missing FME Flow license, or license disallows FME Engine registration.

ERROR    fme-engine-registration-1   401939 : Failed to register FME Engine.

 

On repeat

 

It’s not possible to check on the licensing from the web console because that won’t start up. Manually adding a newly generated .fmelic file from the Sales team to the licenses folder didn’t help: C:\ProgramData\Safe Software\FMEFlow\licenses\

I uninstalled 2026, reinstalled 2024 and it produced the same error, so now it’s a persistent problem.

I’m attaching the Tomcat logs from the new 2024 install.

Would anyone know why the licensing isn’t starting up? 

 

Best answer by janet

This issue has been resolved.

The problem stemmed from port 80 being unknowingly disabled by IT, and resolved by reinstalling with a newly created certificate (enabled HTTPS).

 

    3 replies

    crystalatsafe
    Safer
    Forum|alt.badge.img+30

    Hi ​@janet 

    I'm sorry to hear you are experiencing this issue!

    Can you please submit a support ticket with us: https://support.safe.com/hc/en-us/p/Support

    janet
    Contributor
    • janetContributor
    • Author
    • May 15, 2026

    Hi Crystal, I actually have 2 tickets going that haven’t been helpful or timely so I thought I’d try the Community. #65292, #65283

    janet
    Contributor
    • janetContributor
    • Author
    • Best Answer
    • May 23, 2026

    This issue has been resolved.

    The problem stemmed from port 80 being unknowingly disabled by IT, and resolved by reinstalling with a newly created certificate (enabled HTTPS).

     

    Community Stats

    32,623
    Posts
    123,821
    Replies
    40,991
    Members
    Terms & ConditionsAccessibility statement
    A product of
    Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.