Skip to main content
Solved

Java error after new install of 2022.0 ?

  • May 31, 2022
  • 2 replies
  • 44 views
lifalin2016
Supporter
Forum|alt.badge.img+38

Hi.

I've just finished a new install of FME Server 2022.0.0.2 on Windows Server 2019, and when I browse the management webinterface, I get the ugly Java exceptions below. Either one shows up when I refresh.

What is causing this ? Looks like a Tomcat issue, but how to fix that ?

error 500error 404I've made some small modifications post-install (not Tomcat), but all 4 services are up and running.

Cheers

Best answer by hkingsbury

I'm no tomcat or java expert, but the line 'no output folder' suggests the the account running the FME Server Services might not have sufficient read/write access to the install location and share resources location

-- Cheers, Lars I.
    This post is closed to further activity.
    It may be an old question, an answered question, an implemented idea, or a notification-only post.
    Please check post dates before relying on any information in a question or answer.
    For follow-up or related questions, please post a new question or idea.
    If there is a genuine update to be made, please contact us and request that the post is reopened.

    2 replies

    hkingsbury
    Celebrity
    Forum|alt.badge.img+63
    • hkingsburyCelebrity
    • Celebrity
    • 1632 replies
    • Best Answer
    • May 31, 2022

    I'm no tomcat or java expert, but the line 'no output folder' suggests the the account running the FME Server Services might not have sufficient read/write access to the install location and share resources location

    lifalin2016
    Supporter
    Forum|alt.badge.img+38
    • lifalin2016Supporter
    • Author
    • Supporter
    • 592 replies
    • June 1, 2022

    I'm no tomcat or java expert, but the line 'no output folder' suggests the the account running the FME Server Services might not have sufficient read/write access to the install location and share resources location

    Thanks @hkingsbury​ 

    Actually it was just one of two mistakes, or rather forgotten steps.

    I have done this exercise before, and did document the necessary steps at the time, but that documentation apparently has been lost (can't find it), so I'm retracing my steps.

    The two steps I forgot was:

    1. Adding the AD account to the local Administrators group - which your suggestion pointed at
    2. Deleting all engine logs from the old account (C:\\ProgramData\\Safe Software\\FME Server\\resources\\logs\\engine)

    When both steps was taken care of, the web interface started as expected.

    So again, thanks for pointing me in the right direction 🙂

    Cheers.

    -- Cheers, Lars I.

    Community Stats

    32,106
    Posts
    121,903
    Replies
    39,752
    Members

    Latest FME

    Terms & ConditionsCookie settingsAccessibility 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.