Universal Media Server | Forum

It's working so far on the uninstall-reinstall... But it did as well previously Sun(worked)->Mon(didn't). Will update if the problems replicate.

Working on Galana's system, and...

It's failing to launch again (but it did work yesterday night when I first upgraded to v5.50), and strangely it's not generating a new debug.log file. I've attempted to launch around a dozen times after 11:30pm, but the debug file remains consistent from 10:27 am ...

Thanks again for some staggeringly impressive technical support, and hopefully what has been discovered can make your product even better in the future!

Yes, it passes the point where it used to stop, so it seems like a success. I assume UMS is starting and working?

I can access my own files via the web interface, and I just got Galana to install and test with her PS3, and all seems to be beautiful. I have her debug.log, but I assume it's largely ...

This isn't the full, but I assume it gets far enough to determine if everything is working right - it seems so on my side!

DEBUG 2016-01-01 15:33:20.607 [main] Base path set to file:///C:/ProgramData/UMS/UMS.conf
DEBUG 2016-01-01 15:33:20.630 [main] FileName set to UMS.conf
DEBUG 2016-01-01 15:33 ...

...but you should contact ImDisk's author and let him know about it. I doubt this extremly unfortunate combination of Java's lacking handling of Windows' shortcoming with a path that cannot correcly report it's root path is very common in combination with ImDisk, so I doubt it's known to him. This ...

In calling it "rogue", I was only referencing the fact that it broke on my config - I know your team designed the new coding intentionally, and it was more a tongue-in-cheek phrase than an offense to your programmers.

As for the rest of it, not much makes sense to me - but I will certainly direct ...

What the above shows is that everything is fine with T: - the permissions check is ok and it moves on, but when it comes to R: it fails again. I'm pretty sure there must be something strange going on with the file system on the RAM drive, or simply that Java can't interpret it.

As I mentioned ...

Well, that solved nothing but shifting the failure :roll:

INFO 2015-12-29 23:06:03.597 [main] Working directory: I:\UMS
INFO 2015-12-29 23:06:03.602 [main] Temp directory: T:\UMS\temp
ERROR 2015-12-29 23:06:03.603 [main] The Java temp directory "R:\Temp" is not writable by UMS
ERROR 2015-12-29 23 ...

Changed over to Java x64, took UMS 5.2.3 off and re-installed UMS 5.4 J8 - back to the original failure, instant self-termination with the same error as previous:

INFO 2015-12-29 22:37:56.355 [main] Working directory: I:\UMS
ERROR 2015-12-29 22:37:56.362 [main] A serious error occurred during PMS ...