Solved

Exchange 2003/2007 public folder replication issues for one folder

Posted on 2008-10-16
2
1,626 Views
Last Modified: 2012-05-05
Recently brought up an Exchange 2007 server to migrate away from Exchange 2003.  We have about a dozen public folders, all came over fine except one - the most important.  It has about 2000 contact items in it, and the total size is about 3 megs.

Only about 1675 items made it over, and we followed the troubleshooting steps here as closely as possible, but it's tough as this was written before 2007 - http://msexchangeteam.com/archive/2006/01/17/417611.aspx

Anyway, it appears it's a backfill issue as new items appear to sync.  It's just the initial sync that's causing problems.  We turned up diagnositc logging on the 2003 box and receive the following -

Event Type:      Information
Event Source:      MSExchangeIS Public Store
Event Category:      Replication AD Updates
Event ID:      3011
Date:            10/16/2008
Time:            10:21:22 AM
User:            N/A
Computer:      EXCH001
Description:
A replica of public folder (1-7567) IPM_SUBTREE\Public Contacts
 was modified.

 Expiration interval: 0 (0)
 Database "First Storage Group\Public Folder Store (EXCH001)".
 Folder-wide expiration interval: 0 (0)
 Schedule: 2 (2) FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF
 (00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00
)
 Priority: 0 (0)
 Owning information stores added: {0}
 Owning information stores removed:  

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Information
Event Source:      MSExchangeIS Public Store
Event Category:      Replication Outgoing Messages
Event ID:      3018
Date:            10/16/2008
Time:            10:21:31 AM
User:            N/A
Computer:      EXCH001
Description:
An outgoing replication message was issued.

Type: 0x2
 Message ID: <90BBDBCB14F25144A84BDA3D21E2D3D403BE53@exch001.domain.com>
 Database "First Storage Group\Public Folder Store (EXCH001)"
 CN min: 1-3B1B0, CN max: 1-3BE51
 RFIs: 1
 1) FID: 1-7567, PFID: 1-7559, Offset: 28
      IPM_SUBTREE\Public Contacts

 IDCN Deleted:
 {0}
 

For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type:      Information
Event Source:      MSExchangeIS Public Store
Event Category:      Replication Outgoing Messages
Event ID:      3020
Date:            10/16/2008
Time:            10:21:31 AM
User:            N/A
Computer:      EXCH001
Description:
An outgoing replication message was issued.

Type: 0x4
 Message ID: <90BBDBCB14F25144A84BDA3D21E2D3D403BE56@exch001.domain.com>
 Folder: (1-7567) IPM_SUBTREE\Public Contacts

 Database "First Storage Group\Public Folder Store (EXCH001)". CN min: 1-2E861, CN max: 1-2E865
 Message IDs: 1
  1: 1-A841, 1-2E865
--- : Pat Test : 10/16/2008 1:54:42 PM

 MIDSET Deleted:  {0}
 

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Information
Event Source:      MSExchangeIS Public Store
Event Category:      Replication Outgoing Messages
Event ID:      3017
Date:            10/16/2008
Time:            10:21:33 AM
User:            N/A
Computer:      EXCH001
Description:
Outgoing message type 0x10
 Message ID: <90BBDBCB14F25144A84BDA3D21E2D3D403BE5A@exch001.domain.com>
 Folder(s): (1-7567) IPM_SUBTREE\Public Contacts

 Database "First Storage Group\Public Folder Store (EXCH001)".

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Information
Event Source:      MSExchangeIS Public Store
Event Category:      Replication Incoming Messages
Event ID:      3027
Date:            10/16/2008
Time:            10:21:33 AM
User:            N/A
Computer:      EXCH001
Description:
An incoming replication message was processed.

 Type: 0x20
 Message ID: <6C209CD297926B4D87B0FCDF0D53FF29050F60F3@EXCH002.domain.com>
 Database "First Storage Group\Public Folder Store (EXCH001)".
 Folder(s): (1-7567) IPM_SUBTREE\Public Contacts

 Server: /o=Org/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EXCH002/cn=Microsoft Public MDB

For more information, click http://www.microsoft.com/contentredirect.asp.


Event Type:      Information
Event Source:      MSExchangeIS Public Store
Event Category:      Replication Conflicts
Event ID:      3066
Date:            10/16/2008
Time:            10:29:49 AM
User:            N/A
Computer:      EXCH001
Description:
A folder design conflict occurred in public folder (1-7567) IPM_SUBTREE\Public Contacts
 located on database "First Storage Group\Public Folder Store (EXCH001)".
 Users involved in the conflict:
A2E
User1

 Conflict CNs: 1-3BE5C
8-50F6CFC
 

For more information, click http://www.microsoft.com/contentredirect.asp.


The rest of the messages are similar to above, mostly 3021s.  The conflict above is what's making me wonder - we use a utility called Add2Exchange - it syncs (One way, public to private) all of the public contacts to each user's private contacts for Blackberry usage.

I tried to resend changes and sync content (Under status in ESM), no help.  Finally removed the public folder and let everything settle, then readded the replica - same exact thing, same exact number of items sync'ed.  

Ideas?
0
Comment
Question by:dipersp
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 33

Expert Comment

by:Exchange_Geek
ID: 22909584
If PF Replication is causing so much problems - export the PF to a local PST and re-import on the E2k7 box.
0
 
LVL 9

Accepted Solution

