Kodi Community Forum

Hello,

I'm a bit of a noob, but have been using kodi and serverWMC for a while now. My server PC was running windows7, but I recently upgraded to Windows 10 and did the manual install of Windows Media Center. Since then, whenever I start Kodi on either of my clients (Matricom gbox Q machines), I'm getting the "Recorded TV Folder not Found" message and no TV playback. It works fine on the server machine. I've checked the recorded tv folder and ensured that it is being shared.

I'm looking into upgrading my tv tuner to an HDHR2-US (currently using HDHR3-US) so I can use the HD Homerun DVR software. But was hoping I could fix this issue first.

Any help or suggestions would be greatly appreciated.

Thanks!

:16:33 T:18446744072443577088 ERROR: int CScriptInvocationManager::ExecuteAsync(const string&, const AddonPtr&, const std::vector<std::basic_string<char> >&) - Not executing non-existing script /storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/addons/script.navi-x/service.py
10:16:33 T:18446744072443577088 NOTICE: initialize done
10:16:33 T:18446744072443577088 NOTICE: Running the application...
10:16:33 T:18446744072443577088 WARNING: JpegIO: Error 55: Not a JPEG file: starts with 0x%02x 0x%02x
10:16:33 T:18446744072052821632 ERROR: AddOnLog: PVR WMC Client: Using ServerWMC MAC address from custom addondata '94E:80:70:FE:4A'
10:16:33 T:18446744072052821632 ERROR: AddOnLog: PVR WMC Client: Recorded tv 'smb://SULLIVAN-PC/Users/Public/Recorded TV' does not exist
10:16:33 T:18446744072443577088 NOTICE: starting zeroconf publishing
10:16:33 T:18446744072443577088 NOTICE: starting upnp client
10:16:33 T:18446744072053709184 NOTICE: ES: Starting UDP Event server on 127.0.0.1:9777
10:16:33 T:18446744072443577088 NOTICE: Current resolution: 1920x1080 @ 60.00 - Full Screen
10:16:33 T:18446744072443577088 NOTICE: GL_VENDOR = ARM
10:16:33 T:18446744072443577088 NOTICE: GL_RENDERER = Mali-450 MP
10:16:33 T:18446744072443577088 NOTICE: GL_VERSION = OpenGL ES 2.0

If you are switching to the hdhomerun pvr there is no reason to get this fixed first, as far as I know.

Your clients are not windows based so they can't access the shared folder until you enter the login credentials for the windows account that is running serverwmc (see the Folders tab in serverwmc). If that's not the problem, then consider posting you serverwmc log on pastebin.com.

I figured out my problem. I could not turn off password protection in Windows 10 advanced sharing settings. I followed method 3 of the attached link and it worked!!! http://www.kapilarya.com/how-to-turn-off...windows-10

I am now able to use serverWMC again, so will hold off buying a new HDHR tuner.

Only other issue I have is buffering. But I will search for threads on that and start a new one if need be.

Thanks for your help, Krusty!

One of the reasons I have a domain running at home is that accessing shares is more convenient, but there is also a desirable level of control and security. It seems possible that either the ServerWMC service, or the PVR WMC Kodi plugin, or both are not utilizing SMB networking security features consistently or correctly. Can anyone explain why there is an entry field in ServerWMC for username and password if the system doesn't work unless security is effectively disabled? I know that Kodi, at least has access to Samba or some similar library, since I can easily set up File manager sources that access shared folders in my domain properly, and the upgrade to Windows 10 did not affect this functionality at all.

At any rate, I now have this working on build 1703 (Creator's Update) of Windows 10. To do so I did two things in addition to what I have described above:

1. I went to into Advanced Sharing Settings under Network and Sharing Center and turned on the option for All Networks that says "turn on sharing so anyone with network access can read and write Public folders."
   
2. I entered the domain username and password for the domain user "mediauser" into ServerWMC without the domain prefix.
   

It did not start working until after I did the 2nd thing, so I am not sure whether the first thing is necessary. I will post back here later when I have had a chance to test both ways after rebooting both times.

So it is working, and for that my thanks to the developer and others who contributed bits and pieces of lore about this or that tweak that may or may not, in the end, be needed.
I would still like to have an answer to the question above, if possible. And even more so, a bit more of an explanation as to how the settings on the folder tab get used. It would also be nice if the mediauser password were not transmitted in plain text over the network, assuming that this is what its presence in the Kodi log file means.

The way the credentials are used is by serverwmc is that they are embedded in the samba path so that pvr.wmc/kodi can open the file over the lan. Afaik they are not required for windows clients if you have shared the recorded tv folder with 'everybody' - so I assume it wasn't working because of 1 above.

As for 2, repeating myself here, I don't think it should be necessary for windows clients, but I think you have possibly uncovered a bug when the domain name is entered as part of the login. It might be a parsing error do the to slash in the name, I'd have to look at the code to see if there is a problem there. My motivation to fix this is not high, as you are the first person to ever complain about it. Perhaps you can make a case for why it should be there.

You are right though, this scheme does transmit your login credentials "in the clear" across your lan (Again though, for windows clients you should not need to enter the credentials in serverwmc). I have taken care to make sure the password is not printed in the logs or config files, but that's all. I can see why this would not be acceptable to the more security minded user, so I suggest checking out one of the other pvr solutions, there are many to chose from and they are probably much friendlier to win10 setups. Good luck in your search.