Hi all, I have an Exchange 2010 SP2 system, with 5 CAS servers, 6 mailbox servers and two HUB servers. I'm looking at system events continuously this error, indicating that I have the certificate FQDN autodirmado with HUB server, I get this error on both: Log Name: Application Source: MSExchangeTransport Date: 2/28/2013 8:11:36 AM Event ID: 12014 Task Category: TransportService Level: Error Keywords: Classic User: N / A Computer: server.x.y description: Microsoft Exchange Could not find a certificate contains the domain name That server.xy in the personal store on the local computer. THEREFORE, it is unable to support the STARTTLS SMTP verb for the connector with a Client server FQDN parameter of server.xy If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure That there is a certificate with a domain name for That FQDN. If this certificate exists, run Enable-ExchangeCertificate-Services SMTP to make sure That the Microsoft Exchange Transport service has access to the certificate key. I have a third party certificate, which I add the SMTP service on the HUB, the self-signed certificate for the server I removed. regards Microsoft Certified IT Professional Server Administrator

Check these articles, they should help you to fix it http://smtp25.blogspot.in/2009/10/microsoft-exchange-couldn-find.html http://msexchangeguru.com/2011/06/22/event12014/Gulab Prasad, gulab@exchangeranger.com Exchange Ranger | Z-Hire Employee Provisioning App

Check these articles, they should help you to fix it http://smtp25.blogspot.in/2009/10/microsoft-exchange-couldn-find.html http://msexchangeguru.com/2011/06/22/event12014/Gulab Prasad, gulab@exchangeranger.com Exchange Ranger | Z-Hire Employee Provisioning App

Hi 1.If your send/receive connector on your hub/edge transport server is using a fqdn that is not listed on the certificate, then the event id 12014 will be written to the application log. Get-SendConnector | fl fqdn Get-ReceiveConnector |fl fqdn Get-ExchangeCertificate | fl CertificateDomains If the fqdn on the connector is not listed in the output under CertificateDomains, you'll need to either modify your the connector fqdn or generate a new certificate with the appropriate name in order to resolve the issue. 2. You may also receive this error if your certificate is expired. You can easily check this by using the Get-ExchangeCertificate cmdlet: Get-ExchangeCertificate | fl thumbprint, status, notafterTerence Yu TechNet Community Support

Hi 1.If your send/receive connector on your hub/edge transport server is using a fqdn that is not listed on the certificate, then the event id 12014 will be written to the application log. Get-SendConnector | fl fqdn Get-ReceiveConnector |fl fqdn Get-ExchangeCertificate | fl CertificateDomains If the fqdn on the connector is not listed in the output under CertificateDomains, you'll need to either modify your the connector fqdn or generate a new certificate with the appropriate name in order to resolve the issue. 2. You may also receive this error if your certificate is expired. You can easily check this by using the Get-ExchangeCertificate cmdlet: Get-ExchangeCertificate | fl thumbprint, status, notafterTerence Yu TechNet Community Support

Thanks for answering, I have two Hub Transport, each has 3 receive connectors: Client default Relay In the Default connector are placed in the HELO response, the certificate name (JE. mail.contoso.com), on the other connectors in the HELO response, have the name of the server FQDN. On server1, has since server1.contoso.com. Should I change the HELO response of all Receive connectors on the Hub Transport to mail.contoso.com, to keep me from this error? Affect the mail system?, Now everything works fine, but the event is recorded on the server many ThanksMicrosoft Certified IT Professional Server Administrator