Broadband Tech > Security > Security > Norton Antivirus 2005 Error 3019.6

Norton Antivirus 2005 Error 3019.6

Try this...
Error: "Norton AntiVirus 2004 was unable to scan your computer for infections." (3019,6)

It is for NAV 2004, but may be of some use.
--
WedgeAntilles250

Tom's Rant

reply to Ave8
None of that fixed my problem, thanks for the try though. Is anyone here on WinXP sp2 and using 2005 successfully?

reply to Ave8
AHHHHH!!! There's your problem, you're are using it with SP2. Might have to wait until Symantec comes out with a fix for it.

I have Norton AntiVirus 2005 on Windows XP SP2 and it is running great.

Hi

Also Have Norton Antivirus 2005 on Windows XP SP2, and it is working great!!

reply to Ave8
Okay, thanks for the reports... I suppose I have found myself a task for the weekend then - getting it to work!

reply to Ave8
Well I've got the same problem!! I have NIS 2005 on 4 computers and it works fine on three of them with SP2 installed. But this computer I get the error when I try to do a full system scan?? Virus scan failed, 3019,6. I have went to norton's web site and followed the link to no success also!! Hopefully Symantec will email me a solution. As I have also tried reinstalling.

reply to Ave8
I would look at the install of SP2, instead of the NIS. Uninstall SP2 and run a few malware programs to really clean the machine. Then go and reinstall SP2 and then NIS and see if the problem still exists. SP2 and some Malware causes strange problems. Good luck!
--
Chemistry is better for the living.

reply to Ave8
The Knowledge Base article doesn't address it, but doing a "reset" of NAV Pro 2004 may help. I did it on my copy of NAV Pro 2004 to resolve part of an ongoing 2 year problem with blue screens that I blamed on Zone Alarm and/or NAV Pro 2004, but in retrospect I should have blamed on Dell. Dell (unbeknownst to me) set a custom size for my paging file when it should have been managed by Windows. I've been BSOD free for three weeks now thanks to an IM I received to a thread I created in the Microsoft Forum.

Anyway, refer to the screen print of the options for Norton's Auto Protect. Make sure you are offline when you do this. Uncheck the three checkmarks, click ok. You may have to uncheck them out of order to get them all unchecked. Norton and/or the Windows Security Center may nag you that you are not protected. Ignore the messages for now. Close Norton and reboot. Once rebooted, open Norton and recheck the first three boxes in Auto Protect. Make sure Norton is fully loaded before you recheck the boxes. Again, you may get nagged with the warnings depending on your system. Ignore them. You may have to go to Start > Program Files to open Norton as the Auto Protect icon that sits in the system tray should be gone. Once, you've rechecked the boxes, reboot. Do not try to scan your system before you reboot. Once you've rebooted a second time, then try your scan. I hope this helps.

Owl
--
Rocky is, was, and always will be Dawg E. Dawg. Miss you, pal!

reply to Ave8


Well after hours and hours of trying to figure this out finally got it to do a full scan. Have to go into options and set it not to scan compressed files. I must have a huge file some where on the system that was causing Norton to crash on the scan. Anyway it worked when I did this, now have got to find out which file is causing it.

There shouldn't be any problems with XP SP2, especially with Norton 2005 products.

TheRCRacer: Since you were able to narrow down to compressed files issue, please do let us know which file(s) is causing this. Symantec might need a sample to reproduce and fix this error.

I think someone else posted a similar/same NAV scan error a few weeks ago, but I cannot find it through search. Does anyone remember the thread? I would like to reference it.
--
Ant @ The Ant Farm: »antfarm.ma.cx ... Please do not IM/e-mail me for technical support. Use the forum (I check almost daily)! Disclaimer: The views expressed in this posting are mine, and do not necessarily reflect the views of my employer

reply to Ave8
Well not sure that it's a certain file. Just tried doing a manual scan with scan compressed files and it crashed. Same error, 3019,6......but it don't crash on the same file everytime. Don't know. Did turn scan compressed file option off and it works.

What made me decide to turn the option off for scanning compressed file was one error that I got was 3019,1 which Symantec sent me to this link for it.

»service1.symantec.com/SUPPORT/na···17474506

Did the work around for compressed files and the scan then worked.

reply to Ave8
Have confirmed this problem with NAV 2005 on Windows XP SP1 and Windows 2000 SP3. On Windows 2000 NAV will sometimes crash and sometimes return the 3019,6 error. On Windows XP NAV always returns the 3019,6 error.

This happens when scanning certain compressed files. They don't need to be large. I found one file that is 200K and causes NAV2005 to roll over every time. The only unique characteristics I can find are that this file is self-extracting (.exe) and it was created in 1996 (presumably under DOS). Otherwise there is nothing "wrong" with this file.

I called Symantec Tech Support to find out how to submit this file with a bug report since there is no such information available on the web site. It took a while to convince the person I spoke with that there was no need to get my credit card information since I only wanted to know how to submit a reproducable bug. He said he would send an email with the procedure. That was several days ago and I've received no email since.

As TheRCRacer reported, turn off System> Manual Scan> Scan Within Compressed Files and full system scans will run to completion. Alternately, if you have lots and lots of free time, you can track down the offending files and add them or their host directories as exclusions.

said by CrossingTheBorder:

---

Have confirmed this problem with NAV 2005 on Windows XP SP1 and Windows 2000 SP3. On Windows 2000 NAV will sometimes crash and sometimes return the 3019,6 error. On Windows XP NAV always returns the 3019,6 error.

This happens when scanning certain compressed files. They don't need to be large. I found one file that is 200K and causes NAV2005 to roll over every time. The only unique characteristics I can find are that this file is self-extracting (.exe) and it was created in 1996 (presumably under DOS). Otherwise there is nothing "wrong" with this file.

I called Symantec Tech Support to find out how to submit this file with a bug report since there is no such information available on the web site. It took a while to convince the person I spoke with that there was no need to get my credit card information since I only wanted to know how to submit a reproducable bug. He said he would send an email with the procedure. That was several days ago and I've received no email since.

As TheRCRacer reported, turn off System> Manual Scan> Scan Within Compressed Files and full system scans will run to completion. Alternately, if you have lots and lots of free time, you can track down the offending files and add them or their host directories as exclusions.

---

Same issue, not SP2 related since I am still to install that.

Identified the folder where NAV 2005 generates 3019.6 error, while running a drive scan. Scanned all files inside the folder, no problems. Then scanned the folder itself, get a different error, 3019.1.

said by nVladik:

---

Same issue, not SP2 related since I am still to install that.

Identified the folder where NAV 2005 generates 3019.6 error, while running a drive scan. Scanned all files inside the folder, no problems. Then scanned the folder itself, get a different error, 3019.1.

---

reply to nVladik

said by nvladik:

---

Same issue, not SP2 related since I am still to install that.

Identified the folder where NAV 2005 generates 3019.6 error, while running a drive scan. Scanned all files inside the folder, no problems. Then scanned the folder itself, get a different error, 3019.1.

---

I also have struggled with the error. After several emails back and forth with symantec. I also tried eveything listed above. Thay recomended the following. It worked! I got a full scan.

appears to be due to an installation issue in which the file Wintrust.dll did not get registered. To solve the issue, register the file, please follow the following steps to register it:

Step 1: On the Windows taskbar, click Start > Run.

Step 2: In the Run dialog box, please do the following.(If the file wintrust.dll is not at the location indicated, change the line to use the correct location.)

regsvr32 c:\windows\system\wintrust.dll

Step 3: Click OK.

Step 4: Restart the computer.

I just tried that and it worked. Thanks!