Symantec aware of problem, but no fix available? 1

[nlm9802]

came up with this error
NAVEVAPI.DLL INTERNAL ERROR SCAN FUNCTIONS RETURNED ERROR >0XC0090081<

according to symantec knowledge base, this is a known issue, but they dont have a fix for it besides uninstall/reinstall, which has been done 3 times.

My question is, has anyone successfully gotten rid of this error?

 

[Ajnin]

What OS or NOS? Please provide feedback, good or bad.
And I'm always open to new suggestions or ideas.

Regards

 

[nlm9802]

nt server 4.0 sp6a
exch 5.5 sp4

 

[nlm9802]

here is a link to what symantec says...

http://service4.symantec.com/support/ent-security.nsf/pfdocs/2000122010054448

 

[wfitz]

I have received a similar message, NAVEVAPI.dll internal error,

Running on NT 4.0, corporate edition 7.x

 

[KavaKicks]

TRY THIS:

http://www.hostile.org/blog/arch/2003_10_12_last.html

Had to run back to the office after our (late) dinner tonite. Damn if all the fun of the evening wasn't temporarily sucked back out of me by Norton Antivirus for Exchange. It was running at 100% cpu and putting out about 8 errors every 10 seconds or so... I timed it. Symantec's Knowledge Base should be called an ignorance base... because it was supremely unhelpful or informative. If, you ever get a buch of warnings about critical failures and internal failures and Scan function returned error and all the stupid codes like 0xc0090090, 0xc0090081 and such-like then your best bet is to ignore their site's useless warnings about USAGE.DAT and move straight on to the real cause.
The virus data might be corrupt says one error message... that is your clue. Now, you'll once again find the documentation supremely unhelpful. It will say things like &quot;Hit the Live Update button&quot; or &quot;Run the Live Update app&quot;. They don't work... it thinks it already got that data. Instead, make room on the overly full drive by deleting useless stuff (In the WinNT directory there are likely a bunch of $ntBLAH folders... delete them since they are backed up DLLs from prior service pack installs that went fine. Once you've done that, hit the &quot;\Program Files\Common Files\Symantec Shared\VirusDefs\&quot; folder and look for your most recent virus definitions folder. It will be a date-titled folder (the name listed in brackets in the USAGE.DAT file in this directory). Rename that file or delete it... THEN hit the LiveUpdate. One huge slurping sound later, you can restart the service and all is fine.

 

[KavaKicks]

I tried the previous message I wrote and it worked for some time. However, it did not completely resolve the problem. We finally came across a new reference to this issue. Basically, if you are running Nav for Exchange as well as Symantec corporat edition, it may be double scanning the Excahnge store. Anyway, boss getting cranky .. gotta go ... read this:

Preventing Norton AntiVirus Corporate Edition from scanning the Microsoft Exchange directory structure

http://service1.symantec.com/SUPPOR...src=ent&pcode=&dtype=corp&svy=&prev=&miniver=

 

[Davetoo]

This is a well known issue.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[xmsre]

C0090081 is a bad thing. That's a spin lock initialization failure. Id say that's a coding issue in the filter driver, to put it mildly. Oh well, if it doesn't leak it hangs.