Crashing at startup

[Eposia 0]

Every time I boot up my PC, Emby crashes on startup and I get this:

 

Problem signature:
  Problem Event Name:    CLR20r3
  Problem Signature 01:    MediaBrowser.ServerApplication
  Problem Signature 02:    3.2.28.0
  Problem Signature 03:    5999ddd6
  Problem Signature 04:    System.Management
  Problem Signature 05:    4.6.1590.0
  Problem Signature 06:    5787eec0
  Problem Signature 07:    259
  Problem Signature 08:    10e
  Problem Signature 09:    PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX
  OS Version:    6.1.7601.2.1.0.256.1
  Locale ID:    3081
  Additional Information 1:    afee
  Additional Information 2:    afee4799e90e6516e3f2fbbda763ed8e
  Additional Information 3:    d5ac
  Additional Information 4:    d5ac70ded443025355229665df100c25
 

 

Any help would be appreciated.

[Happy2Play 9783]

First thing I would try is reinstalling from the website.

 

Could you also post your server logs.

 

 

How to Report a Problem

[Eposia 0]

First thing I would try is reinstalling from the website.

 

Could you also post your server logs.

 

 

How to Report a Problem

 

I've tried everything - uninstalled, reinstalled etc. Still having the same issue. This is the server log from startup, when it crashes:

 

2017-08-31 18:27:34.756 Info Main: Emby

    Command line: C:\Users\eposia\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe

    Operating system: Microsoft Windows NT 6.1.7601 Service Pack 1

    64-Bit OS: True

    64-Bit Process: True

    Processor count: 8

    Program data path: C:\Users\eposia\AppData\Roaming\Emby-Server

    Application directory: C:\Users\eposia\AppData\Roaming\Emby-Server\System

 

 

That's as far as the log goes.

 

Attached is the server log when I manually start the server (which starts fine by the way, only crashes on windows startup):

server-63639801226.txt

[Luke 42085]

I'd need to see the log from when it auto-started, thanks.

[Eposia 0]

That is the log from the auto start up... In my message, not the attachment.

[Luke 42085]

That's from windows event viewer it looks like, that's not an emby server log. Is there an emby server log from that time?

[Eposia 0]

No, it's the servers. It's not windows event viewer log. Here's the log from 2 minutes ago from C:\Users\eposia\AppData\Roaming\Emby-Server\logs

 

server-63639957017.txt

[Eposia 0]

This is the windows event viewer logs in case they are of any use. By the way, the Emby Server service is disabled, no setting were changed when I updated from 3.2.27 to 3.2.28 (when this started to happen). Nor when I did a fresh install of 3.2.30. Emby is set to start when windows starts, service is disabled.

 

Event ID - Error 1000, Application error:

 

Faulting application name: MediaBrowser.ServerApplication.exe, version: 3.2.30.0, time stamp: 0x59a45df4
Faulting module name: KERNELBASE.dll, version: 6.1.7601.23403, time stamp: 0x56f58b17
Exception code: 0xe0434352
Fault offset: 0x000000000001a06d
Faulting process id: 0xa28
Faulting application start time: 0x01d323af5ad14f01
Faulting application path: C:\Users\eposia\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: c5c09cd4-8fa2-11e7-8bf4-1c1b0d66fbce

 

Event ID - 1026 .NET Runtime:

 

Application: MediaBrowser.ServerApplication.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.COMException
   at System.Management.ThreadDispatch.Start()
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObjectSearcher.Initialize()
   at System.Management.ManagementObjectSearcher.Get()
   at MediaBrowser.ServerApplication.MainStartup.IsAlreadyRunningAsService(System.String)
   at MediaBrowser.ServerApplication.MainStartup.Main()
 

Edited September 2, 2017 by Eposia

[Luke 42085]

well that's an error we've not seen before. thanks, it will be resolved for the next release.

[Luke 42085]

Why it's happening I don't know, probably some system call that throws an error due to some part of windows not being initialized yet. but we can catch and trap it.

[Eposia 0]

OK, I'll wait until the next release and see if it fixes things. Thanks.