Server won't upgrade (Fails)

[tmservo 2]

Currently running Server 5885. I shut it down to upgrade to the new (5934) and it fails... generating this error.

 

 

Log files: https://onedrive.live.com/redir?resid=D76DDC71AADC6470!383807&authkey=!ALFF--YQK-yWz4I&ithint=file%2ctxt

[tmservo 2]

Note: I also can't uninstall Mediabrowser from control panel; that fails.. so if that is suggested; I'm not sure what happened here..

[Luke 42085]

Try rebooting your computer, then install the update from the website.

[jordy 284]

@@tmservo, just a thought... can you write a new (txt or something like that) file to the users\chris\appdata\roaming\... folder. Maybe the write permissions have changed?

Edited May 20, 2016 by jordy

[CashMoney 94]

I get this every now and then, Luke's instructions always work for me tho

[jscoys 147]

Yeah I have been having this for a while now. In fact if you go into task manager you'll see that the service has correctly shut down but the process "Emby server" is still running. You've got this message because the new install can't rename the directory "system" because it's in use by the process not terminated. What i do here is that i wait between 2 minutes and 5 minutes and in general the process terminates by himself. If not, i kill it... After the process terminated, you can smoothly do the new installation.

 

 

Sent from my iPhone using Tapatalk

[jscoys 147]

@@Luke : we've got a workaround here but in the near future a look at this should be done. I confirm that it does this for fresh installs too.

 

 

Sent from my iPhone using Tapatalk

[ebr 16192]

@@Luke : we've got a workaround here but in the near future a look at this should be done. I confirm that it does this for fresh installs too.

 

 

Sent from my iPhone using Tapatalk

 

There isn't a lot we can do.  The problem is that a program from within that folder is still running.  We've asked it to terminate but, in some cases - and many beyond our control, a process could take a long time to actually quit. 

[jscoys 147]

There isn't a lot we can do.  The problem is that a program from within that folder is still running.  We've asked it to terminate but, in some cases - and many beyond our control, a process could take a long time to actually quit. 

 

As I said before, it's not an obscure process that we haven't got any control on it, it's the "Emby server" itself which for some reasons doesn't close immediately and takes 5 minutes... So in a near future we have to look closer to what happens after asking the app to exit because today it seems to hang more time it really needs (Maybe some external sync requests). The other problem is that it seems when we ask the "Emby" service to stop, it stops whenever the process still alive or not. So we're happy saying "if the service is closed I assume that the process is closed too" but... no! That's why you've got this error message when you try to update immediately after.

 

Today the workaround I proposed or Luke's solution are both valid to update to a new server version.

[ebr 16192]

Improvements are always possible.  I'm just saying that, sometimes at least, this situation is largely out of our control (regardless of the process involved).

 

Also, it isn't ubiquitous or even, I don't think, particularly widespread.  None of my machines ever have this problem and that must also be the case for the majority of people or no one would be getting automatic updates.

 

That doesn't mean it isn't a problem or that we can't someday make it better.  But we can't be sure until we find out exactly what the hold up is.  In many cases like this it is finally discovered that the culprit is some other system or process or even hardware.

[Luke 42085]

Yea it's not that we don't want to improve it, it's just that it's difficult to reproduce.