Roku 3600x Model - "Channels not available yet. Please try again in a few seconds" then crash

[zootropolis 0]

Started experiencing a problem with the Live TV Guide a few days ago. Open the app, click on Guide under Live TV on my home page, and I get "Channels not available yet. Please try again after a few seconds." Then the app crashes back to the Roku home page. 

I can select/tune to a channel using the "On Now" listings on the home page, and it works, but if I try to pull up the guide while watching live TV I also get Channels not available yet and it crashes back to the Roku home page. 

I have also tried tuning to a channel and letting it run, over an hour, but as soon as I try to pull up the guide, it says Channels not available yet and crashes out. 

This only seems to be happening on my Roku 3600x model sticks. I have two of those and they both are behaving the same way.

Also would mention that sometimes the Channels not available yet message pops up and goes away and the app doesn't crash, but the Channels not available yet message will then keep popping up every several seconds. 

I also have a Roku 3810x Streaming Stick+ that doesn't have this issue. I can open the Emby app and immediately open the guide and it works. I can tune to a channel and also then open the guide and it works. 

The Streaming Stick+ is on Roku version 9.4.0 Build 4188-50. The problem 3600x sticks are on 9.4.0 build 4188-24 with no updates available. 

Happens with the 4.0.12 Beta and with the 4.0.4 standard version of Emby. Running server version 4.5.2.0. Haven't changed any server settings recently. 

Tried restarting Emby Server, restarting the PC, refreshing the guide data, changing from Emby Guide Data to XMLTV data. Also tried restarting the Roku Stick and unplugging it from the TV/plugging it back in. No difference. Just can't get the 3600x sticks to pull up the guide. 

I have a Hauppauge WinTV QuadHD Tuner card. 

Most recent server log attached. 

embyserver.txt

Edited November 9, 2020 by zootropolis

[ebr 16169]

Hi.  Can you please start up the app, wait about 30 seconds and then send a log from the app?

Thanks.

[zootropolis 0]

This morning I did a factory reset on one of the Roku sticks but it didn't make any difference.

However, just now after confirming the problem still existed, I shut down the server on the PC (right click system tray -> Exit) and reloaded the Emby Server app from the Start Menu icon. Then I went to the Roku and opened the app and waited 30 seconds. I did that so I could get an updated log file to submit, but now the guide opens correctly. 

I had tried 'Restart Emby Server' from the system tray icon in previous troubleshooting, but I had never tried 'Exit' and then relaunching it from the Start Menu until this morning. Not sure if that makes any difference. But somewhere along the way the problem disappeared.

I'll attach the log files here for reference anyway, but for now - problem solved.

 

embyserver.txt hardware_detection-63740505898.txt

[ebr 16169]

Let us know if it pops back up.  I'm guessing the channel load was timing out for some reason.

[Luke 42077]

@zootropolis has this helped?

[zootropolis 0]

Yes it has helped, I haven't seen the issue again since right click on system tray -> Exit and relaunching the server app. The guide opens immediately now in both the emby release and the emby beta on the 3600x Roku sticks, and no further emby app crashes have occurred. Thanks. 

Edited November 13, 2020 by zootropolis

[Luke 42077]

Thanks for the feedback.

[zootropolis 0]

The issue started again yesterday evening. I tried restarting the server app, exiting the app and relaunching it, restarting the Roku, updating the Roku, restarting the entire PC, refreshing the guide and also switching from Emby guide data to an xml file from zap2it, but nothing made a difference. I get the Channels Not Available Yet message, then a few moments later the app either crashes or it continues to say "Channels not available yet..." every several seconds. I can select a program from the On Now listings on my homepage and it tunes to the channel and will play, but if I try to bring up the guide, either from the home page or from within a TV Show that is playing, it shows that message and will either crash or keep showing that message every few seconds. 

I've attached a log from last night when I was fighting with it. I can see some types of error messages in the log, but I'm not sure how to interpret what it says.  

Maybe if this is just an older-Roku thing it will give me an excuse to go buy one of the new Chromecast devices  Thanks.

embyserver (1).txt

[ebr 16169]

The only request for channels I see in that log come from the web app on the server machine.  Can you start the Roku app, wait 60 seconds and then send a log from the app?

[zootropolis 0]

The issue is definitely intermittent. I attached a server log for activity today from about 22:00 to 22:20 when it happened several times, even with a 60 second pause before hitting the guide button on my home page.

I even filmed the error occurring here from 22:17 to 22:19, including the app crashing back to the Roku home page after 60+ seconds waiting before opening the Guide: 

https://photos.app.goo.gl/RcRRCcjTqcytvfws8 

Then I saw your post requesting the app log, so I understand if the attached server log isn't helpful but I thought I would still include it so you can see the error occurring from 22:17 to 22:19 and maybe find something in the server log for that.

Anyway, I then enabled debug mode in the app to get a log there. The app restarted when I enabled that feature, and the problem went away immediately. Guide opens after a 60 second pause, and I can also exit the app and reload and it opens immediately. 

I submitted the app log at 22:54 central time. The guide worked during that test, so I don't think it will help much, but I submitted it nonetheless. 

Should I just leave the debug mode feature turned on in the app and submit a log as soon as the problem happens again? And report back here in this thread when I submit a new app log?  Thanks. 

embyserver (2).txt

[ebr 16169]

9 hours ago, zootropolis said:

Should I just leave the debug mode feature turned on in the app and submit a log as soon as the problem happens again?

Yes, please.

Thanks.