by:
dipersp earned 0 total points
ID: 23092163
So we created a new public contact folder on EXCH001 (Exchange 2003) server
and copied and pasted all of the contacts into this folder.  We then enabled
replication to EXCH002 (Exchange 2007), and still had the same issue, but a
different number of contacts came over.

After more digging and research, we found an article that talked about the
pipeline logging - turned this up, and found some errors (Below.)

Microsoft.Exchange.Data.Storage.PropertyValidationException: Property
validation failed. Property =
[{00020329-0000-0000-c000-000000000046}:'Keywords'] Categories
Error = Element 0 in the multivalue property is invalid..
   at
Microsoft.Exchange.Data.Storage.StorePropertyDefinition.ValidateSetPropertyValue(Object
value)
   at
Microsoft.Exchange.Data.Storage.StoreObject.set_Item(PropertyDefinition
propertyDefinition, Object value)
   at
Microsoft.Exchange.Data.Storage.InboundTnefConverter.SetProperty(StorePropertyDefinition
property, Object value)
   at
Microsoft.Exchange.Data.Storage.InboundTnefConverter.PromotePropertyValue(StorePropertyDefinition
property, TnefPropertyReader propertyReader, Boolean allowLargeProperties)
   at
Microsoft.Exchange.Data.Storage.InboundTnefConverter.<CreateRulesTable>b__1(InboundTnefConverter
converter, NativeStorePropertyDefinition property, TnefPropertyReader
reader)
   at
Microsoft.Exchange.Data.Storage.InboundTnefConverter.ParseTnefProperty(TnefPropertyReader
propertyReader, Boolean forceTransmittable)
   at
Microsoft.Exchange.Data.Storage.InboundTnefConverter.ParseMapiProperties(Boolean
forceTransmittable)
   at
Microsoft.Exchange.Data.Storage.InboundTnefConverter.ConvertToItem(TnefReader
reader, InboundMessageWriter targetWriter, InboundConversionOptions options,
ConversionLimitsTracker limitsTracker, String correlationKey, Boolean
isSummaryTnef)
   at
Microsoft.Exchange.Data.Storage.InboundTnefConverter.ParseAttachDataObject(TnefPropertyReader
propertyReader)
   at
Microsoft.Exchange.Data.Storage.InboundTnefConverter.ParseTnefProperty(TnefPropertyReader
propertyReader, Boolean forceTransmittable)
   at
Microsoft.Exchange.Data.Storage.InboundTnefConverter.ParseAttachmentProperties()
   at Microsoft.Exchange.Data.Storage.InboundTnefConverter.ReadAttribute()
   at
Microsoft.Exchange.Data.Storage.InboundTnefConverter.ConvertToItem(TnefReader
reader, InboundMessageWriter targetWriter, InboundConversionOptions options,
ConversionLimitsTracker limitsTracker, String correlationKey, Boolean
isSummaryTnef)
   at
Microsoft.Exchange.Data.Storage.InboundTnefConverter.ConvertToItem(Stream
tnefStream, InboundMessageWriter targetWriter, InboundConversionOptions
options, ConversionLimitsTracker limitsTracker, String correlationKey,
Boolean isSummaryTnef)
   at
Microsoft.Exchange.Data.Storage.InboundMimeConverter.<>c__DisplayClass16.<PromoteTnef>b__10()
   at Microsoft.Exchange.Data.Storage.ConvertUtils.CallCts(Trace tracer,
String methodName, String exceptionString, CtsCall ctsCall)
   at
Microsoft.Exchange.Data.Storage.InboundMimeConverter.PromoteTnef(InboundTnefConverter
tnefconverter, MimePart tnefPart, Boolean isSummaryTnef)
   at
Microsoft.Exchange.Data.Storage.InboundMimeConverter.ConvertToItemInternal(MimePromotionFlags
promotionFlags)
   at Microsoft.Exchange.Data.Storage.ConvertUtils.CallCts(Trace tracer,
String methodName, String exceptionString, CtsCall ctsCall)
   at
Microsoft.Exchange.Data.Storage.InboundMimeConverter.ConvertToItem(MimePromotionFlags
promotionFlags)
   at
Microsoft.Exchange.Data.Storage.ItemConversion.InternalConvertAnyMimeToItem(Item
itemOut, EmailMessage messageIn, InboundConversionOptions options,
MimePromotionFlags promotionFlags, Boolean isStreamToStream)
   at
Microsoft.Exchange.Data.Storage.ItemConversion.ConvertAnyMimeToItem(Item
itemOut, EmailMessage messageIn, InboundConversionOptions options,
MimePromotionFlags flags)
InboundConversionOptions:
- preferredCharset: iso-8859-1
- trustAsciiCharsets: True
- isSenderTrusted: True
- imceaResolveableDomain: domain.com
- preserveReportBody: False
- clearCategories: True
- userADSession:
- recipientCache:
Microsoft.Exchange.Data.Directory.Recipient.ADRecipientCache
- clientSubmittedSecurely: False
- serverSubmittedSecurely: True
ConversionLimits:
- maxMimeTextHeaderLength: 2000
- maxMimeSubjectLength: 255
-  maxSize: 2147483647
- maxMimeRecipients: 12288
- maxRecipientPropertyLength: 2000
- maxBodyPartsTotal: 250
- maxEmbeddedMessageDepth: 30
- exemptPFReplicationMessages: True


In the end, the blank categories as detailed on this page did it.  Hope this
helps someone else!

http://msexchangeteam.com/archive/2008/01/10/447843.aspx
0

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
Find out what you should include to make the best professional email signature for your organization.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

751 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question