More > JRiver Media Center 27 for Windows
Library Server has failed to start
JimH:
MC doesn't automatically open the firewall. That's done by the firewall itself. If it's in a verbose mode.
Both sides must be open on 52100 to 52200. SSDP should be open on 1900.
Take a look at the wiki on Media Network. It's possible you've forgotten something.
If, as you describe, you cannot run Media Server on 52199 but you can on another port, then something else is using 52199. Media Server from MC26 or MC27?
RedJ:
--- Quote from: JimH on September 17, 2020, 02:02:29 pm ---Take a look at the wiki on Media Network. It's possible you've forgotten something.
--- End quote ---
I went through the Network section of the wiki. Probably should have listed that too.
--- Quote from: JimH on September 17, 2020, 02:02:29 pm ---MC doesn't automatically open the firewall. That's done by the firewall itself. If it's in a verbose mode.
--- End quote ---
I didn't mean that MC opened the firewall itself, just that Windows firewall automatically asked to add the entries once MC attempted to use that functionality.
Also checked Firewall rules against previously functional MC26 rules to make sure they were the same.
--- Quote from: JimH on September 17, 2020, 02:02:29 pm ---If, as you describe, you cannot run Media Server on 52199 but you can on another port, then something else is using 52199. Media Server from MC26 or MC27?
--- End quote ---
If something is using that port, it isn't visible to the operating system. I have checked with netstat via PowerShell, Microsoft's PortQry, and the NirSoft CurrPorts utility. It also isn't responding to external port check tools (forwarding was left in place for 52199). Meanwhile, Media Server's ports all appear to these tools when not using 52199.
I completely removed all versions of MediaCenter including 26 and 27 before reinstalling 27. So it's not running any others. A sanity check of running services and processes confirms this.
--- Quote from: JimH on September 17, 2020, 02:02:29 pm ---Both sides must be open on 52100 to 52200. SSDP should be open on 1900.
--- End quote ---
Nothing is blocking MC- it's wide open for it, including SSDP, but that port doesn't work even with firewall completely disabled and no other security software services running. It worked on port 52199 for a long time up until the upgrade. BTW- I couldn't ever locate any definitive Windows Firewall settings to use with Media Center/Media Server. That seems like something that should exist so it can be compared against.
AndrewFG:
You say you have been “unable to start a server”: What do you mean by that? What happens when you try? What dialogs do you see?
RedJ:
Under Media Network settings:
* Advanced>TCP Port: Set to 52199
* Click the "..." marching ants menu next to Access Key where the "Test connection to this server" option would beErrors with dialog "Information: Library Server has failed to start. Double-check that the configured port is not already in use and that your firewall software is not blocking it."
--- Quote from: AndrewFG on September 17, 2020, 03:46:29 pm ---You say you have been “unable to start a server”: What do you mean by that? What happens when you try? What dialogs do you see?
--- End quote ---
JimH:
Antivirus could stop Library Server from running.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version