3.4.1->3.5.2 : Problems after upgrade

[ryandavidg 30]

I have an old Win 7 machine which, although very underpowered for most uses these days, has worked fine as a dedicated server just for my music collection. I tend to upgrade it first to see if there are any problems before I upgrade the main server on another machine. It was working perfectly before the update and now I can't get it to work, despite varied efforts over the last few days.

 

Background: Windows 7 machine (x86, sp1, all Windows updates current). Music collection consisting of various libraries like Classical, Jazz, Electronic, Metal, etc. Automatic monitoring of libraries off, images and metadata saved in media folders.

 

Issues:

- Since the update the server is inaccessible from other devices on local network (just times out, although then hitting 'home' on the browser app does provide a top level view of the libraries) and the section with the IP addresses and server version is missing from the server dashboard viewed on the server machine/localhost (see below)

 

 

- Check for application updates never completes

- Library scans never complete, even though I left one for more than a day

 

Steps to resolve:

- Rebooted machine and restarted - no change

- Rebooted then reinstalled Emby over the top from website- no change

- Looked through release notes and noted the move to netcore 2.1.2 so tried installing that - no change

 

There is no blog entry for this release to tell us about major changes/potential problems, but after spending a long time looking through other threads it seems there are various issues people have encountered like "removed theaudiodb in 3.5.2", "remove gamebrowser.dll to resolve crashes" and "new logic in library scans". I don't really use any plugins on this server, tried removing the reports plugin (it was dated May) but this didn't help.

 

I have now tried a portable install on this machine and it is working perfectly so I guess I will rebuild everything with this portable install now. But I thought I'd let you know about the problems I had in case others run into the same thing. Should also note that the setup wizard for the server has audiodb options ticked by default and I unticked them all to avoid problems - not sure if this is really removed but it was noted in another thread where someone had crashes and had to rebuild their library.

 

Finally, I have read the "how to report a problem" instructions and can upload logs if they will be of any use. But I wanted to first check on who will have access to them if I upload them here as this wasn't mentioned in those instructions. If I attach a log here will it only be accessible by devs/admins, or do I need to go through it first to sanitise it and avoid any IP and other info being posted in public?

 

Thanks.

[ebr 16169]

Hi.  This looks like a firewall or other network issue.  First check your firewall settings and make sure there are no blocking rules for Emby.  Also, if you have other anti-malware check that.

 

Many times (especially in Win 7 I think) updating an application will mess up the firewall settings for it.

[ryandavidg 30]

Hi - I checked the firewall rules and they were fine, and matched those for the portable version which works fine. In terms of antivirus, because I only use this machine as a music server it only has MS security essentials on it. What's strange though is that today I checked the original non-portable install a final time (after rebooting the machine so the other version wasn't running) and it worked fine, even completed a full library scan and is visible to all devices. Not sure why setting up a portable install would have fixed anything but at least it's working again. Still have the issue with shutdown not ending the embyserver process in 3.5.2, and needing to reboot the machine to end it - as described by someone else in the below thread but that's not major issue for me:

https://emby.media/community/index.php?/topic/61332-emby-server-crashing-after-a-few-minuites-eachtime-after-opening/

 

After reading about the database improvements coming in 3.6 for fresh installs I guess that will be a good time to move to the portable version for good and rebuild the libraries then.

 

Thanks for your time.