[krustyreturns]

How do you configure this forum to get the burning ears notification?  The specific exception he is reporting seems to be an annoying issue with filesystemwatcher, I found a number of programmer threads of people asking for help on it but I could not find anyone who found a solution.  Some did imply it was an issue with watched network shares though, so maybe that will take care of it.

[JoshDi]

How do you configure this forum to get the burning ears notification?  The specific exception he is reporting seems to be an annoying issue with filesystemwatcher, I found a number of programmer threads of people asking for help on it but I could not find anyone who found a solution.  Some did imply it was an issue with watched network shares though, so maybe that will take care of it.

thank you, krusty. If you can provide a test build that removes the network shares and only monitors my Recording TV directory, I am happy to test.

[sbthomas]

I'm not sure but i think what Krusty was saying was for you to remove the two unnecessary watched folders from Windows Media Center. It has been quite a while for me but if you check in Windows Media Center under Settings -> Media Libraries or  Settings -> TV -> Recorder -> Media Libraries and make sure WMC is not watching those folders, hopefully that will resolve the issue for now.

[JoshDi]

Any updates on this? I am getting more freezes (at least 2 per day)

[krustyreturns]

I forgot about this, I will take a look today.

[krustyreturns]

Update to the latest preview version witch is 1259.  After it installs and runs, find this setting FSW_RecFolderOnly and set it to true.  Then save the config and restart serverwmc.  That should make it only watch the rec tv folder.  If it doesn't work I need to see the serverwmc log.  Sorry for the delay.

[JoshDi]

Update to the latest preview version witch is 1259.  After it installs and runs, find this setting FSW_RecFolderOnly and set it to true.  Then save the config and restart serverwmc.  That should make it only watch the rec tv folder.  If it doesn't work I need to see the serverwmc log.  Sorry for the delay.

thank you! Downloaded, changed the setting FSW_RecFolderOnly to true and restarted serverwmc. Will let you know if I still experience freezing. Happy New Year!

[JoshDi]

With FSW_RecFolderOnly to true, ServerWMC is still freezing. 

Here are the errors in the log:

xml:
2019/12/27 18:19:26.669 StreamRemux> no active stream found for clientName Emby^HTPC-Xeon^0

2019/12/27 18:19:26.685 StreamRemux> no active stream found for clientName Emby^HTPC-Xeon^0

2019/12/27 18:19:26.685 StreamRemux> no active stream found for clientName Emby^HTPC-Xeon^0

2019/12/27 18:19:26.685 StreamRemux> no active stream found for clientName Emby^HTPC-Xeon^0

2019/12/27 18:19:26.685 StreamRemux> no active stream found for clientName Emby^HTPC-Xeon^0

2019/12/27 18:19:26.685 StreamRemux> no active stream found for clientName Emby^HTPC-Xeon^0

2019/12/27 18:19:26.685 StreamRemux> no active stream found for clientName Emby^HTPC-Xeon^0

2019/12/27 18:19:26.685 StreamRemux> no active stream found for clientName Emby^HTPC-Xeon^0

2019/12/27 18:19:26.685 StreamRemux> no active stream found for clientName Emby^HTPC-Xeon^0

2019/12/27 18:19:26.685 StreamRemux> no active stream found for clientName Emby^HTPC-Xeon^0

2019/12/27 18:31:12.336 MaintenanceTimer> Callback started...

2019/12/27 18:31:12.336 RecordingCache_Refresh> [TimerMaintenance] Cache background refresh started.

2019/12/27 18:31:12.336 StreamRemux> no active stream found for clientName Emby^HTPC-Xeon^0

2019/12/27 18:31:12.336 TimerCache_Refresh> [TimerMaintenance] Cache background refresh started.

2019/12/27 18:31:12.336 GetPage> Status-json

2019/12/27 18:31:12.336 MaintenanceTimer> Callback completed in 0.00 sec.

2019/12/27 18:31:12.336 GetHtml> error, file: 'Status-json.html' count not be found

[krustyreturns]

Please post the entire log on pastebin and put a link to it here

[JoshDi]

Please post the entire log on pastebin and put a link to it here

sure, please see this link:
https://pastebin.com/uRiVGiWp

Anyway we can get a more verbose error of the "illegal characters"  I dont have any files in either my main recording folder or the other two network folders - so I dont know what illegal characters are there since there are no files.

[krustyreturns]

I guess we are left where we began then, it just seems to be a problem with window's FileSystemWatcher and last I looked I could not find a fix for it nor is there a way to catch the exception it raises.  I also don't know why some people like yourself experience problems with it but others don't, I guess its a conflict with other software.  FWIW, I use autoit scripts to watch folders and perform actions when certain files are created and it works very well.

[JoshDi]

I guess we are left where we began then, it just seems to be a problem with window's FileSystemWatcher and last I looked I could not find a fix for it nor is there a way to catch the exception it raises.  I also don't know why some people like yourself experience problems with it but others don't, I guess its a conflict with other software.  FWIW, I use autoit scripts to watch folders and perform actions when certain files are created and it works very well.

I think I made a breakthrough. I turned off the username/password for the share and the freezing has gone away. Originally, I had the username/password set for the SMB shares, but my network shares used a different username. 

The RecordingTV folder is available in the Public user folder, so everyone can typically access it without a password.

[krustyreturns]

Thanks for the info.  How long has it run for?

[JoshDi]

Thanks for the info.  How long has it run for?

hasnt frozen since. Its definitely a problem where the SMB credentials are being applied to all network drives. 

I do notice when a lot of shows are being recorded simultaneously, that serverwmc is unresponsive. I have 12 tuners in my system and notice this happens when there are over 6 items being recorded. 

Any ideas?

[krustyreturns]

Serverwmc doesn't record anything, so I can't see why it would have any performance hit even if all twelve tuners were being recorded.  The computer it is running on however is busy doing a lot of recording, so maybe that is what you are seeing?  How does the 'unresponsive'-ness of serverwmc manifest itself?