Greetings, community!
Maybe someone has faced a similar problem ?:
Upgrading Exchange 2007 (with all the latest SP and UR) to Exchange 2013 SP1.
I used to have a single physical server Exchange 2007 with of all roles. Instead, the role of EDGE I used MDaemon.
Now all of the Exchange Server 2013 roles in the virtual configuration: 2CAS, 2MBX, 2EDGE in the DMZ.
Actually what is the problem:
When I subscribe two EDGEs, they are correctly subscribed and correctly created send connectors (2 pcs.)
However, Exchange 2007 does not want to send e-mails via connector "EdgeSync - Site to Internet". In the Application Log every 3-5 minutes appear errors from MSExchange EdgeSync:
Error 1033
The Microsoft Exchange EdgeSync service could not decrypt the credential for Edge Transport server EDGE2.domain.local by using the private key of the internal transport certificate with exception Bad Data.
. The certificate's thumbprint is 4EE35648FFB41AC5C3D603C9688499E99FC28D67 and its subject is CN = mail.domain.ru, OU = IT, O = DOMAIN, L = Moscow, S = Moscow, C = RU. Use the Enable-ExchangeCertificate cmdlet or New-ExchangeCertificate cmdlet in the Exchange
Management Shell to set the correct Exchange internal transport certificate and resubscribe Edge Transport server EDGE2.domain.local.
and
The Microsoft Exchange EdgeSync service could not decrypt the credential for Edge Transport server EDGE1.domain.local by using the private key of the internal transport certificate with exception Not enough storage is available to process this command. The certificate's thumbprint is 4EE35648FFB41AC5C3D603C9688499E99FC28D67 and its subject is CN = mail.domain.ru, OU = IT, O = DOMAIN, L = Moscow, S = Moscow, C = RU. Use the Enable-ExchangeCertificate cmdlet or New-ExchangeCertificate cmdlet in the Exchange Management Shell to set the correct Exchange internal transport certificate and resubscribe Edge Transport server EDGE1.domain.local.
Tried to change to Exchange 2007 SMTP certificate on the other, including and commercial and our own PKI, then did EDGE subscription again - same fault result.
PS: I enable Edge Subscription on MBX servers with Exchange 2013. Exchange 2007 have different syntax for enable subscription, and whether it is necessary to activate it on the old MBX?
PPS: If the message came through the connector "EdgeSync - Inbound to Site", it correctly reach the mailbox on Exchange 2007. Probably because going through SmartHost ...
PPPS: Messages from mailbox stored on Exchange 2013 go through "EdgeSync - Site to Internet" connector without any problems.
