RE: Norman Engine broken in new build
|
Logged in as: Guest
|
|
Users viewing this topic:
none
|
|
Login | |
|
RE: Norman Engine broken in new build - 21.Apr.2004 11:44:00 AM
|
|
|
spearson
Posts: 2
Joined: 20.Apr.2004
Status: offline
|
I'm having the same problem: "Norman files was successfully downloaded. But a failure occured when updating local engine files."
I tried http://kbase.gfi.com/showarticle.asp?id=KBID001630
My autodown.txt file lists: 2004-04-21,07:54:08,921,0,"#0000169c","#000002bc","error ","autodown","Failed to exclusively open file 'C:\Program Files\GFI\MailSecurity\\AntiVirus\Nvc\Nse\NSE_W32.DLL'. Err=32"
|
|
|
|
RE: Norman Engine broken in new build - 30.Apr.2004 12:51:00 PM
|
|
|
mmiller@virtual-mis.com
Posts: 15
Joined: 15.Apr.2004
From: Portland, OR
Status: offline
|
I finally manually copied the Norman files from the Norman Autoupdate directory to the NVC directory. Autoupdates now appear to be occuring and I have not seen any more errors.
Matt
|
|
|
|
RE: Norman Engine broken in new build - 17.Jun.2004 5:17:00 AM
|
|
|
Chaoszwerg
Posts: 45
Joined: 6.Jan.2004
From: Germany
Status: offline
|
must you stop that service for manual replacement?
|
|
|
|
RE: Norman Engine broken in new build - 17.Jun.2004 11:58:00 AM
|
|
|
denismac
Posts: 37
Joined: 2.Dec.2003
From: Oregon
Status: offline
|
Oliver, Yes, services must be stopped. See GFI's article on manually updating definition files. KBI001528
|
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|