Hello edu1404,
It may be best to read the posts in this thread, as there are a few solutions that have helped some of the users here, such as this post - http://community.norton.com/norton/board/message?board.id=nis_feedback&view=by_date_ascending&message.id=40859#M40859
This error can occur for a number of different reasons.
Let us know if any of the solutions in this thread help you!
I’m still out here eager to work with anyone who will help. OscarL offered, but I haven’t heard anything back. I’ve tried all these things in the forum and have given up wasting my time. I agree with the previous poster - 200+ posts about the same issue and no help/solution from Symantec…
bmwpapa, I have left you a Private Message.
Sorry Tim , i'm dont wanted to be unpollite.
i thought about this:
If one people with low knowledge, buy Norton Internet Security 2009 to protect his computer and had this problem , is difficult to obtain an easy solution for that problem.
I'm talking about a normal people, that doesnt have knowledge to solve this....
Sorry again my friend.... but normal people dont want to read 220 post to solve that problem,,,
This people bought's Norton Internet Security 2009 as a solution , don't as problem....
Sorry my poor englhis..
Best regards my friend.
Eduardo
Eduardo is right! Why can’t this be resolved by Symantec?
kram66 wrote:
Eduardo is right! Why can't this be resolved by Symantec?
Because if I remember right, it turns out "Error 3039,1" can have more than one cause., even if you are installing Norton for the first time and happen to be infected in just a small way, before hand.
Or for instance it's because of the leftovers from previous Security Software.......................
Quads
I can't agree with that, Quads. It's not about being fair to Symantec. It's about protecting yourself. That's what we are paying for, year after year.
As for the condition of the system before installation, mine was on a new system before anything else was done.
Verlyn
Well you can agree with what you like, but due to the reason of the Error code having more than one reason for happening, not just one or 2 reasons then how do you expect Symantec to fix the problem. For these 2
If you have without realising Malware in full or part on your PC and try and install Norton and you get that error code, You expect Norton to be able to install and run to remove Malware???? After the fact!
There is Malware that is created to stop Major Security products. If you went from NIS 2008 to NIS 2009, did you completely remove 2008 first.
As for going to Norton from another product brand, say you uninstall AVG, Avast, McAfee, Zonealarm then install NIS and you get the error code after installing NIS. Could be due to not a complete removal of your previous product, registry keys and all.
Do you expect the Products from Symantec to be able to remove your previous product first in it's entireity That is is a lot of company products, a long list.
It is not being fair to Symantec, in the 2 causes above, it's using common sense.................
Quads
Sounds like lazy development! If error 3039,1 can have many causes, then how on hell are we able to understand how and where to look, if this error can mean many things. We pay for a product and expect it to work.
How frustrating can it be for somebody who is not familiar with a PC to find a solution.
In these economic times, if you don't get good service, take your hard earned dollars elsewhere.
Quads, do you work for Semantic.?
kram66 wrote:Sounds like lazy development! If error 3039,1 can have many causes, then how on hell are we able to understand how and where to look, if this error can mean many things. We pay for a product and expect it to work.
How frustrating can it be for somebody who is not familiar with a PC to find a solution.
In these economic times, if you don't get good service, take your hard earned dollars elsewhere.
Quads, do you work for Semantic.?
No I don't Work for them
That is why Most Security company products have removal tools, to removal what is left behind.
I remember I think 5 users getting the error when infected, with I think it was the TDSS variants.
It depends on what you mean by not familiar with a PC, from extreme novice (have to hold their hand just to install) or a Techie.
Quads
Quads,
I understand what you're saying. It can be a daunting task to clean up messes left behind by other products. However, that point is not relevant to the post that immediately preceded yours.
In Message 227, Verlyn wrote:
As for the condition of the system before installation, mine was on a new system before anything else was done.
There was no mess from a previous product.
There was no previous product.
While it may be difficult for Symantec to troubleshoot this, it is their responsibility to do so. It is their product reporting "Error 3039, 1". Their product detected something awry, and reported this error. They should have developers coaching their Support team on what to ask for, what to look for, what to try, etc. to help get to the bottom of this. With 200+ posts on this issue and incredible product dissatisfaction, they should be giving this top priority. Symantec will lose MANY customers over this unless they step up and save the day. I'm willing to give it a try and work with Symantec toward resolution. I was a s/w developer for 10 years, and now manage a s/w dev team. Use me.
BUT... I need Symantec to drive this toward resolution. OscarL contacted me. I provided the requested info. I welcome his response and other Symantec employees to contact me. Look in the code. Tell me what events specifically trigger Error 3039? Help us to help you! Tell us everything you know about this error. Give us special modules that will output debugging info to troubleshoot this. Can you reproduce this in-house? There are a LOT of us out here who can reproduce it for you. Pretend that I'm one of your QA testers in your lab and I've just shown you this critical show-stopping, hold the release, problem. We must fix this now, or we can't ship.
Help me to help you. Be a "man". Acknowledge this problem publicly on this forum as a real problem - a serious problem. Tell us everything you know about this error and things we should look for. Workarounds? Severity? Is it only when SONAR is enabled? Are our computers still being protected?
Looking forward to more private messages...
Looking forward to contacts from people very close to the code, and not Support chats who tell me to reinstall.
I don't think Symantec see the importance of this issue and maybe they think it's only a handful of people that are complaining and we can fix it on our own and go away. However, they don't see the damage their are doing to themselves. If they don't care about trying to resolve the issue, then they don't care about their customers.
This needs to be highlighted higher up the food chain at Symantec, somebody who cares about our problem?
I think that you can see by the activity from OscarL and myself on this thread, that we at Symantec are actively researching this issue. We have solicited the support of others with this problem since we haven't been able to reproduce it in house.
I realize that the thread is long, but a common theme amongst the people that I've dealt with has been that their operating system installation is damaged. Running Component Checker and Windows File Checker (sfc) has revealed these issues. Oscar and I have also provided diagnostic scripts to help us further isolate the source of the problem. Oscar recently has indicated that we are currently attempting to develop ways to repair these broken operating systems.
Reese wrote:
...but a common theme amongst the people that I've dealt with has been that their operating system installation is damaged. Running Component Checker and Windows File Checker (sfc) has revealed these issues. Oscar and I have also provided diagnostic scripts to help us further isolate the source of the problem. Oscar recently has indicated that we are currently attempting to develop ways to repair these broken operating systems.
Reese, can you help me determine if I fall into this same category?
Can you tell me what to run, and how? Where can I get Component Checker and Windows File Checker?
Can you provide me with the diagnostic scripts?
Can you give all of us more details on what triggers Error 3039? What condition does the code actually detect when it reports it?
How much time is Symantec investing in this problem? Daily? How many resources are dedicated to it?
We all want to know the answers to these questions and more. At least, those of us who haven't given up yet... :)
Windows File Checker is built into the operating systems. From a Run or Command Line prompt type "sfc /scannow".
Component Checker can be found on Microsoft's site as MDAC Utility: Component Checker. This doesn't work on Vista though. Note that running this is a two step process, first have it identify which version(s) of MDAC is installed and second, select that version and have it verify that it is intact.
Send me a private message (look for the 
in the upper right hand corner of any community page) with your e-mail address and I will send you the diagnostic script.
The 3039,1 error is generated when the product has detected that the behavioral analysis portion (also known as SONAR) is not running.
I continue to watch this thread, although my problem "appears" to have been fixed. I say "appears" because I suspect that I was directed to a version that may have had the 3039 message disabled. At about ten minutes into a restart I get an error type sound. It's like the donk donk that one hears on the "Law and Order" TV shows, but just a single donk. Didn't happen until the last install.
It's been almost six months since the first report of the problem, with no resolution in sight.
I would expect Symantecs is losing customers over this.
Hello RawRats,
If you're not seeing the error, then your issue should be resolved. I can assure you that we don't disable error messages from showing. Do you have any other indication that this issue isn't resolved for you? The sound you're hearing could be from a number of things that may not be related to the Norton software. You could disable Advanced Protection and see if the sound goes away, to help narrow down the source of the sound.
Let us know if you have any other questions!
RawRats,
What Norton Product and Version do you have (e.g. NAV 2009)?
If you have a 2009 product, but your main UI shows a green check and "Advanced Protection" is enabled, then you no longer have this problem.
I have NAV 2009 version, 16.5.0.134
I already said that I no longer get the 3039 error message.
What I do get, that I didn't get before installing the above version, is an indication that "something" is happening about ten minutes after a reboot. That "something" is a sound that is usually associated with an error of some sort.
Hello,
I now have this same problem. It is exactly as described above though much of this thread. It is now April 3, 2009 and I have been on the phone with Symantec tech for most of the day and all of the night. I have spoken with MANY techs and had many of them take control of my computer to try to fix it themselves. As a matter of fact, I have a supervisor doing so as I type this. The problem is on my Laptop and I am typing this on my Desktop computer. NONE of the techs seem to know a thing about this issue at all. Some actually wanted to argue with me telling me that the Sonar Advance Protection is actually a VIRUS! They were not aware that it was part of the PROGRAM of Norton 36 Ver. 3.0!!! Imagine, I had to repeat over and over in as clear a voice as possible that is IS part of the program! They have also tried to sell me a $99.00 one time service to find my virus, a virus that no one even knows that I have.
When I tell them of this thread or that this is a well known problem, they simply ignore me. I keep getting booted up to the next higher tech, but once I get there, that tech asks me the same stuff over and over and over and then tells me that they are NOT the higher tech! HOURS and HOURS of this, imagine!!!
Can ANYONE steer me in the right direction to fix this problem? I have read where a lot of people are going to never buy Norton again. Well, I have been a VERY long time user and this experience is making me wonder WHY I have stayed with Symantec! HELP!
Oh, now the guy is going to step me backwards to version 2.0 to see if that works. He just told me that his supervisor (there seems to be NO limit on the higher chain of command in India) is telling him that this error 3039 problem is "Under Investigation" . I mentioned to him that from what I can see on this thread, it has been under investigation for MANY years now! I hope that I live long enough to see it resolved!