Public Folder Replication between Ex2000 and Ex2003

[Steve Woolley]

As part of migrating from Exchange 2000 and Exchange 2003, I have
setup a second server (running Windows 2003 and Exchange 2003). I plan
to slowly move my current Exchange 2000 users over to the new server.
I had planned on setting up replicas for the public folders so that
both servers could be used to access the publc folders.

However...
I can view and manage both servers from both ESM's. I setup the
Replicas by selecting properties on the individual public folders and
Adding the new server as a replica. When the new public folders did
not magically appear on the new server, I buzzed the newsgroups which
led me to believe that I have to "Propagate Settings" for the public
folders to appear on the new server. I found the propagate settings by
right clicking on the public folders, selecting "All Tasks". However,
Propagate Settings is grayed out and only "Mail Enable" is available.
I have also tried (uder the public folder properties - Replication
tab) setting the pulic folder replication interval to "Always run" but
this also seemed to have no effect.

Am I doing something wrong here? Where are my public folders on my new
server?

Steve Woolley
swoo...@adstelecom.com

[¥xÆW·L³n§Þ³N³B]

Hi Steve,

The "Propagate Settings" option is only available for a public folder that
has at least one sub-folder.

There are two types of public folder replication - hierarchy replication
and content replication. Hierarchy replication occurs every 5 minutes
between all public folder stores in your Exchange organization. Content
replication occurs every 15 minutes only between the servers that have the
replica of the public folders.

For this public folder replication issue, please make sure the following
things first:

1. The mail flow between these two servers is ok because public folder
replication uses messages.
2. If these two servers are in two routing groups that are connected by a
connector, make sure that the "System Messages" is allowed to go through
this connector.
3. The proxyaddresses of the Public Folder Store object of both servers
contain valid addresses. You can use ADSI Edit to check this in AD.

Also, I think you need to enable the diagnostics logging for the following
categories on both servers, set the Application event log size to 100MB,
add some items to public folders and then analyze the information collected
in Application event log.

MSExchangeIS -> Public Folder -> Replication Incoming Messages
MSExchangeIS -> Public Folder -> Replication Outgoing Messages
MSExchangeIS -> Public Folder -> Non-delivery Reports
MSExchangeIS -> Public Folder -> Replication Errors

Thanks.

Best Regards,

Jason Zhou
Microsoft Online Support Professional

Get Secure! - www.microsoft.com/security

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[Steve Woolley]

Thanks for the response Jason. I turned on diag logging on both email
servers. I have now seen a large number of the following errors:

Event Type: Error
Event Source: MSExchangeIS Public Store
Event Category: Replication Errors
Event ID: 3093
Date: 9/2/2003
Time: 9:41:00 AM
User: N/A
Computer: MAIL1
Description:
Error -2147221233 reading property 0x67480014 on object type
tbtOwningFolders from database "First Storage Group\Public Folder
Store (MAIL1)".

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

Event Type: Error
Event Source: MSExchangeIS Public Store
Event Category: Replication Errors
Event ID: 3093
Date: 9/2/2003
Time: 9:39:29 AM
User: N/A
Computer: MAIL1
Description:
Error -2147221233 reading property 0xe080003 on object type
tbtMsgFolder from database "First Storage Group\Public Folder Store
(MAIL1)".

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

I have checked out some of these errors through newsgroups but have
seen an assortment of solutions: ignore these errors, need to do an
offline defrag, etc.

Any insight?
Steve Woolley
swoo...@adstelecom.com

jas...@online.microsoft.com ("台灣微軟技術處") wrote in message news:<tkuBsBHc...@cpmsftngxa06.phx.gbl>...

[¥xÆW·L³n§Þ³N³B]

Hi Steve,

Yes, in many cases this error does not necessarily mean any problem so that
it can be ignored. However, I still suggest you try the following two
methods to troubleshoot this problem:

1. Make sure that if the Replication key exist, its value is not set to 0.
Please view the following Knowledge Base article for more information:

812294 XADM: Replication Does Not Occur for One Exchange Server in the
http://support.microsoft.com/?id=812294

2. This issue may occur when replication key in the registry on the problem
Exchange server has been corrupted. To resolve this issue, delete the
corrupted registry key. To do this, please follow these steps:

1. Click "Start", and then click "Run".

2. In the "Open" box, type "regedit" (without the quotation marks) and then
press ENTER.

3. In Registry Editor, locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS

4. On the "Registry" menu, click "Export Registry File".

5. Type "MSExchangeISBackup" (without the quotation marks) and then click
"Save".

6. In Registry Editor, locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ExchangeSe
rverName\PublicUniqueID, where <ExchangeServerName> is the name of the
Exchange server, and where <PublicUniqueID> is the subkey named <Public>
with a globally unique identifier.

7. Click the subkey located in step 6, and then press DELETE.

8. Click "Yes ".

9. Quit Registry Editor.

10. Restart the Information Store service and test public folder
replication (hierarchy replication occurs every 5 minute; and content
replication occurs every 15 minutes).