Log Name: Application Source: MSExchangeIS Public Store Date: 12/15/2010 12:00:30 PM Event ID: 3092 Task Category: Replication Errors Level: Warning Keywords: Classic User: N/A Computer: kdmpEXCH01.kpcb.com Description: Error 1129 occurred while processing a replication event. Folder: (6-13) NON_IPM_SUBTREE\StoreEvents{E5583E80-E8CB-454C-A842-CC2C0FD820D9}\globalevents Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="MSExchangeIS Public Store" /> <EventID Qualifiers="32797">3092</EventID> <Level>3</Level> <Task>29</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2010-12-15T20:00:30.000Z" /> <EventRecordID>11405975</EventRecordID> <Channel>Application</Channel> <Computer>kdmpEXCH01.kpcb.com</Computer> <Security /> </System> <EventData> <Data>1129</Data> <Data>(6-13) NON_IPM_SUBTREE\StoreEvents{E5583E80-E8CB-454C-A842-CC2C0FD820D9}\globalevents </Data> </EventData> </Event> I have two exchange servers. I went to this PF and looked at the replication tab and only the one exchange server is listed there. How do I get rid of this error?

Also, if I Update Content this is the error: -------------------------------------------------------- Microsoft Exchange Error -------------------------------------------------------- Action 'Update Content' could not be performed on object 'StoreEvents{480B2B52-3E8A-4872-BEBE-EE52E7A7FF3F}'. StoreEvents{480B2B52-3E8A-4872-BEBE-EE52E7A7FF3F} Failed Error: Cannot start content replication against public folder '\NON_IPM_SUBTREE\StoreEvents{480B2B52-3E8A-4872-BEBE-EE52E7A7FF3F}' on public folder database 'kdmpEXCH01\PF\PF'. MapiExceptionNoReplicaAvailable: StartContentReplication failed. (hr=0x80004005, ec=1129) Diagnostic context: Lid: 1494 ---- Remote Context Beg ---- Lid: 31229 Error: 0x0 Lid: 9206 StoreEc: 0xFFFFF9BF Lid: 19865 StoreEc: 0x469 Lid: 27225 StoreEc: 0x469 Lid: 1750 ---- Remote Context End ---- Lid: 26322 StoreEc: 0x469 -------------------------------------------------------- OK --------------------------------------------------------

Hi Kanien, Which version of exchange do you use? Are all the exchange servers in the same sites? Please check did you update the kb refer to below: http://support.microsoft.com/kb/936000 And then, run isinteg to check integrity/health of public folder database, probably there is integrity issue on database level. Hope this helps. If the issue still existed, please tell us. Regards! Gavin TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I'm trying to run isinit on the database after dismounting it and I can't seem to get it to work. I know I must be doing something extremely stupid... my exchange server is exch01 and my command syntax is isinteg -s exch01 -fix but all it does is spit out the default help information as if I ran isinteg -? instead of attempting to integrity check the information store.

