Hello,
I thought that might be the issue so I built up a new Exchange 2007 server and migrated the mailboxes. The error has since gone away however I do now have a true "front-end/back-end" topology where my front-end system has my public SSL certificate bound to it and my back-end has the cert generated by Exchange at install time.
I'm not sure how you would deploy the product any other way since you can't have two certificates bound to the same IIS site.
Prior to changing the topology I did get an error indicating the certificate for my single Exchange server was "invalid" and didn't match the fqdn of the system. This was obvious since I had replaced the certificated generated by Exchange with my public one.....which explains the error I originally posted about.
Thank you for the reply!
Jason