Upgrade 9.3 - Windows current upgrades - UMS doesn't start anymore

For help and support with Universal Media Server
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Post Reply
Trebly
Posts: 24
Joined: Tue Mar 06, 2018 2:28 am

Upgrade 9.3 - Windows current upgrades - UMS doesn't start anymore

Post by Trebly »

Hi,

Ctx : Windows 10 Pro.

During the last two year each time I receive an upgrade I validation and installed it without the "clean" option.
I got back my configuration and connexions without problem.

This last time (03/07/2020 v 9.3), this happens :
  • the upgrade stopped on the jre-x64 : unable to upgrade "error opening file to upgrade" (I renamed the jre current directory to old)
  • After the end of installation the loading panel is displayed but remains which means that it doesn't start any process from the exe (just shows the logo and hangs).
I don't know what to do :
- I thought to run again install but in clean mode, but how to get back the configurations after if this solves the start problem ?

Best regards
Trebly
Trebly
Posts: 24
Joined: Tue Mar 06, 2018 2:28 am

Re: Upgrade 9.3 - Windows current upgrades - UMS doesn't start anymore

Post by Trebly »

Hi,

Checked debug.log.
Found error in "Database connection error : IO Exception : null

Look at new thread with this simple subject.

Thanks

Trebly
User avatar
SubJunk
Lead Developer
Posts: 3707
Joined: Sun May 27, 2012 4:12 pm

Re: Upgrade 9.3 - Windows current upgrades - UMS doesn't start anymore

Post by SubJunk »

It probably means you tried to install the program while it was still running. Please restart the computer and try installing again.
If that still doesn't work, try opening Task Manager (right-click an empty part of the taskbar and click Task Manager) and then close "javaw.exe"
Trebly
Posts: 24
Joined: Tue Mar 06, 2018 2:28 am

Re: Upgrade 9.3 - Windows current upgrades - UMS doesn't start anymore

Post by Trebly »

Hi,

Thanks, I have done all of this, but I don't got any solution.
Looking into ums.log I found that that crash was coming from a failure at opening the database.

After this I have created a new thread with a new title, this to formulate the problem in an other manner, report the tests that I have done.

https://www.universalmediaserver.com/fo ... 035#p41035
Post Reply