When your Exchange unified messaging server logs event ID 1082, what do you do?
The first step in answering this question is understanding what event ID 1082 means. The error message itself is pretty clear: “No Hub Transport server available to process header file C:\Program Files\Microsoft\Exchange Server\UnifiedMessaging\voicemail\70683b04-5e47-4d24-a143-1cf331a4f121.txt.“. If you look in the referenced directory, you’ll probably find a bunch of pairs of files, with each pair consisting of a .wav file that contains the actual voicemail plus a .txt file that contains routing information.
This error can occur for several reasons, all involving UM’s inability to find a hub transport server to talk to. Things to check:
- make sure you have a hub transport role installed and that it’s up
- look for event ID 12014, which indicates a problem with TLS handshaking with the hub. If you see this, you can probably fix it with the enable-ExchangeCertificate cmdlet; use it to enable the certificate for use with SMTP
- verify that your hub transport server is properly advertising the X-ANONYMOUSTLS verb. Exchange 2007 advertises this verb as part of its EHLO handshake. If you don’t see this verb, it indicates that– for whatever reason– the server has forgotten that it should be able to accept opportunistic TLS sessions using self-signed certificates.
I’ve seen the third case once recently; I was able to fix it by removing and reinstalling the hub transport role on the affected server. However, I’d like to better understand what causes it before recommending that as a permanent fix.