Jump to content

Windows service on Server 2016 - won't start


Recommended Posts

Posted

I'm not at the machine now, but the detail tab on the error just repeated the same message

Posted (edited)

I note from this other post that the version of NSSM might be relevant.

 

https://emby.media/community/index.php?/topic/50155-emby-service-is-gone/page-3&do=findComment&comment=503569

 

I'm in bed at the minute but when I wake up I'll try again with the very latest build I can find, as I'm pretty sure the one I've been using isn't that.

Edited by danswan
Happy2Play
Posted

I am using "nssm 2.24 (2014-08-31)" on my test build.

 

2.24.0.74

Happy2Play
Posted

What is your server version number?

Posted

I am using "nssm 2.24 (2014-08-31)" on my test build.

 

2.24.0.74

Damn, same as mine :(

Posted

What is your server version number?

Version 3.2.34.0

Happy2Play
Posted

Version 3.2.34.0

 

Actually meant server 2016 version number.

Posted

It sounds like you shouldn't be using the nssm method.

Posted

Actually meant server 2016 version number.

 

 

Sorry. Version 1607 (OS Build 14393. 1715)

 

 

It sounds like you shouldn't be using the nssm method.

 

What's the alternative?

Posted

If this is an older installation it will have already created a windows service that you can keep on using.

Happy2Play
Posted

Sorry. Version 1607 (OS Build 14393. 1715)

 

 

 

What's the alternative?

 

Test system is on Version 1607 (OS Build 14393. 693),  I will see if I can update to that version number.

Happy2Play
Posted

Looks like Windows update will take me to (OS Build 14393.1770).  Will see after update installs.

 

KB4041691 (OS Build 14393.1770)

Happy2Play
Posted

Sorry updating to (OS Build 14393.1770) made no difference.  Later I will test updating to (OS Build 14393.1770) then installing Emby and service via NSSM, to see if I get the same results.

Posted (edited)

Sorry updating to (OS Build 14393.1770) made no difference.  Later I will test updating to (OS Build 14393.1770) then installing Emby and service via NSSM, to see if I get the same results.

 

Thank you!

 

 

If this is an older installation it will have already created a windows service that you can keep on using.

 

It's not an older install. I put server 2016 on my server box around a month ago and installed Emby afresh then. I was looking for the service, couldn't find it, so found out about the NSSM method.

Edited by danswan
Posted

In case it's relevant, I'm updated to 14393.1770 now, no change

Happy2Play
Posted

Have you tried deleting the current service and recreating it?

Posted (edited)

Many times :(

 

**Edit** It's working! I'm not sure what changed, but I did it again, and it wouldn't stay running again. I then deleted & recreated, this time giving the service a different name (EmbyServer rather than Emby) and also checked 'Allow the service to interact with the desktop', and it seemed to work OK?!

 

So I deleted again, and set up using the standard steps, and it does now appear to be worked as expected. Id like to say what fixed it, as I've followed these steps many times, but the bottom line is it's now working :)

Edited by danswan
Happy2Play
Posted

Glad you got it working.

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...