No news is good news. I haven't had a 3038,104 since June 5, and it's June 14. Nine days is enough to conclude that the work done by the remote Norton assistance did solve the problem. The 3038,104 error on June 5 was probably a server-driven error, if that is the case, and those are rare and go away by themselves in a few mintues to a few hours. I'll check in here from time to time to make sure that you know whether the 3038,104 problem is truly solved. I'm not really ready to click the "Solved" button yet, but if you must, the post regarding going to Norton online support and getting remote assistance will exercise people who are familiar with this problem and know how to do things that they can't disclose for security reasons.
↧
