Error 004 showing up on Vip622

imranp128

Member
Original poster
May 11, 2009
7
0
TExas
So Dish network recently came and setup the system. Two of the receivers working fine, but one of them gives me error 004, but it also only seems to happen in the night/ evening hours. This doesnt happen on the other receivers and they get a good signal on all the satellites. Does anyone Know what the problem could be? I know that it is a Dpp44 switch, im beginnign to think its a problem with the switch. any help would be appreciated!
 
My 622 does this sometimes. Were you able to change channels and then change back to make it go away? If so, it's nothing to worry about except it does mess up recordings and buffers.

It doesn't hapen to me often, and I always attributed it to all the new sats and HD. You might be more ambitious and let tech support know about it.
:welcome
 
I've been having the exact same thing happen on my 622 for about the past 2 months. Usually once a day and usually during evening or late nite hours. When it occurs on mine....... it does it twice in a row, meaning i have to click ok twice to get it to return to the original program. I've tried a hard reboot but to no avail. Sure does get frustrating.
 
Yeah it really gets annoying, except my error message just doesnt want to go away. During the day there are no problems whatso ever. I really dont want to call dish network again to come fix this.... AHHH
 
Having that problem here lately, too. Just every once in a while, but it also seems to be in the evening. I can get out of the error pop-up, and the buffer continues to record while the error is on the screen, so nothing appears lost while the message is on the screen. And both my 622 and power inserter are plugged into a surge protector (has to be for now).
 
I had a similar problem and it turned out to be a faulty switch.

Switch the cables running out of the DPP44 so the cable running to one of the working receivers is now connected to the port that the receiver that is giving you problems was hooked to.

Example:

Current:
Port#1 - VIP622 (Family Room - Trouble receiver)
Port#2 - VIP622 (Bedroom - works fine)
Port#3 - VIP211 (Basement - works fine)

Switch to:
Port#1 - VIP211
Port#2 - VIP622
Port#3 - VIP622 (troubled receiver).

Then do a check switch on all receivers. If the problem occurs again on the same receiver, it could be a receiver problem. If the problem now shows up on the VIP211, it could be a switch problem.
 
I get the same problem with two 612s, but not the 722. It usually happens at about 6:30 AM. Have replaced the DPP44, but that did not fix it. In my case, both 612s error at the same moment--even though they are tuned to different programs on different satellites.:confused:
 
Just hear back from Dish technical folks:

"We have identified the problem you are experiencing and have a solution in progress. The fix is currently being tested by our validation group and is scheduled to go public mid-June."

:up
 
I have 2 persistent problems (error codes not handy):
(1) the recorder will say in the middle of a view/recording that I am not authorized although I have been watching that channel and can come back to it. I think it is checking some OTA channel on the 3rd tuner. This started recently, possible after a new card on a refurb 722 but I think also on a 722 that did not need a card update.
(2) I still have the recorder saying that it was stopped by User 1 at 4:12 or 4:13 AM MST/MDT. As this has happened dozen times or more, I am getting annoyed especially for shows that only are available about once a year at one time. No, the remote address is a high number and is not likely to be found in anyone else's and it does not happen at any other time. No, this is not the reset time.

-Ken
 
So this is a problem that a lot of dish network custoemrs are having? one of the tech guys at dish told me that it was a grounding problem, since it happens in the evening. Im not really sure ehat that means. But i can tell u this is gettign really annoying!
 
So this is a problem that a lot of dish network custoemrs are having? one of the tech guys at dish told me that it was a grounding problem, since it happens in the evening. Im not really sure ehat that means. But i can tell u this is gettign really annoying!

Dish just confirmed for me that it is a software problem. They hope to have a fix out next month.
 
I talked to them last night, and they didnt mention anything about a software update. Im thinking that at night the switch just isnt receiving enough power from the power inserter for whatever reason. I wonder if adding another power inserter to the trouble receiver will solve the problem....
 
I don't think you should need more than 1 in-line power source for a DPP44 now would a second one help. Just make sure you are powering input 1 of the DPP44. The receivers can power a switch for a while but this will hurt them. IIRC this is a 6"x10"x2" box with the connectors on the smallest ends.
-Ken
 
I talked to them last night, and they didnt mention anything about a software update. Im thinking that at night the switch just isnt receiving enough power from the power inserter for whatever reason. I wonder if adding another power inserter to the trouble receiver will solve the problem....

CSRs are not yet informed. I am working with senior folks at Dish on this. It is not your DPP44 (or mine), it is a Dish software issue that they are working very hard to fix. Don't drive yourself crazy trying to fix what is not your problem.
 
i mean its just that i dont see anyone else really having this problem, and if it was software wouldnt anyone with a 622 be having the same problems as me?? and i mean its keeping me from watching my channels in the evening. Seems to be a bigissue for dish to be taking a backseat trying to figure out a bug in the software. Unless it was everyone with a 622, its hard to believe. I just wanna replace the switch and see if it fixes the problem
 
Trust me on this. I replaced the DPP44 switch without success before bringing up the issue with senior Dish management at the SatelliteGuys Meet and Greet in Denver last weekend. Those present had not heard of the problem, but told me to email them the particulars--which I did on Monday. An engineer got back to me the same day saying that they had found the problem and over time it will impact all (MPEG4?) DVRs. At first it was only hitting my two 612s, but has recently also hit the 722. They said they know for certain what the issue is, and that it is software. The fix is being tested now and should be out in a release in June.
 

Users Who Are Viewing This Thread (Total: 0, Members: 0, Guests: 0)

Who Read This Thread (Total Members: 1)

Top