If so, shouldn't there be a 64-bit version of "wrapper.exe" and "wrapper.dll"?įrom the Application Library location "C:\Program Files (x86)\Universal Media Server\, I thought that all of UMS ran 32-bit! If I am interpreting this error message correctly, a 64-bit JVM routine is attempting to load the 32-bit module "wrapper.dll".īut, I am a novice when it comes to Java programming.
dll on a AMD 64-bit platform System signals will not be handled correctly. INFO | jvm 1 | :36:04 | WrapperManager: => This is a 64-bit JVM. INFO | jvm 1 | :36:04 | WrapperManager: of the Wrapper with a 64-bit version of Java, or vica versa. INFO | jvm 1 | :36:04 | WrapperManager: One common cause of this problem is running a 32-bit version INFO | jvm 1 | :36:04 | WrapperManager: current user and that the file has not been corrupted in any way. INFO | jvm 1 | :36:04 | WrapperManager: Please verify that the file is both readable and executable by the INFO | jvm 1 | :36:04 | WrapperManager: C:\Program Files (x86)\Universal Media Server\win32\service\wrapper.dll INFO | jvm 1 | :36:04 | WrapperManager: could not be loaded: INFO | jvm 1 | :36:04 | WrapperManager: The file is located on the path at the following location but INFO | jvm 1 | :36:04 | WrapperManager: WARNING - Unable to load the Wrapper's native library 'wrapper.dll'. INFO | jvm 1 | :36:04 | WrapperManager: Initializing. STATUS | wrapper | :36:04 | Launching a JVM. I discovered that there is a C:\Program Files (x86)\Universal Media Server\service\win32\ folder that containsĪ "wrapper.log" file with additional Log Records including: We might be making progress but, unfortunately, I need a little more assistance.
I'm not sure how to create firewall rules for a service, but you can probably find that out by searching the net if that is in fact the problem. Have you tried to disable the Windows firewall? When UMS runs as a service it runs in a "different context" so that any firewall rules you have made for the. When it comes to the problem itself, the reason UMS doesn't "work" as a service, I must say that I suspect some firewall is at play. :35:57.428 Reading RendererName: "Samsung EH5300" (default: "Unknown renderer") :35:57.427 Reading MediaInfo: true (default: false) :35:57.409 Using address /192.168.1.32 found on network interface: name:eth1 (Realtek PCIe GBE Family Controller) :35:57.170 Attached http player control handler to web server
:35:57.170 UPNP Services are online, listening for media renderers :35:56.779 Enabled 118 configurations, listed in order of loading priority: :35:56.717 Added file watch at renderers: renderers\\nf :35:56.639 Loading renderer configurations from C:\Program Files (x86)\Universal Media Server\renderers :35:55.842 Java: Java HotSpot(TM) Client VM 1.8.0_66 32-bit by Oracle Corporation :35:55.842 Starting Universal Media Server 5.3.1 :35:55.483 Language not specified, defaulting to OS language. I hope it is easily readable but all of the relevant Log Records are below: => Unlike the trace when run as an Application Program, there was no Trace Record: x:xx.xxx Access granted to /192.168.1.17 by rule: 192.168.1.17 <=Īnd, I do get the identical results without the "IP Filter" specification.Īnd, even with Java 1.8.0_25 which is what the UMS Installer downloads. To diagnose this problem, I suppose you will need a more detailed Log Trace or an NMAP trace?
I never even get the the UMS Icon on the TV!Ĭlearly, something isn't working correctly when run as a Windows 10 Service. But, when I run it as a Windows Service on Windows 10, it "fails": When run as an Application Program, it works perfectly. Has anyone succeeded in running the latest UMS (5.3.1) as a Windows Service on Windows 10? Read this if you want to run UMS as a Windows Service: Open TCP Ports 50 in Windows Firewall.