Library Scanning in 3.2.60.0

[WhackOBill 8]

I moved from 3.2.34.0 to 3.2.60.0 today by doing the manual install method as suggested.  I also put in a new CPU going from an i3-3225 to an i5-3470S.

 

The library scans no longer work, nor does the scan on change mechanism.  When I manually attempt to scan all libraries, I get this in the log ...

 

Scan media library failed.

32 minutes ago

Exception of type 'SQLitePCL.pretty.SQLiteException' was thrown.

 

I've also noticed that when I play a complete show, it doesn't get marked as played even though it shows 100% in the progress bar in the Emby for WMC client.  Did the update break my database?

Everything else seems to be running as normal, though it did take some time for the Emby icon to ever show up in the system panel list.  Am I seeing some new permissions issue?

[Luke 42090]

hi @@WhackOBill, can you please attach the emby server log? you can learn how to do that here:

https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

 

Thanks !

[WhackOBill 8]

I retried the scan, which failed in the same way, then restarted Emby to free up the log file.  I've attached it to this message.

server-63651571200.txt

[Luke 42090]

hi @@WhackOBill, can you check and make sure that you don't have multiple instance of emby server running? Check your windows startup, check windows services, make sure you are only starting it in one way and not more than one. Thanks !

[WhackOBill 8]

You know, I remember having a conflict a few years back where I had two startups for Emby at some point.  I think it was caused by originally from upgrading from MB3 when Emby first came out.  I will check the server tomorrow to see if there are two startup records again.  This is the only time I've ever manually upgraded Emby (as recommeded for 3.2.60.0) instead of letting it update itself and I'm wondering now if the manual install didn't recognize the existing startup record and created a second.

 

Thanks for the tip.  No wonder the SQLLite DB says it's locked in the log ... another instance has it open perhaps.

[Luke 42090]

I notice you're running it as a service, so check your windows startup, maybe you're running it twice at the same time, one as a service and the other in full desktop mode.

[WhackOBill 8]

You're right ... I had a service entry which I've set to Manual now as well as a Programs/Startup entry.  Oddly, I don't have Emby set to run at startup ... the checkbox is unchecked.  Might be a holdover shortcut from long ago.  I'm good to go now though.  Thanks for tolerating my lameness on this.  I should have figured this out on my own.

[Luke 42090]

Thanks for the feedback.