Actually, I get a similar Windows error related to f-prot. Something to the
effect of " VDD error: a device attached to your system isn't functioning"
and we aren't running any Symantec products on either of the servers that
get this error. I'll get the exact message when it happens again.
---
>Actually, I get a similar Windows error related to f-prot. Something to the
>effect of " VDD error: a device attached to your system isn't functioning"
>and we aren't running any Symantec products on either of the servers that
>get this error. I'll get the exact message when it happens again.
declude -diag
Mark Chadwick
IT Support Engineer
Science International
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Michael Abbott
Sent: 29 January 2002 16:31
To: [EMAIL PROTECTED]
Subject: RE: DSN:Re: [Declude.Virus] MY Party not caught
I know I hav
For anyone who comes across the Symantec problem I
mentioned, when I opened the registry key mentioned in the KB article, I
found the VDD key contained the SYMEVNT1.DLL file that is mentioned in my
error box. When I deleted and re-created the VDD key with blank content
as directed in the KB (using
