Stuck on Splash screen

For help and support with Universal Media Server in general
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Post Reply
Posts: 16
Joined: Mon May 23, 2016 9:44 am

Stuck on Splash screen

Post by gideond » Sun Jun 17, 2018 3:23 am

I just updated from 7.01 to 7.10 and UMS won't load past the splash screen. I've uninstalled, reinstalled, clean installed and checked firewall and AV settings. The JAVA binary is showing in task manager as running, but i have no interface at all. Just a splash screen in the middle of the desktop. Reverting to 7.01 and it's working fine again.

Running Windows 10 x64 1803 build. I'll have access to an earlier Win10 build later today I can test it on. Java 8 is fully up to date.

Update: Tested this on my older Windows 10 build and while there is a lengthy delay on the splash screen after updating to 7.10 it does eventually load and continues to load more quickly after that.

Posts: 1
Joined: Thu Jun 28, 2018 4:34 pm

Re: Stuck on Splash screen

Post by BenM » Thu Jun 28, 2018 4:47 pm

I found this thread via Google, after having exactly the same problem - after upgrading to 7.1 on Win10 x64 it just hung at the splash screen.

I managed to fix it though. In the log file (C:\ProgramData\UMS\debug.log) I found:

INFO 2018-06-28 14:29:32.646 [main] Using database located at: C:\ProgramData\UMS\database
ERROR 2018-06-28 14:30:34.862 [main] Error updating tables: Out of memory.; SQL statement:
DEBUG 2018-06-28 14:30:34.865 [main] Database file count: 21634

So I closed UMS, then renamed the database file C:\ProgramData\UMS\database\ to (the file was about 10gb in size) and started UMS again - it opened fine and regenerated the database file without any problems.

Hope that helps.

Posts: 198
Joined: Thu Jun 30, 2016 1:07 pm

Re: Stuck on Splash screen

Post by boss » Thu Jun 28, 2018 8:02 pm

Or you can just delete the entire database folder. It will be rebuilt when UMS restarts.

Myself and at least one other user had the same problem when updating to UMS V7.1.0

Post Reply