SOLVED: Strange choice for 10.9.1 making it non-functional in Win Server 2019

[magu2k]

Good day,

I have been using Jellyfin for sometime now, and was pretty excited when I saw today that 10.9 had been released. And it all flew away when I found that it doesn't seem to work on Windows Server 2019.

My current understanding is that it is the service tray, which I typically make use of, to control Jellyfin as a service, requires .net 4.8.1. I can under no circumstances get it to run.
I can run the executable manually, but it is far more convenient as a service for my use, and nothing seems to be loading when I run it and try to access it. 
As far as I can get, so far is to run the executable manually but I am stuck at the server select screen, it just says it's not available. I am not able to discern what part of the settings is causing this, or if there is a setting that can be changed.


This all seems like a very odd choice given the primary functionality added to 4.8.1 was arm64 support. I am guessing however, it's something pertaining to the tooltip features implemented in it, but is there a way we could have an option that works on other operating systems? Currently my perfectly fine and functional install that worked yesterday is dead in the water to myself and all the family/friends that use it.

At this point I see re-installation as a last option. While I like Jellyfin, and there aren't many great alternatives, I'd almost sooner quit the entire "game" than try to do a fresh install on another OS. Jellyfin really sorely lacks any kind of functionality for migrating an install/configuration/layout (anything at all)

[Strongbad]

I am also having the same issue on Server 2019.

[Wey]

Because of that i performed an inPlace upgrade from 2019 to 2022 xD

[stab99z22]

I also ran in to the .Net 4.8.1 problem and did the following as a work around:

I installed the latest stable 10.8.x version of Jellyfin on my Win 10 workstation, and copied the Jellyfin.Windows.Tray.exe and associated files to my Windows server 2019 running 10.9.1. The tray app seems to work fine.

Edit: I can easily zip the files and make them available to you if needed

[magu2k]

I also ran in to the .Net 4.8.1 problem and did the following as a work around:

I installed the latest stable 10.8.x version of Jellyfin on my Win 10 workstation, and copied the Jellyfin.Windows.Tray.exe and associated files to my Windows server 2019 running 10.9.1. The tray app seems to work fine.

Edit: I can easily zip the files and make them available to you if needed

If you can supply me with it, I would really appreciate that, I am hoping to get this running again right away.


And thanks for replying, glad someone found a potential work around right away. I am just wondering if you found running the executable directly vs the service caused issues. Just trying to "scout ahead" a bit to find out what I can expect.

One other quick question, when running the installer to upgrade from 10.8 to 10.9, did you check "install as service" or leave it unchecked? when I did that, it seemed to remove it and I can't really recall the behaviour in prior upgrades

[magu2k]

Because of that i performed an inPlace upgrade from 2019 to 2022 xD

Thanks for that solution I think that might be what I try next should the .exe replacement not work, does it work pretty well at preserving most or everything from the initial install? I kinda like exactly the configuration and everything I have going on the install I have already. I've never actualyl done an in place win server upgrade, only win10/7/etc

[baxtr]

I can verify that the work around that stab99z22 posted does work. As they stated, install the old 10.8.xx file elsewhere, but be sure to copy all 4 files that have the "tray" wording and place them in the new install directory to overwrite. I initially missed one of the files (not sure which) and it did not work but after stab99z22 posted the fix, I did it again and got all 4 files, all is good and working swimmingly on 10.9.1. And I am on WHS 2011

[magu2k]

I can verify that the work around that stab99z22 posted does work.  As they stated, install the old 10.8.xx file elsewhere, but be sure to copy all 4 files that have the "tray" wording and place them in the new install directory to overwrite.  I initially missed one of the files (not sure which) and it did not work but after stab99z22 posted the fix, I did it again and got all 4 files, all is good and working swimmingly on 10.9.1.  And I am on WHS 2011

I did it and seems to be working well, thank you all for the help hopefully anyone else having a similar issue will see this

[mfc2]

I encountered the same error message with the tray app on Windows Server 2012. The workaround of using the four tray files from 10.8.13 seems to work.

[muentzer]

That workaround saved my day! Works fine on Windows Server 2016 Essentials.