meeranair
Posts: 9
Joined: 29.Jul.2008
Status: offline
|
Review and Research the Event logs for errors or warnings related to this issue. Collect logs with increased diagnostic logging.
{Example :The following Event’s indicate that Proxy addresses are not stamping:
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 2035
Description:
The e-mail address description object in the Microsoft Exchange directory for the 'TYPE' address type on 'i386' machines is missing.
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 2037
Description:
The file version of 'Address\TYPE\I386\3RDPARTY.dll' installed on the local server is not current. Unable to locate a correct version on any server in the site.
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 2027
Description:
Unable to generate the e-mail address. Unable to load address module 'C:\Exchsrvr\Address\TYPE\I386\3RDPARTY.dll' for address type 'TYPE'. Error 0xc007007e.
Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Controller
Event ID: 8231
Description:
Permanent failure reported by policy group provider for 'CN=Recipient Policies,CN=Name,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=Name,DC=com':'MAD.EXE', error=8000ffff. Taking provider offline.}
2. Increase diagnostics logging on public folder replication messages.
Since public folder replication traffic is message-based, we can troubleshoot a problem by increasing the diagnostic logging level for public folder replication messages. Typically, to troubleshoot public folder replication problems, increase the logging level to Maximum on the following diagnostic logging categories:
Replication AD Updates ; Replication Incoming Messages ; Replication Outgoing Messages ; Non-Delivery Reports ; Replication Backfill ; Replication General ; Transport Delivering (available only on Exchange 2003).
{When you increase diagnostic logging to Maximum, significantly more events are generated in the application log. Therefore, make sure that the application log is large enough to contain these events.}
a. Start Exchange System Manager.
b. Expand Administrative Groups, expand Administrative Group Name, and then expand Servers.
c. Right-click your Exchange Server computer, and then click Properties.
d. Click the Diagnostics Logging tab, and then expand MSExchangeIS in the Services list.
e. Press the CTRL key, and then click all the following items:
Replication AD Updates
Replication Incoming Messages
Replication Outgoing Messages
Non-Delivery Reports
Replication Backfill
Replication General
f. Click Maximum, and then click Apply.
3. Increase the logging level to Medium on the following diagnostic logging category: Replication Errors
a. Start Exchange System Manager.
b. Expand Administrative Groups, expand Administrative Group Name, and then expand Servers.
c. Right-click your Exchange Server computer, and then click Properties.
d. Click the Diagnostics Logging tab, and then expand MSExchangeIS in the Services list.
e. Click Replication Errors, click Medium, click Apply, and then click OK.
4. Perform the above mentioned steps on an Exchange server that does not have Public Folder replication issues. This is because an outgoing public folder replication message from one Exchange Server computer corresponds to an incoming public folder replication message on another Exchange Server computer. Therefore, you can view the event logs from the two computers to match the outgoing public folder replication messages from one Exchange Server computer with the corresponding incoming public folder replication messages on the other Exchange Server computer.
5. Hierarchy Replication Messages : This does not include the modification of the public folder content. This only includes the modification of the public folder itself. For example, when the public folder is renamed, when the public folder replica list is modified, when the public folder's display name is changed, when the public folder permissions are modified, when the public folder description is changed, and more. Any change to the public folder other than adding or removing content from that folder is replicated by a hierarchy replication message.
The following event id’s are generated in this scenario:
a. Event ID: 3018: This is the outbound replication message. This event is logged on the computer where the hierarchy change was made. This computer then sends the hierarchy change message to all the other public folder server computers that are in the same top level hierarchy (TLH).
b. Event ID: 3028: This is the inbound replication message. This event is logged on the computer that receives the outbound replication message (Event ID: 3018) from another computer.
6. Content replication messages : This is created when Posting items to Public Folder, Modifying items in the Public Folder, Removing items from Public Folder.
The following event ID’s are generated in this scenario:
a. Event ID: 3020: This is the outbound replication message. This event is logged on the computer that sends the public folder content to another computer.
b. Event ID: 3030: This is the inbound replication message. This event is logged on the computer that receives the outbound replication message (Event ID: 3020) from another computer.
7. Backfill replication messages : Backfilling is the process that a store that has missed replication updates uses to request a re-send of the missing data. There are two parts to the Backfill process: Backfill Request ; Backfill Response. Sometimes, the backfill process may take from 48 to 72 hours or longer to complete.
The following event ID’s are generated in this scenario:
Backfill request:
a. Event ID: 3014: This is the outbound replication message. This event is logged on the computer that sends the backfill request message.
b. Event ID: 3024: This is the inbound replication message. This event is logged on the computer that receives the backfill request message (Event ID: 3014) from another computer.
Backfill response:
a. Event ID: 3019: This is the outbound replication message. This event is logged on the computer that sends the backfill response message.
b. Event ID: 3029: This is the inbound replication message. This event is logged on the computer that receives the backfill response message (Event ID: 3019) from another computer.
8. Status replication messages:
A status request message is sent by one store to another store to trigger the replication of missing updates. Status request messages occur when a new replica of a public folder is created in a store. In this scenario, the store where you create the new public folder replica determines that it must be missing the corresponding public folder information, and that it must perform a backfill operation to obtain that public folder information. A hierarchy status request message is generated when you create a new public folder store on an Exchange Server computer. The two occasions where a status request message is generated are very similar:
a. A new replica of a public folder causes a status request message to be generated to obtain the public folder content.
b. A new public folder store causes a status request message to be generated to obtain the public folder hierarchy. This behavior occurs because a new hierarchy folder has been created.
9. Determine whether the replication messages that are sent from one computer are received by another computer : To do this, track the replication messages by using the Message Tracking feature on both the sending Exchange Server computer and the receiving Exchange Server computer. To configure message tracking, follow these steps:
a. Start the Exchange System Manager
b. Expand Administrative Groups, expand your administrative group, expand Servers, right-click your Exchange Server computer, and then click Properties.
c. On the General tab, click to select the Enable message tracking check box, and then click OK.
d. After you enable message tracking on both Exchange Server computers, create a new public folder or add content to an existing public folder, and then wait for the events to appear that indicate that the replication messages have been sent from the originating Exchange Server computer.
e. Start the Exchange System Manager, expand Tools, and then click Message Tracking Center.
f. In the Message Tracking Center on both the Exchange Server computers, track both the following message types:
1. Messages that are sent from the originating computer.
2. Messages that are sent to [email=ExchangeServerNane-IS@DomainName.com]ExchangeServerNane-IS@DomainName.com[/email] where [email=ExchangeServerNane-IS@DomainName.com]ExchangeServerNane-IS@DomainName.com[/email] is the name of the destination public folder store.
10. If the destination Exchange Server computer does not receive replication messages, verify that Integrated Windows authentication is enabled on the SMTP virtual server on that destination computer. To do this, follow these steps:
a. Start the Exchange System Manager.
b. Expand Administrative Groups, expand your administrative group, expand Servers, expand the Exchange Server computer that does not receive replication messages, expand Protocols, expand SMTP, right-click the SMTP virtual server, such as Default SMTP Virtual Server, and then click Properties.
c. Click the Access tab, and then click Authentication.
d. Click to select the Integrated Windows Authentication check box if it is not already selected, and then click OK two times.
11. You may receive the following messages in the application event log that indicate replication messages have been received successfully on a computer that is running Exchange 2003:
Event Type: Success Audit
Event Source: MSExchangeIS Public Store
Event Category: Logons
Event ID: 1018
Description: NT AUTHORITY\SYSTEM was validated as NT AUTHORITY\SYSTEM and logged on to the Public Folder Store "First Storage Group\Public Folder Store (ServerName)" as an owner using administrator privileges.
Event Type: Information
Event Source: MSExchangeIS Public Store
Event Category: Transport Delivering
Event ID: 9650
Description: Message delivery is being attempted. Internet Msg Id:<B1E7E7ADC8AB4049B6D77127293363C6012AA7@DomainName.com>, Submit Time: 04/02/2004 17:14:51.8308048, Recipient:/O=OrganizationName/OU=OrganizationalUnitName/cn=Configuration/cn=Servers/cn=ServerName/cn=Microsoft Public MDB, MDB:First Storage Group\Public Folder Store (ServerName).
Event Type: Information
Event Source: MSExchangeIS Public Store
Event Category: Transport Delivering
Event ID: 9651
Description: Message was successfully delivered to <B1E7E7ADC8AB4049B6D77127293363C6012AA7@DomainName.com> on /O=OrganizationName/OU=OrganizationalUnitName/cn=Configuration/cn=Servers/cn=ServerName/cn=Microsoft Public MDB. Internet Msg Id:First Storage Group\Public Folder Store (ServerName).
12. After you receive event ID 9651, you will see an event ID 3028 message indicating that a replication message has been processed.
Event Type: Information
Event Source: MSExchangeIS Public Store
Event Category: Replication Incoming Messages
Event ID: 3028
Description: An incoming replication message was processed.
13. To configure public folder replication status request messages, follow these steps:
a. Configure the registry value for the public folder replication status request messages on the Exchange 2000 Server computers and on the Exchange Server 2003 computers that do not have up-to-date public folder hierarchy information as per Knowledge Base article 321082.
b. Dismount and then remount the public folder store on each of those Exchange Server computers where you configured this registry key.
c. Wait approximately 12 to 24 hours or longer, and then verify that the whole public folder hierarchy has replicated to the computer where you experience this problem.
d. After the public folder hierarchy has replicated successfully, follow the steps in the following Microsoft Knowledge Base article to configure the registry key to enable public folder content replication status messages:
14. Public folder content replication takes much longer to complete than public folder hierarchy replication. Wait at least 48 to 72 hours or longer, and then verify that the public folder content for all the public folders that have replicas on that public folder store has been replicated.
Related Knowledge Based Articles:
http://support.microsoft.com/kb/286356/ : Exchange Recipient Update Service does not stamp proxy addresses in Exchange 2000 Server and in Exchange Server 2003
http://support.microsoft.com/kb/246856/ : How to enable message tracking in Exchange 2000 Server and in Exchange Server 2003
http://support.microsoft.com/kb/262162/ : Using the Message Tracking Center to track a message in Exchange Server
http://support.microsoft.com/kb/828420/ : Public folder replication does not occur, and event ID 3020 is logged on a computer that is running Exchange 2000 or Exchange 2003
http://support.microsoft.com/kb/321082/ : How to Send Replication Status Request Messages in Exchange 2000 Server
http://support.microsoft.com/kb/813629/ : Update to send status request messages in Exchange 2000 Server
http://support.microsoft.com/kb/813629/ : Update to send status request messages in Exchange 2000 Server
http://support.microsoft.com/?kbid=842273 : How to troubleshoot public folder replication problems in Exchange 2000 Server and in Exchange Server 2003.
_____________________________
Meera Nair
MS Exchange Admin Support
|
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
Replicate Public Folder in new server - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread