Re: Public folder replication 5.5 -> E2K3 not working correctly

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Nicholas Basile\(MSFT\) (nicbas_at_online.microsoft.com)
Date: 05/21/04 

Date: Fri, 21 May 2004 07:11:07 -0400

This trick may help. I have found it to be successful in times when 5.5
folders get rehomed before content actually arrives. Se if it will help
you.
Confirm that there are replicas on both the 5.5 and the 2003 server.
Connect with a client, open the folder in question with Outlook. Select
Edit, Select Copy, Select Paste.
This will duplicate every message/post in the folder, and leave the
originals highlighted at that time. Select Delete. You will delete all the
original items, but still have copies with new timestamps. See if it works. 

-- 
Nicholas Basile(MSFT)
nicbas@online.microsoft.com
Microsoft PSS
Please do not send email directly to this alias is for newsgroup purposes
only!.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Charlie Kaiser" <nospam@nospam.com> wrote in message
news:%23NOfVlGPEHA.1160@TK2MSFTNGP09.phx.gbl...
> I've been searching newsgroups and Google all day and found numerous
> references to this problem, but no causes or solutions.
> Here's the scenario:
> I'm seeing an odd behavior in my E2K3 test implementation. Lab is 2 W2K3
> DCs, 1 Exch 5.5 server, 1 E2K3 server. Restored 5.5 IS to test lab server.
> (same org/site name, didn't join org; usual recovery server scenario)
Built
> second box to E2K3.
> I got E2K3 up and running fine, was able to move mailboxes and access
mail,
> got OWA running, and used PFMigrate to create PF replicas from my Exch 5.5
> server.
> All of my PFs replicated successfully except for one, the one with the
most
> data in it. It's got 950 items, about 177 mb of info.
> The folder replicated, but none of the data in it. It shows up on my E2K3
> server as 0 items, 0 kb. I have removed and recreated the replica several
> times, cranked up replication logging, and don't see much that indicates
an
> error (more on that in a bit).
> If I delete the replica from the E2K3 box, I can connect to the PF from
> outlook and see all the messages (incoming emails with .tif attachments).
If
> I set up the replica, I don't see any messages. I added another post to
the
> PF and it posted OK, and I was able to reply to it successfully, so I know
> mail is flowing OK to and from that folder. Once I sent the new message,
> then recreated the replica, I can see the new post in the replica, but
none
> of the pre-existing messages. I've tried sending the replication request
> messages as per Q321082. No help.
> I've tried creating the replica with PFMigrate, manually from the 5.5
> server, and manually from the E2K3 server. I've got replication set to
> always. When I created the replica initially, full replication of all
other
> PFs took about 5 minutes. (I only have about 20 PFs) I let the replication
> spin over the weekend with no change. This is the only PF with the issue.
> The email addresses for the PF on both servers match. The PF is listed in
> the AD Exch system objects folder. I've done a send hierarchy and send
> contents, although I didn't expect that to work since the send is from the
> E2K3 box to the Exch 5.5 box.
> Now, when I cranked up logging, I found a couple of replication messages,
> but can't figure out what they're telling me yet. The first, which I get
> after a "send hierarchy" command,  is a 3019 message with the following
> info:
>
> ************
> An outgoing replication message was issued.
>
>  Type: 0x80000002
>  Message ID: <6A39E548EDF5BF40AAF1B5EB72837870A521@<E2K3
> servername>.<domainname>.COM>
>  Database "First Storage Group\Public Folder Store (<E2K3 servername>)".
>  CNSET: 1-669C,1-A51D
> 2-FFFFFFFF0002,2-FFFFFFFF0004
> 5-485A,5-9BFF
> c-9,c-B
> d-9,d-1FC5
>
>  CNSET(FAI): {0}
>
>  RFIs: 45
>   1) FID: 2-FFFFFFFF0003, PFID: 1-1, Offset: 988
>  IPM_SUBTREE\Internet Newsgroups
> 2) FID: 8-5674, PFID: 1-1, Offset: 1988
>  IPM_SUBTREE\Temp1
> 3) FID: 8-5671, PFID: 1-1, Offset: 3001
>  IPM_SUBTREE\IT
> 4) FID: 8-1B65, PFID: 1-1, Offset: 4282
>  IPM_SUBTREE\Seattle_Contacts
> 5) FID: 8-1B64, PFID: 1-1, Offset: 5522
>  IPM_SUBTREE\efax
> 6) FID: a-A837, PFID: 1-1, Offset: 6825
>  IPM_SUBTREE\Good Luck
> 7) FID: b-A035, PFID: 1-1, Offset: 8201
>  IPM_SUBTREE\Contacts
> 8) FID: b-4278, PFID: 1-1, Offset: 9478
>  IPM_SUBTREE\ECC Contact List
> 9) FID: 5-331B, PFID: 8-1B64, Offset: 10667
>  IPM_SUBTREE\efax\NY Dealers
> 10) FID: a-A838, PFID: a-A837, Offset: 11978
>  IPM_SUBTREE\Good Luck\Contacts
> 11) FID: a-A839, PFID: a-A838, Offset: 13435
>  IPM_SUBTREE\Good Luck\Contacts\LOS ANGELES COUNTY CONTACTS
> 12) FID: a-18AAB, PFID: a-A838, Offset: 14926
>  IPM_SUBTREE\Good Luck\Contacts\MELISSA'S CONTACTS
> 13) FID: a-A83B, PFID: a-A838, Offset: 16390
>  IPM_SUBTREE\Good Luck\Contacts\ORANGE COUNTY CONTACTS
> 14) FID: a-A83D, PFID: a-A838, Offset: 17867
>  IPM_SUBTREE\Good Luck\Contacts\SAN DIEG0 COUNTY CONTACTS
> 15) FID: a-A83E, PFID: a-A838, Offset: 19353
>  IPM_SUBTREE\Good Luck\Contacts\VENTURA COUNTY
> 16) FID: 5-7172, PFID: a-A83E, Offset: 20806
>  IPM_SUBTREE\Good Luck\Contacts\VENTURA COUNTY\SAN DIEG0 COUNTY CONTACTS
> 17) FID: 5-7174, PFID: a-A83E, Offset: 22397
>  IPM_SUBTREE\Good Luck\Contacts\VENTURA COUNTY\SAN DIEG0 COUNTY CONTACTS1
> 18) FID: 8-5672, PFID: 8-5671, Offset: 23991
>  IPM_SUBTREE\IT\IT Calendar
> 19) FID: 8-1B67, PFID: 8-1B65, Offset: 25313
>  IPM_SUBTREE\Seattle_Contacts\Seattle Contacts
> 20) FID: 8-90FC, PFID: 8-1B65, Offset: 26913
>  IPM_SUBTREE\Seattle_Contacts\seattle1
> 21) FID: 8-5675, PFID: 8-5674, Offset: 28443
>  IPM_SUBTREE\Temp1\Seattle
> 22) FID: 8-5678, PFID: 8-5674, Offset: 29468
>  IPM_SUBTREE\Temp1\Seattle Working
> 23) FID: 3-8, PFID: 1-5, Offset: 31065
>  NON_IPM_SUBTREE\OFFLINE ADDRESS BOOK\EX:/o=<orgname>/ou=<sitename>
> 24) FID: d-F, PFID: 3-8, Offset: 32088
>  NON_IPM_SUBTREE\OFFLINE ADDRESS BOOK\E...
>  IDCN Deleted:
>   5-3309,5-485A
> 5-9A91,5-9BF8
> 6-7,c-9
> b-BC3,c-A
> 6-8,c-B
>
>  Server: /O=<orgname>/OU=<sitename>/CN=CONFIGURATION/CN=SERVERS/CN=<Exch
5.5
> servername>/CN=MICROSOFT PUBLIC MDB
> **********
>
> In the above example, the problematic public folder is the only one not
> listed.
> I get this corresponding log entry on the 5.5 server:
> *********
> An incoming replication message was processed.
>
> Type: 0x80000002
> Message ID: 13-812
> CNSET: 1-485A,1-9BFF
> 3-FFFFFFFF0002,3-FFFFFFFF0004
> d-9,d-B
> f-9,f-2FF0
> 11-669C,11-A529
>
> CNSET(FAI): {0}
>
> Server: /O=<orgname>/OU=<sitename>/CN=CONFIGURATION/CN=SERVERS/CN=E2K3
> Servername>/CN=MICROSOFT PUBLIC MDB
> **********
>
> The second message, which I get when I execute a "send contents" command,
> contains the following:
> **********
> An outgoing replication message was issued.
>
>  Type: 0x80000004
>  Message ID:
> <6A39E548EDF5BF40AAF1B5EB72837870A539@<servername>.<domainname>.COM>
>  Folder: (5-9A92) IPM_SUBTREE\Jazz EFax
>
>  Database "First Storage Group\Public Folder Store (<E2K3 servername>)".
>  CNSET: d-27DE,d-27DE
>
>  CNSET (FAI): {0}
>
>  Message IDs: 1
>   1: d-1FDE, d-27DE
> --- : <message subject>: 5/17/2004 7:12:50 PM
>
>  MIDSET Deleted: d-1,d-1FDD
>
>  Server: /O=<orgname>/OU=<sitename>/CN=CONFIGURATION/CN=SERVERS/CN=<exch
5.5
> servername>/CN=MICROSOFT PUBLIC MDB
> **********
> And the following response from the 5.5 server:
> **********
> An incoming replication message was processed.
>
> Type: 0x80000004
> Message ID: 13-813
> Folder: (1-9A92) IPM_SUBTREE\Jazz EFax
>
> CNSET: f-27DE,f-27DE
>
> CNSET(FAI): {0}
>
> Server: /O=<orgname>/OU=<sitename>/CN=CONFIGURATION/CN=SERVERS/CN==E2K3
> Servername>/CN=MICROSOFT PUBLIC MDB
> **********
>
> So it looks like when the hierarchy attempts to replicate, it doesn't
> recognize that the folder in question exists. But when I try to push the
> contents, it recognizes it's existence OK. It just doesn't see any changed
> data.
> So where do I look to reconcile the differences? I tried ESEUTIL and
ISINTEG
> on the restored pub.edb. No difference...
> There must be some way to tell exchange that the 950 messages in that
folder
> need to be replicated.
>
> Any ideas on how I can further troubleshoot this problem?  Thanks!
>
>
> Charlie
>
>

