Emby Windows Service NOT working correctly since 3.2.60 update

[pcnetwiz 0]

I've enjoyed Emby Server for a very long time.  I've used many different flavors, and currently settled on a Window version.  However, ever since the update of 3.2.60 (and the latest 3.2.70 didn't fix it either) I've experienced a strange problem with getting the Emby server service started, or rather getting Windows recognizing the service being started.  Let me explain.

 

Prior to 3.2.60 update, everything works fine without a hitch.  But after the 3.2.60 update, the Windows could not start the service.  However, if you manually start the service, you can see that the EmbyServer.exe executable is actually started, and I can browse from the browser normally.  However, Windows service control will think that it couldn't start the service, hence throw an error message.  (see attached image)  Does anyone have similar issues?  If I kill the EmbyServer process, and launch it manually from the start menu, the system works flawlessly.  However, if I shutdown the EmbyServer, and start it manually from the Windows service control, samething happens.  I can still use the service remotely.  It's just annoying that Windows will always have a red Exclamation point saying that there is something wrong with one of my services.  

 

Thanks for any input in advance.

 

Andrew,

[Happy2Play 9785]

Sorry there a dozens of topics on this.  The original method no longer works (well it sort of work but not controlable).  This a a big change in net core version.

 

I would run "sc delete "Emby Server".

 

 

Running Emby Server as a Windows Service

[pcnetwiz 0]

Are you suggesting to delete the existing Emby Windows service, and then use the NSSM in the URL you provided to create a new Windows Service?

 

Thanks, I will give it a try!

 

Andrew,

[Luke 42088]

Yes that is correct, thanks.

[berrick 30]

@@pcnetwiz

 

Just to add my 5 pence worth I have had more trouble getting nssm to work than I ever did with the other methods for running as a service.

 

What I found was this;

1. My media server is domain joined
2. Media is on a NAS which can only be accessed with a Domain admin account

• On the Log On tab of the newly created nssm service I had to select "This account" and add the domain admin account credentials from point 2
• refreshed Services and checked the log on as column to ensure need account was being used
• Stop/start the new service

This allowed Emby to work. Any other credentials would just cause the error "NO streams - got it" when trying to play media.

 

Don't have any issue with credentials just running EmbyServer.exe on media server instead of nssm.

 

Incidentally @@Luke, anyone, when running as a service should I not see the Emby tray icon?

[GhostRider 49]

Incidentally @@Luke, anyone, when running as a service should I not see the Emby tray icon?

 

No, the system tray icon is not part of the service so it is not visible when running Emby as a service.

Edited January 20, 2018 by GhostRider

[berrick 30]

@@GhostRider

 

Thanks for confirmation.

 

Not often these days I need to login into server and couldn't remember for sure

[pcnetwiz 0]

(Resolved)  After deleting the old NT service, and creating a new one with the NSSM, everything is working again.  @@Luke thank you for the tip.

 

Andrew,

[Luke 42088]

Thanks for the feedback.