MSN messenger 6.2

I was forced to upgrade msn messenger 6.2.0.139 to 6.2.0.205 (the build no may not be exact, but very close). If I didn't upgrade, I just couldn't sign in.
As soon as I upgraded, NIS 2005 popped up a message "Norton Antivirus was unable to start the Instant Messenger scanner. It will be unable to scan Instant Messenger downloads for infections."
I followed the procedures exactly outlined by Symantec to eliminate the problem, but to no avail.
Any input will be very much appecriated.

System Info: Win XP pro w/SP2 and all hot fix. P4 3.2, 1G DDR RAM, 120gSATA HD, ATI 9600pro w/256MB, LAN and sound on ASUS PC800c deluxe MB, LG DVD+/--RW, DVD-RAM

 

Yangor,

What procedure from Symantec did you try?

Steve

 

Well

Symantec document ID:2004102711134006 (12/31/2004)
Solution1 Disable NAV Instant Messenger and then update MSN Messenger
Solution2 Disable NAV Instant Messengerscanning and then configure MSN to use NAV scanner

 

Try updating NAV / NIS.

Steve

 

Sorry I pressed the submit button before I finish posting.
In addition to the mentioned procedure I also tried:

Symnatec document ID: 2003082516003808 (11/01/2004)
How to configure MSN Messenger 6.x to use NAV to scan downloaded files.

Symantec document ID: 1999121613163206 (08/26/2004)
How to run LIveUpdate.

Symantec document ID: 2004110108242406 (11/29/2004)
Disable NAV Instant Messenger scanning to stop the error message.
Uninstall MSN Messenger
Install the latest version of MSN Messenger from MSN.com
Reenable NAV Instant Messenger scanning.

Uninstall and reinstall NIS 2005.

 

That's pretty much all I could find also.

Are you getting the error code (3021,2) in the lower-left corner of the window that pops up? http://service1.symantec.com/SUPPORT/nav.nsf/docid/2003120315224606

One other thing, what was the problem with signing in with the older version and did it begin after installing NIS 2005?

Steve

 

Hi Steve

The error code 3021,4
As I indicated in my post, I have tried all the remedy steps recommended by Symantec.
Response to your second question:
NIS 2005 was installed last year. The sign in problem occurred about 5 days ago.

One more thing I have forgotten to mention was that the error message pops up every 2 minutes no matter what program I am running. Now, I disable the MSN Messenger scanner in order to stop seeing the lovely pop ups.

 

Not sure, but using the above method you shouldn't have to reenable Instant Messenger scanning.

Norton AntiVirus Instant Messenger scanning should be automatically configured.

I guess that is where the problem lies. Let me know if you want to try something else (longshot ) or if your satisfied with it disabled.

Steve

 

Believe me, I tried all the combinations that I can think of including let both MSN Messenger
and NAV automatically configure.
Disable scanning is my final option which is not my preference.

There should be a solution, but we haven't found it out yet.

 

Have a look here, http://service1.symantec.com/SUPPOR...us&ver=2003 Professional Edition&csm=no&tpre=

You may have come across this at some point looking for a solution, but I thought the process of fixing this error before the "update fix" was interesting.

I would try uninstalling MSN Messenger, restart the computer and go by the directions in the link. Maybe doing things in a different sequence or order will fix it for you.

I just found it interesting in the first part of the article (Step 5) that you were instructed to restart your computer after "What instant messengers to protect," uncheck all of the items, and then click OK".

Just uninstall MSN Messenger (restart) and go by the instructions from the start. It's worth a try.

Steve

 

As Matacumbie says

1. Go to http://service1.symantec.com/SUPPOR...on&csm=no&tpre=
and uncheck MSN Messenger

2. Open MSN and follow the instructions on this link
http://service1.symantec.com/SUPPOR...s&ver=2003 Professional Edition&osv=&osv_lvl=

Make sure that the path highlighted in the red box ends at Navw32.exe (exactly as written).

MSN Messenger will then scan any incoming files correctly. This is what I had to do with mine to get it to work. The target was originally Ccimscan.exe.

Hope this helps

 

Thanks guys.

I did what you suggested (not all suggestions at once).
The error message still comes up every two minutes.

I need more HELP.