Erro de replicação de Public Folder – event ID 3093
Tive um problema de replicação entre servidores de public folders, estou enviando a solução definitiva enviada pelo suporte da Microsoft.
Problema – A pasta pública não replicar para outro servidor no mesmo local, a replicação da PF no mesmo local tem não, um monte de ID de evento 3093 do MSExchangeIS Public Store foi mostrado
Meio Ambiente – Exchange 2010 On-Premises
Causa Raiz – pasta pública no servidor de destino teve mais de um endereço SMTP principal.
Resolution – 1-) We raised event log level for MSExchangeIS
[PS] C:\windows\system32>Set-EventLogLevel -Identity “STS40WK8\MSExchangeIS\9001 Public\Replication Backfill” -Level Expert
[PS] C:\windows\system32>Set-EventLogLevel -Identity “STS40WK8\MSExchangeIS\9001 Public\Replication Incoming Messages” -Level Expert
[PS] C:\windows\system32>Set-EventLogLevel -Identity “STS40WK8\MSExchangeIS\9001 Public\Replication Outgoing Messages” -Level Expert
2-) Forced a change for the folder and tracked the message
Get-MessageTrackingLog -Server “STS40WK8” -MessageID “<D8EEAFF22FFB4C4FBBC0811F904B8CD901C42D51@STS39WK8.dc.com.br>”
EventId Source Sender Recipients MessageSubject
——- —— —— ———- ————–
RECEIVE STORE… IMCEAEX-_O=FIRST+20ORGANIZATION_OU=EXCHANGE+20ADMINISTRAT… {IMCEAEX-_O=FIRST+20ORGANIZATION_OU=FIRST+20ADMINISTRATIV… Hierarchy
FAIL ROUTING IMCEAEX-_O=FIRST+20ORGANIZATION_OU=EXCHANGE+20ADMINISTRAT… {IMCEAEX-_O=FIRST+20ORGANIZATION_OU=FIRST+20ADMINISTRATIV… Hierarchy
RunspaceId : 1fd40216-11ad-4a48-8882-e8434bfda1ef
Timestamp : 07/07/2014 11:29:38
ClientIp :
ClientHostname : STS40WK8
ServerIp :
ServerHostname :
SourceContext :
ConnectorId :
Source : ROUTING
EventId : FAIL
InternalMessageId : 431536
MessageId : <D8EEAFF22FFB4C4FBBC0811F904B8CD901C42D51@STS39WK8.dc.com.br>
Recipients : {IMCEAEX-_O=FIRST+20ORGANIZATION_OU=FIRST+20ADMINISTRATIVE+20GROUP_CN=CONFIGURATION_CN=SERVERS_CN=STS125WKE_CN=MICROSOFT+20PUBLIC+20MDB@t-systems.com.br, IMCEAEX-_O=FIRST+20ORGANIZATION_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=CONFIGURATION_CN=SERVERS_CN=STS40WK8_CN=MICROSOFT+20PUBLIC+20MDB@t-systems.com.br}
RecipientStatus : {550 5.2.0 RESOLVER.ADR.BadPrimary; recipient primary SMTP address is missing or invalid, 550 5.2.0 RESOLVER.ADR.BadPrimary; recipient primary SMTP address is missing or invalid}
TotalBytes : 5969
RecipientCount : 2
RelatedRecipientAddress :
Reference : {, }
MessageSubject : Hierarchy
Sender : IMCEAEX-_O=FIRST+20ORGANIZATION_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=CONFIGURATION_CN=SERVERS_CN=STS39WK8_CN=MICROSOFT+20PUBLIC+20MDB@t-systems.co
m.br
ReturnPath : STS39WK8PublicFolder@dc.com.br
MessageInfo :
MessageLatency :
MessageLatencyType : None
EventData :
3-) As we can see above the message was not delivered due to 550 5.2.0 RESOLVER.ADR.BadPrimary; recipient primary SMTP address is missing or invalid}, to fix this problem using AdsiEdit we modified the Proxy Addresses for the Public Folder and also added the missing X500.
X500/O=FIRST ORGANIZATION/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=STS40WK8/CN=MICROSOFT PUBLIC MDB@t-systems.com.br
4-) We forced a new change and tracked the message and this time it was delivered, therefor the replication of the hierarchy started to work
Get-MessageTrackingLog -Server “STS40WK8” -MessageID “<D8EEAFF22FFB4C4FBBC0811F904B8CD901C42FBD@STS39WK8.dc.com.br>”
EventId Source Sender Recipients MessageSubject
——- —— —— ———- ————–
RECEIVE STORE… STS39WK8PublicFolder@t-systems.com.br {STS40WK8PublicFolder@t-systems.com.br} Hierarchy Backfill Response
TRANSFER ROUTING STS39WK8PublicFolder@t-systems.com.br {STS40WK8PublicFolder@t-systems.com.br} Hierarchy Backfill Response
DELIVER STORE… STS39WK8PublicFolder@t-systems.com.br {STS40WK8PublicFolder@t-systems.com.br} Hierarchy Backfill Response
# Finally to force a backfill of the content we ran
Get-PublicFolder -Server STS40WK8 -Recurse -ResultSize Unlimited |Update-PublicFolder -Server STS39WK8
Related Knowledge Base Articles
=======================
How to troubleshoot public folder replication problems in Exchange 2000 Server and in Exchange Server 2003
http://support.microsoft.com/kb/842273/en-us
Public Folder Replication Troubleshooting – Part 1: Troubleshooting the Replication of New Changes
http://blogs.technet.com/b/exchange/archive/2006/01/17/417611.aspx
#ficaadica