Question Locked

Exchange Error 0x80004005 with Duplicate Logons in Exchange

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

About a month ago my exchange server crashed. After we got it up and running everyone started getting the following error when attempting to run a send/receive:

"error 0x80004005 'the operation failed' 2003"

I have noticed that in the Exchange System Manager on my server that everyone, with the exception of one person who started after the incident, has a duplicate or triplicate entry in the Servers>First Storage Group>Public Folder Store>Logons

The individual who only has one entry does not receive the error while everyone else does. Also, this is affecting the users ability to edit/open shared calendar entries.

Any thoughts?

4 replies

by Former member

CAUSE
This issue may occur if you are using Norton AntiVirus with the script blocking feature enabled.

RESOLUTION
To resolve this issue, visit the following Symantec Web site to obtain either an updated version of Norton AntiVirus or to receive help with the reconfiguration of Norton AntiVirus:
http://www.symantec.com/support (http://www.symantec.com/support)

WORKAROUND
To work around this issue, use one of the following methods:

Method 1: Disable Script Blocking in Norton AntiVirus
Warning This workaround may make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.
In Norton AntiVirus, turn off the "Enable script blocking" feature.

For more information about how to do this, view your product documentation or contact Symantec Corporation.

Please post back if you have any more problems or questions.

by bibomaria

Hi !
When you try to download the offline Address Book in Microsoft Outlook, the offline Address Book may not be downloaded successfully. That time exchange server generate this type of errors. TO solve this problem you can use Kernel software that is very effective and powerful. you can find it at:: www.exchangemailboxrepair.com

This discussion is closed to new replies.