We had a few end-users who experienced this error after a head end upgrade to 4.10.01075. What corrected it for us on 1 occasion was have the enduser restart all ISP network equipment at their house. In two instances where that didn't correct it we p...