Prev: The Exchange mailbox Server: has reached its timeout threshold
Next: How can I use an external LDAP server as a source for a custom GAL pls?
From: Charlie Kaiser on 15 Sep 2009 19:14
scenario:
Single-server E2K3 org. Single E2K7 server added for replacement purposes.
Mailboxes moved, connectors replaced, mailflow verified, client access
verified. All working OK.
PF migration started. Created replicas of PFs on new server using ESM.
Allowed things to spin for a week. Started decommissioning of old server.
Started looking at PFs and found that about 25% of them are not replicating
content. When viewing them with ESM07, connecting to the 7 server, I see zero
item counts on those non-replicating pfs. When viewing them on the 3 server,
I see valid number counts. When connecting to OWA 7, I see no items in the
folders.
I've cranked up PF rep logging and have looked at SMTP logs. It appears that
there may be an auth issue between the two servers, but I'm not sure of that.
I'm getting Event ID 1020 errors referring to content conversion limit
problems.
Here's the relevant info from the event:



Log Name: Application
Source: MSExchange Store Driver
Date: 9/14/2009 5:42:16 PM
Event ID: 1020
Task Category: MSExchangeStoreDriver
Level: Error
Keywords: Classic
User: N/A
Computer: <New server FQDN>
Description:
The store driver couldn't deliver the public folder replication message
"Folder Content Backfill Response (<old server IS FQDN>)" because the
following error occurred: The content conversion limit has been exceeded.

Research on this error lead me to these articles:
http://msexchangeteam.com/archive/2006/01/17/417611.aspx
http://msexchangeteam.com/archive/2006/01/19/417737.aspx
http://msexchangeteam.com/archive/2006/01/23/417974.aspx
http://msexchangeteam.com/archive/2008/01/10/447843.aspx

That's when I cranked up the logging and found this info in the generated
files:

Microsoft.Exchange.Data.Storage.ConversionFailedException: The content
conversion limit has been exceeded.
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: False
- imceaResolveableDomain: <mail domain FQDN>
- preserveReportBody: False
- clearCategories: True
- userADSession:
- recipientCache: Microsoft.Exchange.Data.Directory.Recipient.ADRecipientCache
- clientSubmittedSecurely: False
- serverSubmittedSecurely: False
- disableNewXHeaderMapping: - convertReportToMessage: False-
treatInlineDispositionAsAttachment: False
- preferredInternetCodePageForShiftJis: False
0


The relevant line is "- isSenderTrusted: False". Apparently, this means it's
not authenticating.
But when I run a network trace on the connection attempt, I get this:

220 nsi-exch.ns-intl.local Microsoft ESMTP MAIL Service, Version:
6.0.3790.3959 ready at Tue, 15 Sep 2009 09:01:29 -0700
EHLO NSI-EXCH2007.ns-intl.local
250-nsi-exch.ns-intl.local Hello [10.0.0.8]
250-TURN
250-SIZE
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250-X-EXPS GSSAPI NTLM LOGIN
250-X-EXPS=LOGIN
250-AUTH GSSAPI NTLM LOGIN
250-AUTH=LOGIN
250-X-LINK2STATE
250-XEXCH50
250 OK
X-EXPS GSSAPI
334 GSSAPI supported
{Bunch of data}
334 {Bunch more data}
235 2.7.0 Authentication successful.
MAIL FROM:<PublicFolders@<FQDN>> SIZE=3331 BODY=BINARYMIME
RCPT TO:<<servername>-IS@<FQDN>> NOTIFY=NEVER
250 2.1.0 PublicFolders@<FQDN>....Sender OK
250 2.1.5 <servername>-IS@<FQDN>
XEXCH50 144 2
354 Send binary data


According to the article, that exchange indicates all is well with auth.
Making a change to the folder on the 3 server doesn't change anything.

So why am I having replication failures?

Even tried move all replicas. Hasn't helped...
Any thoughts? Thanks!

Charlie Kaiser
Sr. Systems Engineer
charlie{at}networksolutionsintl.com

 | 
Pages: 1
Prev: The Exchange mailbox Server: has reached its timeout threshold
Next: How can I use an external LDAP server as a source for a custom GAL pls?