moviefan 187 Posted January 2, 2018 Posted January 2, 2018 (edited) I'm not sure how anyone has been successful at using .60. Update fails for me every time and server never starts. Both updating via the WebGUI, as well as shutting down Emby Server and running the installer manually. One time it even deleted my shortcut in the Startup menu which is kind of weird. Keeps just going back to .36 which works fine but tells me to update. Rolling back this update requirement could be prudent. Edited January 2, 2018 by moviefan
Happy2Play 9780 Posted January 2, 2018 Posted January 2, 2018 Not sure if I have no issue since I updated with each version (.36 to .40, .50, .60) and everyone that is having issues is jumping versions. 1
Luke 42077 Posted January 2, 2018 Posted January 2, 2018 Hi, the automatic update issue from 3.2.36 to the latest is unfortunate, but we don't believe there are any issues outside of that. If you're having an issue we're more than happy to help you get squared away. Thanks !
GHynson 9 Posted January 3, 2018 Author Posted January 3, 2018 Not sure if I have no issue since I updated with each version (.36 to .40, .50, .60) and everyone that is having issues is jumping versions. I'm with Happy2Play, I had major issues jumping from .36 to .60 via the update on the Emby server page. I'm up to .60 now with NO ISSUES as of yet after I did the incremental upgrade path I posted earlier. To recap how to recover from a bad .60 upgrade: 1) DO NOT UPGRADE from .36 to .60. 2) If you have, and are having issues, download the .36 build from https://github.com/MediaBrowser/Emby/releases 3) Shutdown the Emby server. 4) Extract the the SYSTEM contents into your Emby server folder. C:\Users\Administrator\AppData\Roaming\Emby-Server (If you went with the default paths) I'm running Emby on a Windows Server 2016 RAID-6 system. 5) Over-write the files if prompted. 6) Start up Emby, it should now state version .36. Check to see if everything is back to working order. 7) Shutdown Emby server. *Repeat steps 2-7, but use the next revision build. Example .40, and then .50* 8) From the .50 build, you can go ahead and do the upgrade via the Emby server panel page. And everything should be working great. At least that's what I did and it fixed all my issues. 2
moviefan 187 Posted January 3, 2018 Posted January 3, 2018 I went through this incremental process and it resolved the issue for me as well. Kind of a pain in the ass but at least it's done. I suggest posting @@GHynson post above as a sticky for a couple of weeks if this isn't going to be fixed in the code. The suggestions provided by staff earlier did not help my issue and just had me wasting my time trying multiple installs.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now