event ID 3092 Public folder replication errors
- From: Marcus Bentley <MarcusBentley@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 31 Jul 2007 02:18:27 -0700
All my servers are 2003 SP1, and Exchange is 2003 SP2, with all patches to
around 1 month ago.
I did a removal of an Exchange server that was a mailbox and public folder
server.
I followed the KB article 822931, removing first Exchange Server 2003 from
the administrative group.
This was essentially an upgrade migration, so I used the native Move Mailbox
tool to move mailboxes to the new server.
I added the new server as a replica for all public folders, user and system
ones such as address books, etc.
I left it a week as I was in no rush, then I removed the server to be
decomissioned from the public folder replica list.
Once this was complete I checked the contents of the 'public folders' from
within the PF store on the ESM, and it only had a handfull of public folders
that were only locally relevant, like the store events folders.
All my mailbox databases were empty so I began deleting all these, and
deleted storage groups as they became empty.
I then deleted the PF store.
Everything has been working perfectly for users, no reports of loss of data
within public folders. The PF EDB is about 6 GB so it is used.
I also did all the rest of the steps, such as moving roles, moving RUS, etc.
as per the KB.
But since I fully removed the legacy Exchange Server, despite there being no
functional problem I am getting these Event ID 3092 errors popping up every
15 mins in the application logs, like the one below.
Event Type: Warning
Event Source: MSExchangeIS Public Store
Event Category: Replication Errors
Event ID: 3092
Date: 31/07/2007
Time: 09:53:56
User: N/A
Computer: PWGSREX047936
Description:
Error 1129 occurred while processing a replication event.
Folder: (a-1ADCB) IPM_SUBTREE\MSU Alpha Trial
I have run through the process using isinteg as per KB889331 for backfill
requests never completed. As I am Exchange SP2 I did not need the hotfix
suggested, simply to run the commandlines for isinteg.
isinteg -s server_name -test replstate, and the fix command
This has not helped.
Can anyone suggest where I go from here as I am getting around 300 of these
errors every 15 mins, so when I do get a problem with exchange it is
extremely dificult trying to find relevant events in the log.
Thanks for any suggestion,
Marcus.
.
- Prev by Date: Can you configure OWA 2k3 to automatically login?
- Next by Date: Re: Restrict outgoing message size per domain
- Previous by thread: Can you configure OWA 2k3 to automatically login?
- Next by thread: Re: Keep getting a 0X8004010F message
- Index(es):
Relevant Pages
|
Loading
