04-02-2012 07:54:49 AM
This is the message I receive in a grey box at the top of my screen which therefore locks up my entire system making me have to reboot it via turning the power off to the system.. all the time.
I wanted to delete some programs that were set to record unbeknownst to me and it locked up saying the system is busy. Then I tried to program it to record something in the future.. locked up again.
When it does this you cannot change the channel.. take the menu off the screen NOTHING.. I let it sit like that over night..well this morning had to reboot the system yet again.
Why is it doing this and how can I fix it besides calling AT&T and having someone come out or like I wanted to last night. take and pitch it threw the window.
Any help will be greatly appreciated cause I'm not liking my system right now at all.
04-02-2012 02:25:01 PM
I have seen that message since the ability to rew/ff live tv from any stb. I see it after I have deleted a recorded program and I press a button to change the channel or something. But the box only stays up a few seconds and then goes away. After that I can use the stb normally. I have never had it completely lock up. Have you tried unplugging the ac cable from yrou RG for 30 seconds and then reconnect it? After it reboots do the same thing with all of your stbs. If the problem persists contact TS and let the CSR know what is going on with your service.
04-21-2013 09:00:58 PM
04-22-2013 05:18:56 AM
04-25-2013 04:01:05 PM
I've been slammed by this all day impacting watching things I have recorded. I have no problems watching live TV
I only have one TV with the DVR wired directly to the gateway.
04-28-2013 02:43:30 PM
I was seeing this message for awhile when I was erasing a recorded program and tried to do something else with the DVR. I noticed that the DVR was responding really slow to the remote commands for about two weeks or so. Seeing that others had posted about this issue as well I figured ATT must have been doing some kind of update or was about to rollout one. The problem has since resolved itself, and I read that there was a new update rolled out.
You may continue to see this issue for a bit longer seeing that updates are rolled out region by region. And depending on where you will get it sooner or not as soon.