What you need to do is throw Norton Antivirus 2007 out the friggin' window!
At the very lease, you need to fully uninstall it, then re-install it
WITHOUT any email scanning components whatsoever. Rule number one, ALL
email scanners are incompatible with Windows Mail and every other email
client know to modern man. It is in the nature of the way they must work
that there WILL be problems sooner or later; it's not an "if", but a "when".
In this case, you'll need to get the Norton removal tool because the
uninstaller (like most everything else Symantec makes) is broken and doesn't
completely remove the product. Once removed, re-install without any email
Download and run the Norton Removal Tool http://www.oehelp.com/OETips.aspx#3
3. Turn off email scanning in your antivirus software. http://support.microsoft.com/KB/951805
Stop error message when you send or receive e-mail messages on a Windows
Vista-based computer that has e-mail scanning software installed: "STOP:
Hal Hostetler, CPBE -- hhh@xxxxxx
Senior Engineer/MIS -- MS MVP-Print/Imaging -- WA7BGX http://www.kvoa.com
-- "When News breaks, we fix it!"
KVOA Television, Tucson, AZ. NBC Channel 4
Live at Hot Licks - www.badnewsbluesband.com
"Loosinmymind" <Loosinmymind@xxxxxx> wrote in message
> Hi, Can someone please help me. Whenever I send out an email with a
> or any kind of attachment including word documents through Windows mail,
> says the email was sent, but it isn't being recieved by the recipient.
> get a Norton symantec pop up saying this problem does not occur often,
> support team have not been able to reproduce the error, and it also says
> the error message is actually caused by a problem on the cpu itself. When
> clicked the "run it now" button to run a Symantec administrative tool it
> states that I must be logged into an administrative account to complete
> action, but I am! The only info it gave was this: Module 1003, Error ID 9,
> Build Symantec. I have Norton Antivirus 2007 and I ran a full scan and I
> don't have a virus. I'm about to throw this cpu out the friggin' window!
> there anyone out there who knows why it's doing this? My last resort is to
> bring it in to the geek squad to see if they can fix it.