Exchange Error 12014

Hello, I am getting this error on my 2010 Exchange server:

Application Error: 12014

Microsoft Exchange could not find a certificate that contains the domain name gateway.calhospital.org in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector Default SERVER4 with a FQDN parameter of gateway.domain.org. 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.

This has occured since I changed the FQDN on my receive connector to match the outside DNS record.  I understand this is a certificate issue and I need a certificate that matches my new name on the send connector.  My question is can I just add another generic certificate with the new FQDN, while leaving the old cert in tact?  Is this error even that big of a deal?

All of my vendor purchased certs reside on our ISA server for Active Sync and OWA, OutlookAnywhere..... however SMTP traffic flows through a hardware firewall and not the ISA, so maybe I need another generic cert for the exchange server with a CN that matches the FQDN???

If anyone has experience in this, please let me know and Thanks!

Shawn
sdavidson916Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

BusbarSolutions ArchitectCommented:
Well,
If this error annoys you then you need to get a certificate for that, if not then you can jut ignore it, the error will be a deal when you add another hub transport server (you will need to have 2) in different sites, HUB servers will not be able to send to each other since they will need SMTP/TLS.
so in your case for a single server deployment either ignore it or get a certificate from the internal CA and assign it only to the SMTP service

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Alan HardistyCo-OwnerCommented:
This question has been classified as abandoned and is being closed as part of the Cleanup Program.  See my comment at the end of the question for more details.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.