Jump to content

Emby Server Crashes on Start


HappyGilmour

Recommended Posts

HappyGilmour

Hi,

 

As of 3 days ago, my Emby Server for Windows will not start. It crashes with a fault on clr.dll. I have downloaded the latest version and ran the install over my current installation with no joy. I am including 3 log files. Hope they have the data that will help someone figure this out. Thank you in advance!

MBClassic-29220162e027650a12f483d9558fa84e5a48c36.log

MBClassic-29220169b4742325fb34c95bed342196e505eb3.log

MBClassic-29220166703474846224c07b8ccede4497b9392.log

Link to comment
Share on other sites

Hi,

I guess I need a better description perhaps of what the problem is. You're saying the server crashes on startup and yet these logs show successful startups as well as playback.

 

It is possible the server is running fine, but the Emby for Windows Media center app is the one that's crashing?

Link to comment
Share on other sites

HappyGilmour

Well that is curious. I have attached screenshots of the error I am getting. After this happens I cannot access it via web interface, my Roku client or Media Center.

 

 

 

 

post-4679-0-21191100-1457111998_thumb.jpg

post-4679-0-09934300-1457112007_thumb.jpg

Link to comment
Share on other sites

ok. what i would do is install the latest version from the website on top of your existing install, then let me know if the issue persists. thanks.

Link to comment
Share on other sites

HappyGilmour

I did that twice. Still got the same error (unless you have updated the version in the last 3 days.)

Link to comment
Share on other sites

HappyGilmour

I downloaded the setup.exe. That downloaded the latest version. I let it install. It automatically tried to start the server and Windows reported the same error with the clr.dll module. 

 

PS Thank you for actively supporting the product. 

Link to comment
Share on other sites

can you check the windows event viewer to see if it has a detailed error report? thanks.

Link to comment
Share on other sites

HappyGilmour
Copied from detail of event:

 

Log Name:      Application

Source:        Application Error

Date:          3/4/2016 12:54:22 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      media-center.morganfamily.homedns.org

Description:

Faulting application name: MediaBrowser.ServerApplication.exe, version: 3.0.5882.0, time stamp: 0x56d8f920

Faulting module name: clr.dll, version: 4.6.1055.0, time stamp: 0x563c12de

Exception code: 0xc0000005

Fault offset: 0x000000000000f1b5

Faulting process id: 0xbb4

Faulting application start time: 0x01d1763ee228deb0

Faulting application path: C:\Users\media.MORGANFAMILY\AppData\Roaming\MediaBrowser-Server\System\MediaBrowser.ServerApplication.exe

Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll

Report Id: 1fee7f72-e232-11e5-9144-6cf049721993

Event Xml:


  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2016-03-04T17:54:22.000000000Z" />

    <EventRecordID>43106</EventRecordID>

    <Channel>Application</Channel>

    <Computer>media-center.morganfamily.homedns.org</Computer>

    <Security />

  </System>

  <EventData>

    <Data>MediaBrowser.ServerApplication.exe</Data>

    <Data>3.0.5882.0</Data>

    <Data>56d8f920</Data>

    <Data>clr.dll</Data>

    <Data>4.6.1055.0</Data>

    <Data>563c12de</Data>

    <Data>c0000005</Data>

    <Data>000000000000f1b5</Data>

    <Data>bb4</Data>

    <Data>01d1763ee228deb0</Data>

    <Data>C:\Users\media.MORGANFAMILY\AppData\Roaming\MediaBrowser-Server\System\MediaBrowser.ServerApplication.exe</Data>

    <Data>C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll</Data>

    <Data>1fee7f72-e232-11e5-9144-6cf049721993</Data>

  </EventData>

</Event>

Link to comment
Share on other sites

anything else, is that really it? there are no crash logs in the emby server logs folder?

Link to comment
Share on other sites

HappyGilmour

I don't see anything else in the log folder except what I sent you. This event happens at the same time. (Sorry I didn't see it the first time.) Maybe it has additional info?? Looks like a .NET issue.

 

Log Name:      Application
Source:        .NET Runtime
Date:          3/4/2016 12:54:22 PM
Event ID:      1023
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      media-center.morganfamily.homedns.org
Description:
Application: MediaBrowser.ServerApplication.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEE87AF1B5 (000007FEE87A0000) with exit code 80131506.
 
Event Xml:
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1023</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-03-04T17:54:22.000000000Z" />
    <EventRecordID>43105</EventRecordID>
    <Channel>Application</Channel>
    <Computer>media-center.morganfamily.homedns.org</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Application: MediaBrowser.ServerApplication.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEE87AF1B5 (000007FEE87A0000) with exit code 80131506.
</Data>
  </EventData>
</Event>
Link to comment
Share on other sites

HappyGilmour

Was curious if you found anything else with this? I will make myself available tomorrow if you need me to try different things. One thing I have not tried is a full uninstall and then fresh reinstall. I was afraid it would erase all my settings/library. But I will do whatever needs to be done. Thanks again.

Link to comment
Share on other sites

HappyGilmour

That did not work. It told me I was up-to-date on .NET 4.5 and it wouldn't run. So I uninstalled and reinstalled .NET. Still get the same Emby error. So now trying to uninstall Emby Server and then reinstall it. I'll let you know. 

Link to comment
Share on other sites

HappyGilmour

When I go to uninstall it tells me that "Emby Server has closed" but the process does go on for a while and then finish. But any reinstall (stable,beta,dev) causes the same issue. I have tried disabling AntiMalware (MS Security Essentials) and same error. I am out of ideas. If you folks are also out of ideas I will just blow out Windows and start over.

Link to comment
Share on other sites

QwEmby

I would also consider running hardware diagnostics to check for failures. i researched the error code a bit

Finding the exact cause for this is going to be difficult. Review any unmanaged code your service might be using. Suspect environmental problems if there is no obvious candidate, misbehaving malware scanners are notorious. If it repeats very poorly then suspect hardware problems like soft RAM errors.
Link to comment
Share on other sites

HappyGilmour

I read that same post about this error. I ran some hardware diags and they came up clean. I am going to try blowing out Windows and reinstalling this weekend. I will let you know.

 

I think it is important to point out too that, while this issue was sudden, it seems too consistent (crashes EVERY time on startup) and not seeing issues on any other app or system log. That, to me, would rule out a hardware problem. What hardware would this app hit that no other part of the OS or any other app hit? 

 

My gut is telling me an update to a different app or a Windows update is causing this problem. Hoping that a fresh OS install corrects it. Again, I will post back here with the results. Thanks again for your help. It is very much appreciated.

  • Like 1
Link to comment
Share on other sites

HappyGilmour

CHKDSK revealed no errors. SFC found a corrupted ehrecvr.exe. It replaced it from source. But that had no effect on the issue. The .NET repair tool reregistered the install service. But that also had no effect on the error. It sent logs to Microsoft. I guess I will wait to see if they come back with something?

 

In the meantime I am running CHKDSK on my 2 large storage volumes as well.

  • Like 1
Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...