I am trying to finish migrating public folders from an Exchange 2003 SP2 system to an Exchange 2007 SP1 system. I have migrated most of the folders. If you look in the 2003 ESM, it shows nothing under Public Folders but when you look at Public Folder Instances, some have hung around. I have tried to Move All Replicas and have discovered that Folder Content Backfill Responses from the old server to the new one are failing once they get to the hub server with status:554 5.6.0 STOREDRV.Deliver; Corrupt message content554 5.3.4 STOREDRV.Deliver; Content Conversion limit(s) exceeded554 5.6.0 STOREDRV.Deliver.Exception;PropertyValidationException; Failed to process message due to a permanent exceptionMost of the errors are the Corrupt message content. I have tried hot fix KB93600 on the Exchange 2003 server. I have run eseutil /d and isinteg -s servername -fix -test alltest until there were no errors. Nothing seems to get the rest of this content to move properly. I can't decomm the server until it is all done.Micah

On Wed, 14-Oct-09 14:34:55 GMT, mjbsn wrote:>I am trying to finish migrating public folders from an Exchange 2003 SP2 system to an Exchange 2007 SP1 system. I have migrated most of the folders. If you look in the 2003 ESM, it shows nothing under Public Folders but when you look at Public Folder Instances, some have hung around. I have tried to Move All Replicas and have discovered that Folder Content Backfill Responses from the old server to the new one are failing once they get to the hub server with status:>>554 5.6.0 STOREDRV.Deliver; Corrupt message content554 5.3.4 STOREDRV.Deliver; Content Conversion limit(s) exceeded>554 5.6.0 STOREDRV.Deliver.Exception;PropertyValidationException; Failed to process message due to a permanent exception>>Most of the errors are the Corrupt message content. I have tried hot fix KB93600 on the Exchange 2003 server. I have run eseutil /d and isinteg -s servername -fix -test alltest until there were no errors. Nothing seems to get the rest of this content to move properly. I can't decomm the server until it is all done.What Rollup have you installed on the E2K7 server(s)?Have you created any additional Receive Connectors in Exchange 2007?Does it listen on an internal IP address and NOT allow authentication?You can also jack up the logging on public folder replication and seeif there's more information in the applications log.These might help, too:http://msexchangeteam.com/archive/2006/01/17/417611.aspxhttp://msexchangeteam.com/archive/2006/01/19/417737.aspx01/23/417974.aspxhttp://msexchangeteam.com/archive/2008/01/10/447843.aspx---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

Thanks for your reply. To answer your question I am running Exchange 2007 SP1 Rollup 9After I posted...I found the exact articles that you mentioned. I do have an additional receive connector which I believe was contributing to the access denied problems as well as the quota limit exceeding. I think I fixed that issue.However, the following error still exists:Microsoft.Exchange.Data.Storage.ConversionFailedException: Message content has become corrupted. ---> Microsoft.Exchange.Data.Storage.ConversionFailedException: Content conversion failed due to corrupted TNEF (violation status: 0x00000800)In message tracking it looks like:554 5.6.0 STOREDRV.Deliver; Corrupt message contentI have already applied the hotfix found in KB936000 but, it doesn't seem to fix the issue. Any other suggestions?Micah

Pf replication is about as fun as a trip to the dentist! If you are running AV on the HTs, they may drop pf replication messages as well. Disable during replication and test. If cant get a folder to replicate and get the item counts to match, export it to a pst from the 2003 server in Outlook -- using an account that has its default public folder store set to the 2003 pf store , then reimport with Outlook using an account that has its default public folder store set to the 2007 pf store.

On Wed, 14-Oct-09 22:41:04 GMT, Andy David wrote:>>>Pf replication is about as fun as a trip to the dentist! The dentist, these days, is less painful than dealing with PFreplication problems.>>If you are running AV on the HTs, they may drop pf replication >messages as well. Disable during replication and test. If you're using ForeFront on the E2K7 HT servers:Key (all on one line):HKLM\SOFTWARE\Wow6432Node\Microsoft\Forefront Server Security\ExchangeServerSpecifies whether to scan IPM replication messages. The Transport ScanJob scans files called Winmail.dat for viruses. Exchange uses thesefiles for several purposes, including facilitating replication betweenservers (IPM replication messages). If FSE modifies a Winmail.datfile, the public folder replication process will fail. Setting thisDWORD registry key to 1 prevents the Transport Scan Job from scanningIPM replication messages. If a virus is replicated because of publicfolder replication, the Realtime Scan Job will still detect the viruseven if this key is set.I forget if there's a similar key on the older Sybari AntiGen productfor E2K3.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP