My sad error installing on Windows Server 2022

It’s been a while since I’ve dealt with a Windows server. But we needed to upgrade a very delicate and large secured document server from ye ol’ FMS18 to 22(2025). So a new server was created, a copy of the data drive was attached and It works just fine. Yay.

Unfortunately, upon installing Otto, I’m getting errors Starting with “Problem running post-install step. Installation may not complete Correctly…”

Then I check the running services (based on a comment I read here) and lo and behold, the OttoFMS service was “Paused.” But It would not resume. I get the message “Windows could not resume the OttoFMS service on the Local Computer. This service did not return an error…”

This is a fresh install, so maybe there is some conflict. Also this machine does not yet have its final FQDN attached to it, but I would still think that I could get it installed.

Of course this is a machine that is in a protected network so once I get to the log in page for Otto, I’ll need to request a license key for it.

Hey Fred,

It maybe that antivirus is trashing or blocking nssm.exe from running. Look for suspicious logs in the service events.

Let us know what you find.

Todd

Hey Fred,

We also had a different report of OttoFMS failing to start with a fresh install of 4.13.0, if you install 4.12.0 instead does it work?

-Kyle

Hey Fred,

I’ve just confirmed there is an issue with 4.13.0 and new installs not working. Installing 4.12.0 and upgrading to 4.13.0 should work. I’ll have 4.13.1 released today or tomorrow that fixes the issue.

-Kyle

OK that did it. I found another bug.

Hey Fred,

OttoFMS 4.13.1 was just released which should fix this issue. Thanks for the report!

-Kyle

ok, I’m on a Windows Server 2022, with 4.13.1 and I’m still getting the error. If I manually try to start ottofms-win-x64.exe

I get and error about it not being found or don’t have permissions. Something still doesn’t seem to be working.

Hey @Egon ,

If you go to the service management screen on the windows server does OttoFMS appear in the list? At which point in the install process does it fail? Did you try installing with the Powershell command as administrator and it still failed? What is the exact text of the error message?

-Kyle

It does not.

I haven’t tried installing via power shells, just right clicked and “Run as administrator” I got the error on installing and then got another one when trying to manually start.

Can you send a screenshot of the error?

-Kyle

This may be a threat locker issue. Let me dig in to that and get back to you.

1 Like

ok, so the last part was caused by TreatLocker, Got around that, but how when I go to put in the license it just tells me it Reason: “Missing”

Hey @Egon ,

If you open up the OttoFMS logs do you see any errors? normally that license issue means there was an error reading or writing to the filesystem.

-Kyle

This is what the logs say

2025-10-16T12:40:23.646Z	error	Error checking license read ECONNRESET
2025-10-16T12:52:20.232Z	error	Error checking license getaddrinfo ENOTFOUND edd-sl-proxy.geistgate.com

I can ping that address from the server

Does this mean anything to you?

Hey @Egon ,

The ECONNRESET and ENOTFOUND errors are network/DNS errors that mean something is up with your network connection to edd-sl-proxy.geistgate.com. If you’re seeing those I would not expect you to be able to ping the proxy, but is sounds like you can?

-Kyle

yeah, I can ping them from every server, which I also thought was odd.

I’m getting a return IP of: 146.112.61.106 when I ping edd-sl-proxy.geistgate.com

Strange, seems like it should be working. I would recommend you stop by office hours for us to take a look with you so we can do some realtime troubleshooting.

I’m going to try to get some time with our networking guys, something is still being blocked at the protocol level I think