Running roonserver on Windows Server 2016. Everything was great until sometime within the last 24 hours or so. Now roonserver.exe immediately crashes when I try to run it.
Application: RoonServer.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.TypeLoadException
at Sooloos.App.InitPing()
at Sooloos.App.Init()
at Sooloos.App.Main(System.String[])
I’m completely dead in the water with roon at the moment. When I try to launch it, it immediately terminates. I’m guessing that there must have been an update released within the last day or so because it was working perfectly fine before.
Unfortunately, I can no longer check anything since the roonserver process immediately terminates when I try to run it. Or is it possible to check its version in some other manner?
As it might be caused by Microsoft and it’s automatic updates, it would be helpful if you could provide a list of the updates installed yesterday. I don’t think that the devs are of much help for you as the error looks like a typical .NET error (.NET is a prerequisite for Roon to run correctly, but not provided by Roon) – you may just get the tip to check or reinstall .NET.
Note: Check that .NET 3.5 is installed, this was the last known Microsoft update issue.
As it isn’t a development system, the goal is to have as few runtimes installed as necessary to keep things simple. In this case, the problem wasn’t solved by a newer runtime… I actually had to install an older runtime (3.5) than what was already on the system (4.6).
Interesting, may be worth the upgrade if it impacts Roon Server (I primarily use IOS for Roon clients). I’ll need to poke around the forums to look into that. Thanks for the heads up.
Unfortunately already running the latest .NET framework over here. Also getting the same results, roonserver.exe immediately crashing after trying to start the executable.
Only difference with Stan’s installation is I’m using a Windows 11 desktop as the Roon Server instance. Also tried reinstalling the roonserver btw, but to no avail.
FYI, just downloaded and installed the new Roonserver.exe from Roon, this seems to have solved the issue here