This may be a forlorn hope and directed to someone who still knows something about NIS 2004 which I still have installed on my Win XP SP3 OS and usually works fine and has done for years. My update subscription expires in May 2009 when I shall probably upgrade to NIS 2009 if it is out by then. What has happened is that during the last definitions update which I manually downloaded on 21st August a new ecmsvr.dll (version 81.2.0.25) file appeared at Program Files/Common Files/ Symantec shared/Virus Defs/ 20080820.16 (this last seems to be the date of issue although on my computer it is shown as created 21st August as above). Since then when trying to open "Quarantine" through the "Reports" facility in NAV 2004 I get the message "Norton Antivirus Quarantine Console has encountered a problem and needs to close". Research shows the faulting application to be as below.
Any ideas how to rectify? The entry below is from the Application Error Records in the Event View. NAV error reports say it is an internal program error also. I can say that the Quarantine Console opened fine before this last definitions update and the rest of NIS 2004 works fine.

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 23/08/2008
Time: 08:43:06
User: N/A
Computer: 043115320582
Description:
Faulting application qconsole.exe, version 10.0.10.13, faulting module ecmsvr32.dll, version 81.2.0.25, fault address 0x00008b3c.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 71 63 6f ure qco
0018: 6e 73 6f 6c 65 2e 65 78 nsole.ex
0020: 65 20 31 30 2e 30 2e 31 e 10.0.1
0028: 30 2e 31 33 20 69 6e 20 0.13 in
0030: 65 63 6d 73 76 72 33 32 ecmsvr32
0038: 2e 64 6c 6c 20 38 31 2e .dll 81.
0040: 32 2e 30 2e 32 35 20 61 2.0.25 a
0048: 74 20 6f 66 66 73 65 74 t offset
0050: 20 30 30 30 30 38 62 33 00008b3
0058: 63 0d 0a c..

As you can see from the above I cannot open the Quarantine window in NAV 2004 reports - I just get the message that there is an internal program problem and an invitation to send to Microsoft which I did.. Is it possible to find a file in Quarantine in any other way to delete it? Can it be reached through Program Files? Hopefully someone will know this if not about what is causing the problem.

Hi imbart:

The same, exact thing is happening to my system. I'm using the same version of NAV, and same operating system.

I've been all over the net, but can't find an email contact address for Norton to report this.

Thanks Joe DS - I feel relieved its not just me. It does seem to be something to do with the last updates (ecmsvr in particular)and like you I find it impossible to contact Symantec - I did find an email contact link in their support site but it didn't work and an old email address I had for them returned my message undelivered. We can only hope someone from Symantec reads this forum. Hopefully the next updates on 27th August will put it right. You and I have discovered it by trying to open the Quarantine Items console but how many other NAV2004 users would bother to do that unless they had a virus. If we are right there must be loads of NAV2004 users unaware of this.

Hi Imbart:

I may have found a "back door" way to notify them. I sent the following message to the feedback page on this site:

https://secure1.symantec.com/discuss/support/feedback2.nsf/internet+services+feedback

-----------------------------------------------------------------------------------------------------------
Could you please provide a jump for registered customers to use to report bugs or glitches associated with the latest virus definitions or associated files updates? I have been all over your website, as well as google, etc., and cannot find anything related to this, other than your technical help page, which of course, charges for correspondence.

In this particular case, for instance, I noticed that since I downloaded the latest definitions on Aug. 20, I can no longer access the "View Quarantine" page. Instead, I receive the following message:

"
Norton AntiVirus Quarantine Console has encountered a problem and needs to close. We are sorry for the inconvenience."



If you are interested, this post string provides a comprehensive description of the problem:

/p1109131-Corrupt_new_ecmsvr_dll_file.html
-------------------------------------

I hate to think that they would charge customers to report software bugs that they have created. (Certainly, there would be legal implications there.)

Thanks for that Joe-DS. Let’s hope we are right and Symantec now pick it up. The file I think is causing the problem is actually the latest ecmsvr32.dll (I missed out the “32” previously) which can be seen in the error report because in the error data shown through the original Microsoft error message stating that the faulting items are qconsole.exe and ecmsvr32.dll I notice a text file is also generated each time the message is shown in the Windows Temporary folder to be sent to them named “(variable figures here each time)appcompat.txt” which suggests some kind of incompatability to me. Let's hope for the best now.

imbart, thanks for bringing this to our attention. Symantec is now researching this as incident 1397537.

Well, I just downloaded the latest virus defs, but still can't access the Quarantine file.

As noted above, the MS Crash Warning indicates the following is involved.
AppName: qconsole.exe AppVer: 10.0.10.13 ModName: ecmsvr32.dll
ModVer: 81.2.0.25 Offset: 00008b3c

A quick check of my HD reveals that the dll file in question is the same one mentioned in the above posts.

File location:

C:\Program Files\Common Files\Symantec Shared\VirusDefs\20080827.038\ECMSVR32.DLL

File Modified: Wednesday, August 20, 2008, 1:00:00 AM

Hopefully, this will be fixed soon. Please keep us posted.

Same here, Joe-DS. Same file ecmsvr32.dll (v.81.2.0.25) downloaded again with the latest updates so we now have it twice:

1. Program Files/ Common Files/ Symantec Shared/ Virus Defs/ 20080820.016/ ecmsvr32.dll (v.81.2.0.25 253KB)

2. Program Files/ Common Files/ Symantec Shared/ Virus Defs/ 20080827.038/ ecmsvr32.dll (v. 81.2.0.25 253KB)

This file (ecmsvr32.dll) which seems to be the problem is described as “Symantec Engine Common Object Model Serve” in “Properties”.

Symantec appears to acknowledge the problem. I tried to access “Incident 1397537” but didn’t get anywhere so I hope we are kept posted here

imbart, I'm sorry that I didn't make it clear previously. The incident number is internal only, you wouldn't be able to find any additional information from public sources about it.

Just to give you a brief update, we are continuing to investigate the issue but may not have a solution for you until next week or latter.

Many thanks reese anschultz. I am grateful for your interest and await the solution which I hope will be a simple one preferably a patch or amended file download to automatically instal as I am not too clever with more complicated solutions.

Reese - Regarding my last post which on reflection sounds a little odd I seem to have got my wires crossed with the word “solution” thinking of things like instructions to edit the registry etc when what I meant to say is that I hope the solution comes silently with the updates.

Hi imbart...
Did you have any luck getting NAV to work with this error?
I am getting the same error messages/warnings...

SK

Same here. Hope this is fixed soon, since this has been going on for over two weeks now. My subscription runs out in October, and while I've generally been satisfied with Symantec, this has me thinking twice.

(Vent) The big issue, for me, is the fact that there have been no announcements on the Symantec site--itself-- that this is a recognized issue and that a solution is currently being worked on--at least I couldn't find anything about it. Customers shouldn't have to turn to third party sites for information about a service they pay for--especially when things go wrong. I don't think it would break the bank if Symantec would put in a "system status" type page--or something that would allow customers to track issues. Along this line, there SHOULD be a provision to allow any customer with an active subscription to report problems/issues via a special email jump directly to Symantec--FREE of charge. (End of Vent.)

SwiftKick and Joe-DS. Symantec are certainly taking their time. The solution hasn't arrived yet. As you say, Joe_DS, it seems this forum is the only place people with this trouble can hope to see progress. I notice ecmsvr32.dll (v. 81.2.0.25) came yet again with the 3rd Sept updates. We have it three times now and it seems to be the problem to me.