Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1119787" data-attributes="member: 82144">Very important: you need to make sure you alter the TV Server one, because that one is copied for MediaPortal on all clients. To be clear, any changes in the MediaPortal ones that are not also made in the TV Server one will be overwritten.Which machine did you reboot - client-only or client-server (HTPC)?Rebooting the client-only would make no difference. Rebooting the client-server might help.If you had asked I could have told you that wouldn't help. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />Really, the two solutions I listed in my previous post are the only way you are going to solve this problem. No amount of reinstalling will help.That's because MPExtended (which presumably connects to the database as root also) is running on the server. The root user will have no problem connecting to the database from any program running on the server, whether that be TV Server itself, MPExtended, or any other software. WebMediaPortal has no problems because it does not try to connect to the database directly like MediaPortal does.As above. Make sure you change the TV Server configuration, otherwise the MediaPortal configuration changes are all overwritten.It looks like you're making progress though, because some are using mediaportal. According to your previous logs 192.168.1.5 is HTPC (the server). I can't tell if that is TV Server without fresh logs.If you want further help from me, fresh logs from both the client and server (HTPC) would be helpful at this point.</blockquote>

[QUOTE="mm1352000, post: 1119787, member: 82144"] Very important: you need to make sure you alter the TV Server one, because that one is copied for MediaPortal on all clients. To be clear,[B] any changes in the MediaPortal ones that are not also made in the TV Server one will be overwritten.[/B] Which machine did you reboot - client-only or client-server (HTPC)? Rebooting the client-only would make no difference. Rebooting the client-server might help. If you had asked I could have told you that wouldn't help. ;) Really, the two solutions I listed in my previous post are the only way you are going to solve this problem. No amount of reinstalling will help. That's because MPExtended (which presumably connects to the database as root also) is running on the server. The root user will have no problem connecting to the database from any program running on the server, whether that be TV Server itself, MPExtended, or any other software. WebMediaPortal has no problems because it does not try to connect to the database directly like MediaPortal does. As above. Make sure you change the TV Server configuration, otherwise the MediaPortal configuration changes are all overwritten. It looks like you're making progress though, because some are using mediaportal. According to your previous logs 192.168.1.5 is HTPC (the server). I can't tell if that is TV Server without fresh logs. If you want further help from me, fresh logs from both the client and server (HTPC) would be helpful at this point. [/QUOTE]

Verification