Microsoft.Exchange.Net.ExSmtpClient.TlsApiFailureException: A TLS API failure occurred. Error = 0x80

Status
Not open for further replies.
R

Rob.Ford

Hi,

I have the same problem that someone reported here.

We have 2 UM servers with identical setups (UM config, certificates, etc) in different sites. One works perfectly. The other, you can call and configure your voice mail, call and leave a voice mail or be diverted to another number via a call answering rule.

All this works except the voice mail is not delivered. In the application event log I see:

A pipeline stage encountered the following error. Details : 'Microsoft.Exchange.Net.ExSmtpClient.TlsApiFailureException: A TLS API failure occurred. Error = 0x80090301

This is logged continuously, every minute or so, or more. If I set this UM server startup mode to only TCP, the events are not logged continuously and then only ocurr when someone tries to leave a voice message.

Both servers have UM assigned certificates with the correct subject/DNS names. The corresponding CAS servers have specific receive connectors, configured for TLS, for both the working and non-working UM server IP addresses. I have even loaded the UM certs onto our CAS servers. What-ever I try, the good server just works, and the bad one just logs this error.

Does anyone have any suggestions as to why this is?

Cheers,

Rob
 
R

Rob.Ford

Hi,

I've resolved this. Our problem UM 2010 box was talking to a local 2010 CAS. The CAS server had had rootsupd.exe run on it to update the local computer " Trusted Root Certification Authorities" store.

This caused a TLS handshake failure between the UM and CAS servers because their were far too many trusted authorities for the process to work.

There were 314 trusted authorities on the CAS. I have trimmed these down to about 80 and UM immediately worked and this error went away (I also restarted the UM service just to be sure).

Cheers,

Rob
 
Status
Not open for further replies.
Top