Are you using SmarterMail Certificate facility or other?

If your port bindings used a CRT file in the past you'll need to change them to use a PFX version of your certificate. To acquire one you can export your server's certificate as a PFX from the Windows Certificates console (in MMC.exe) including the private key. Be sure to set a strong password on your PFX and add that password to the SmarterMail web interface when you update those bindings to point to the new file.

Hey, Larry

I see you put in a ticket for this on Friday and we were able to get things working for you. As Kyle said, changing to PFX and re-setting your passwords so certs are regenerated is a relatively simple way around invalid cert issues on an upgrade. 

The issue was the certs had two different passwords and the bindings had the wrong one. This means it could not load the cert. The certs were not expired, and I do not know how the password was changed in some but not all. The fix was to reenter the password in the SETTINGS>SSL CERTIFICATION>OPTIONS. Change the IIS> Centralized Certificates> Edit Feature Settings > Certificate Private Key Password to the same password. Changing all the bindings SETTINGS>BINDINGS>PORTS> double click and enter the same password. Then regenerate Certs SETTINGS>SSL CERTIFICATION>AUTOMATIC CERTIFICTES> selecting all certs and right clicking and renew now. This corrected the issue. This was kind of short answer.  Sorry.