10-19-2014 6:04 PM
I'm getting this message on the screens of the TVs in my house. It appears when I first turn on a TV:
Error Code: 0 - Failed to load resource
Kx: Faile to load resource
Web exception: the remote name could not be resolved
Socket exception: No such host is known.
Anyone know what's up, and what can be done about it?
Solved by: Go to Solution.
- edited 10-19-2014 7:54 PM
It does not appear to be anything associated with your specific setup. It looks like it has been happening nationwide:
It would be nice if someone from AT&T acknowledged the issue. About 2 weeks ago, there also seemed to be a targeted DoS attack aimed specifically at the Motorola 589's but the advice on this site kept simply offering standard troubleshooting tips. As with this issue, a lot of headaches could have been avoided with some simple upfront ackowledgement that they are aware of the problem.
Edit - there is also another thread on this site about this:
10-19-2014 10:57 PM
When it happened on mine I just hit the exit button and it reload and worked fine. Only happened once...
10-20-2014 8:40 AM
Are you still experiencing those issues? I believe it can be related to an app channel, possibly if it was left open when the TV was turned off. If you still need help, our team will be happy to assist! You can send us a private message by clicking here. In your message, please include your full name, phone number, account number and the best time you can be reached.
Please let us know if you have any other questions.
Did a post have a solution that worked for you? Help other people find solutions faster by marking posts that helped you as an "Accepted Solution". Learn about accepted solutions: Learn More.
10-20-2014 9:47 AM
I have also seen the error message several times recently. Like Kong57, everything works and there is no interruption of service. But I have not opened any app channels (at least knowingly) in some time as Dmitriy mentions. Other than normal viewing of programs and recordings, the only functions I use include the guide, DVR programming and search. So I will be curious to see what might be causing this seemingly harmless but recurring error.
10-20-2014 10:53 AM
I have noticed it once on each TV. Pressing OK, got me off of the error screen.
10-20-2014 12:04 PM
Same with me - it happened once on each TV, and I just selected "Exit" and everything was working fine. Probably just some new feature they haven't implemented 100% yet.
10-20-2014 12:34 PM
Did you know... SEC Network is an app channel? So is The Weather Channel.
Also, I noticed that my set tops defaulted to On Demand when they rebooted after the upgrade. On Demand may also be implemented as an app channel. This may indicate an issue with the local VHO On Demand service, maybe?
10-20-2014 4:06 PM
Thank you for everyone that has reported this. We apologize about the inconveniences and are investigating it. It appears that the error message is appearing to some, but it should only appear once. Press the Exit button as @Kong57 suggested to get out of it. If you are still having issues, please send a message to us by clicking here. Be sure to include your name, account number, phone number, and the best time to reach you.
AT&T Customer Care
Need help with an account specific question? Post a new question here on the forums by clicking the "Ask a Question" button.
For additional support, please visit us at our AT&T services hub.
Follow us on: Twitter @ATTCares and @DIRECTVService
- edited 10-21-2014 7:33 PM
It looks like there was another update last night or early this morning (10/21 in San Jose, CA area at least) and this problem appears to be fixed.
I could easily reproduce the problem by rebooting my wireless receiver which I always need to do of course when I move it between two TV's in different rooms. I've tried rebooting now at least twice and the problem no longer appears.
I SPOKE TOO SOON - PROBLEM IS NOT FIXED! %$#$#$#@
...I just had to wait a little longer before the message appeared.
10-21-2014 11:17 PM
10-22-2014 9:18 AM
Mine went away for awhile but now it's back. It's more of an annoyance than anything, since it's easy to make disappear. Most everyone I know with Uverse is having the same problem, so I guess eventually it will go away. I don't remember seeing it unitl after the last update.
10-22-2014 11:30 AM
The error message has continued for me as well, and I PMd AT&T Customer Care as David T suggested. A number of posters have mentioned that this problem began after an update, and it occurs to me that I don't think I've gotten a recent update. My version is currently 2.4.29140.22--is there a newer update, or am I actually current? I know that updates roll out over time, so if I don't have it yet, this problem may have nothing to do with the update.
10-22-2014 11:58 AM
docbombay, 2.4.xxx is the new release (came out starting the end of June this year; I just got it a couple weeks ago).
This message is normally associated with the receiver trying to talk to an application server. Have you noticed being tuned to any particular channel when this appears?
10-22-2014 12:32 PM
I have been having the same issue as the OP since the latest update a couple weeks ago. Issue occurs on the DVR and 2 regular boxes. I have hit the exit button to get out of the screen, but there it is again the next time I turn on the TV, nearly every time for the non-DVR boxes. I do not use any apps, and I have left the receivers tuned usually to a local channel when I shut it off.
I'm running 2.4.29140.12