Natelanxon 27 Posted August 31, 2025 Posted August 31, 2025 Hi there. I've had instances over the last few weeks where Emby Server seems to crash, although not in a way that kills the app itself. Something seems to be happening that prevents the server from being accessible on localhost. I'm attaching the most recent log file and am also pasting below the two Windows error logs that occurred at the time Emby became unreachable. - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name=".NET Runtime" /> <EventID Qualifiers="0">1023</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2025-08-31T13:02:23.7587927Z" /> <EventRecordID>233278</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>DESKTOP-20VMVUI</Computer> <Security /> </System> - <EventData> <Data>Application: EmbyServer.exe CoreCLR Version: 6.0.3624.51421 .NET Version: 6.0.36 Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FF918FA4089 (00007FF918DD0000) with exit code c0000005.</Data> </EventData> </Event> - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2025-08-31T13:02:24.1334084Z" /> <EventRecordID>233279</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>DESKTOP-20VMVUI</Computer> <Security /> </System> - <EventData> <Data>EmbyServer.exe</Data> <Data>4.8.11.0</Data> <Data>670d0000</Data> <Data>coreclr.dll</Data> <Data>6.0.3624.51421</Data> <Data>670ddee9</Data> <Data>c0000005</Data> <Data>00000000001d4089</Data> <Data>3020</Data> <Data>01dc1a24573449d3</Data> <Data>C:\Users\nate\AppData\Roaming\Emby-Server\system\EmbyServer.exe</Data> <Data>C:\Users\nate\AppData\Roaming\Emby-Server\system\coreclr.dll</Data> <Data>fab8259a-1e13-4385-86dc-6e675ad0f8db</Data> <Data /> <Data /> </EventData> </Event> embyserver-63892246007.txt
Luke 42077 Posted August 31, 2025 Posted August 31, 2025 Hi, please try removing these plugins: 2025-08-31 04:07:16.574 Info App: Loading InfuseSync, Version=1.5.2.0, Culture=neutral, PublicKeyToken=null from C:\Users\nate\AppData\Roaming\Emby-Server\programdata\plugins\InfuseSync.dll 2025-08-31 04:07:16.574 Info App: Loading statistics, Version=3.4.1.1, Culture=neutral, PublicKeyToken=null from C:\Users\nate\AppData\Roaming\Emby-Server\programdata\plugins\Statistics.dll Then restart the server and see if it happens again. Thanks.
Natelanxon 27 Posted August 31, 2025 Author Posted August 31, 2025 Will do - thanks. Are there known issues with those plugins?
Luke 42077 Posted August 31, 2025 Posted August 31, 2025 2 minutes ago, Natelanxon said: Will do - thanks. Are there known issues with those plugins? No, but since the problem is not obvious we should start by eliminating external variables.
Natelanxon 27 Posted September 10, 2025 Author Posted September 10, 2025 Just to update, the problem occurred again since disabling those two plugins. However, I did also run my recent error logs through ChatGPT and Gemini Pro and one suggestion is that the database file may have been locked by a real-time backup application. I have Backblaze running continuously on this system and have never excluded any of Emby's system folders. I've now excluded the Emby folder and since doing so have had no reoccurrence of this issue. I'll report back again in a few days. 1
Solution Natelanxon 27 Posted October 22, 2025 Author Solution Posted October 22, 2025 I have a resolution. The problem was not to do with the database file being locked but in fact my Emby port assignment conflicting with another piece of software that uses the same port (WireGuard, in my case). I changed Emby’s port to a different number and ever since then I’ve had no reoccurrence of the problem. I hope this helps anyone else who’s had a similar issue to mine. 1
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