On Mon, 20 Dec 2010 20:30:58 +0000, Kanien wrote: > > >I'm trying to run isinit on the database after dismounting it and I can't seem to get it to work. I know I must be doing something extremely stupid... > >my exchange server is exch01 and my command syntax is > >isinteg -s exch01 -fix > >but all it does is spit out the default help information as if I ran isinteg -? instead of attempting to integrity check the information store. If you look at that help text you'll see that the "-test testname[[,testname]...]" is a mandatory parameter. Add "-test alltests" to your command line. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Kanien, Other information for you: http://support.microsoft.com/kb/301460 Regards! Gavin TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I ran isinteg here is the output P:\Program Files\Exchange>isinteg -s kpmpexch01 -fix -verbose -l logfile.log -t d:\database\pf.edb -test alltests Databases for server kpmpexch01: Only databases marked as Offline can be checked Index Status Database-Name Storage Group Name: PF 1 Offline PF Storage Group Name: SG01 2 Online S01DB01 Storage Group Name: SG02 3 Online S01DB02 Storage Group Name: SG03 4 Online S01DB03 Storage Group Name: SG04 5 Online S01DB04 Storage Group Name: SG05 6 Online S01DB05 Storage Group Name: SG06 7 Online S01DB06 Storage Group Name: SG07 8 Online S01DB07 Storage Group Name: SG08 9 Online S01DB08 Storage Group Name: SG09 10 Online S01DB09 Storage Group Name: SG10 11 Online S01DB10 Enter a number to select a database or press Return to exit. 1 You have selected PF / PF. Continue?(Y/N)y Test Categorization Tables result: 0 error(s); 0 warning(s); 0 fix(es); 0 row(s) ; time: 0h:0m:0s Test Restriction Tables result: 0 error(s); 0 warning(s); 14 fix(es); 0 row(s); time: 0h:0m:0s Test Search Folder Links result: 0 error(s); 0 warning(s); 0 fix(es); 0 row(s); time: 0h:0m:0s Test Global result: 0 error(s); 0 warning(s); 0 fix(es); 1 row(s); time: 0h:0m:0 s Test Delivered To result: 0 error(s); 0 warning(s); 0 fix(es); 6 row(s); time: 0 h:0m:0s Test Repl Schedule result: 0 error(s); 0 warning(s); 0 fix(es); 0 row(s); time: 0h:0m:0s Test Timed Events result: 0 error(s); 0 warning(s); 0 fix(es); 0 row(s); time: 0 h:0m:0s Test reference table construction result: 0 error(s); 0 warning(s); 0 fix(es); 0 row(s); time: 0h:0m:10s Test Folder result: 0 error(s); 0 warning(s); 1 fix(es); 127 row(s); time: 0h:0m :11s Test Deleted Messages result: 0 error(s); 0 warning(s); 0 fix(es); 0 row(s); tim e: 0h:0m:0s Test Message result: 0 error(s); 0 warning(s); 0 fix(es); 44320 row(s); time: 0h :0m:16s Test Attachment result: 0 error(s); 0 warning(s); 0 fix(es); 5307 row(s); time: 0h:0m:0s Test Per-User Read result: 0 error(s); 0 warning(s); 0 fix(es); 120 row(s); time : 0h:0m:0s Test Replication result: 0 error(s); 0 warning(s); 0 fix(es); 36 row(s); time: 0 h:0m:0s Test Message Tombstone result: 0 error(s); 0 warning(s); 0 fix(es); 3 row(s); ti me: 0h:0m:0s Test Folder Tombstone result: 0 error(s); 0 warning(s); 0 fix(es); 1 row(s); tim e: 0h:0m:0s Now in test 17(reference count verification) of total 17 tests; 100% complete. I'm still getting Log Name: Application Source: MSExchangeIS Public Store Date: 12/22/2010 11:24:21 AM Event ID: 3092 Task Category: Replication Errors Level: Warning Keywords: Classic User: N/A Computer: KPMPEXCH01 Description: Error 1129 occurred while processing a replication event. Folder: (7-13) NON_IPM_SUBTREE\StoreEvents{480B2B52-3E8A-4872-BEBE-EE52E7A7FF3F}\globalevents

Hi kanien, Could you please post what version for exchange you use? Per the cmdlet you run to fix Logical Corruption on the database, and the logs, it seems good, did you reboot the server or the IS service to make a test? We also could use "isinteg -s servername -test replstate -fix" to make a test again. If the evenlt log still exist, seems some issue with the edb file, I would use the eseutil /p and eseutil /d to repair and defragement the DB, and then mount the db again and make a test. Per the event log, the issue caused by that folders table in the source database was out of sync. The final method I would do is:Removed the other replica (other than the source) via PFMC, then added it back. Regards! Gavin TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, This problem occurs when messages in the Exchange Server 2003 public store include date properties that are set to zero. When date properties are set to zero, the date is displayed as Jan 1, 1601 in Exchange Server 2003. When the server that is running Exchange Server 2007 replicates the public folder that includes these messages, the replicated messages contain random data in the date properties. Therefore, Exchange Server 2007 determines that these messages are invalid, and it drops them. for referance : http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=6.5.6940.0&EvtID=3092&EvtSrc=MSExchangeIS+Public+Store&LCID=1033Dinesh S.

I stopped receiving the errors after doing the isinteg check and deleting and recreating the /globalevents.