Katie_Clark
asked on
Public Folder Replication Errors
I am receiveing
the following event once daily on all public folder replica servers. They are all Exchange 2003.
Event Type: Warning
Event Source: MSExchangeIS Public Store
Event Category: Replication Errors
Event ID: 3090
Description:
Error 0x80004005 occurred while processing an incoming replication message.
I turned on replication logging. It looks like public folders are replicating. I did notice that the SiteFolderServer is not correct but would that cause this error?
the following event once daily on all public folder replica servers. They are all Exchange 2003.
Event Type: Warning
Event Source: MSExchangeIS Public Store
Event Category: Replication Errors
Event ID: 3090
Description:
Error 0x80004005 occurred while processing an incoming replication message.
I turned on replication logging. It looks like public folders are replicating. I did notice that the SiteFolderServer is not correct but would that cause this error?
ASKER
AV is excluding the /exchsrvr and all subdirectories. It is only configured to scan once a week currently. The stange thing is that the error occurs on all replica servers once daily but each day it increments by 5 minutes.
That is odd.
The problem is, without knowing which folder is triggering the message, it is difficult to go much further.
It might just be a corrupt attachment or similar in a single folder that the replication system doesn't like - perhaps in a folder that doesn't change very often.
Simon.
The problem is, without knowing which folder is triggering the message, it is difficult to go much further.
It might just be a corrupt attachment or similar in a single folder that the replication system doesn't like - perhaps in a folder that doesn't change very often.
Simon.
ASKER
Do you think isinteg would help?
I don't like to run that tool unless I have to. If something goes wrong you loose the database.
Plus, do you know which database you would run the tool on?
Simon.
Plus, do you know which database you would run the tool on?
Simon.
ASKER
That is a good question. I see the replication errors on all replica servers but not on the master. No offline maintenance has ever been run on any of the servers.
If you see the errors on all the replicas, then that would tend to indicate that the problem item is on the master public folder store.
You might get lucky and spot the likely folder by doing an item count comparison. However that is going to be a fishing trip.
I am pretty positive that it is just one single item causing the error, but how to find that item... do the replication logs not give you any clue as to what the error is?
Simon.
You might get lucky and spot the likely folder by doing an item count comparison. However that is going to be a fishing trip.
I am pretty positive that it is just one single item causing the error, but how to find that item... do the replication logs not give you any clue as to what the error is?
Simon.
ASKER
I think I found the folder. Thanks
ASKER
Still getting replication errors on the globalevents folders nightly
Event Type: Error
Event Source: MSExchangeIS Public Store
Event Category: Replication Errors
Event ID: 3079
Date: 4/3/2006
Time: 3:31:37 AM
User: N/A
Computer: Description:
Unexpected replication thread error 0x80004005 on database "SG1\SG1PF1".
EcReplFolderMessagesUnpack
EcReplMessageUnpack
FReplRcvAgent
For more information, click http://www.microsoft.com/contentredirect.asp.
Event Type: Error
Event Source: MSExchangeIS Public Store
Event Category: Replication Errors
Event ID: 3079
Date: 4/3/2006
Time: 3:31:37 AM
User: N/A
Computer: Description:
Unexpected replication thread error 0x80004005 on database "SG1\SG1PF1".
EcReplFolderMessagesUnpack
EcReplMessageUnpack
FReplRcvAgent
For more information, click http://www.microsoft.com/contentredirect.asp.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes it is set to replicate the entire public folder store.
You don't have to replicate everything.
The only things that you have to replicate are the content folders and certain system folders. Some of the system folders are unique to every server and shouldn't be replicated.
Simon.
The only things that you have to replicate are the content folders and certain system folders. Some of the system folders are unique to every server and shouldn't be replicated.
Simon.
Can you see which folder is triggering the message?
Otherwise, make sure that your AV is configured correctly. It should be excluding /exchsrvr and its sub directories for on access and on demand/scheduled scans.
Simon.