Relevant Pages

  • RE: reomve server from site.
    ... How to Remove the First Exchange 2000 Server Computer from the Site ... the Offline Address Book folder, the Schedule+ Free Busy folder, the Events ... Click the Replication tab, and then click Add. ...
    (microsoft.public.exchange2000.admin)
  • Re: Public Folder replication still occurring after removing replica
    ... still attempting to replicate between the old & the new server). ... I set up the replication according to 307917. ... folders & OAB Version2 still listed under Public Folder Instances. ...
    (microsoft.public.exchange.admin)
  • Re: Lingering objects, replication on dcs
    ... Hi Jorge, I looked at the events carefully and I remembered after I did the ... whack, but there's still some replication issues, I noticed it replicates ... # Jorge de Almeida Pinto # MVP Windows Server - Directory Services ... the old 2k DC and then uninstall e2k3, reinstall the 2k3 DC, I'm trying to ...
    (microsoft.public.windows.server.active_directory)
  • Re: Public Folders better at disappearing than David Copperfield?
    ... >Before you dismounted the public folder store (the source of the PF ... could "see" this folder depending on which server the folder lived. ... Before and during replication of this folder I had the ...
    (microsoft.public.exchange.admin)
  • Re: Replicate Public folders between 2 SBS 2003 exchanges
    ... we can use Domain DFS to deploy the file replication. ... since the SBS 2003 server does not support domain trust ... only the permission to access the shared folder. ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)