Question : Cannot access voicemail on Exchange 2010 from OCS 2007R2. Failure Type 80004005


I have just installed a new OCS 2007R2 server on one box that comunicates with my new Exchange 2010. So far all the exchange integration works fine. Only issue is when I try to access my voicemail internally from the client, I get an error and the call does not go through. I searched around for the error I am getting and it points to either a bad certificate (Not sure but the certificate we have on exchange is a certificate from GoDaddy that has all the proper dns entry in it and should be trusted by OCS by default. Also other articles points to a microsoft Patch for Windows 2008R2 that when I try to apply says it does not apply to my systems (Both exchange and ocs). Also I have applied all the patches for OCS per the baseline analyser... This is the error I get from the logs on the OCS error when it fails to get a response from Exchnage:

Log Name:      Office Communications Server
Source:        OCS Protocol Stack
Date:          7/12/2010 9:07:05 AM
Event ID:      14501
Task Category: (1001)
Level:         Error
Keywords:      Classic
User:          N/A
A significant number of invalid certificates have been provided by remote IP address when attempting to establish an MTLS peer. There have been 20 such failures in the last 3601 minutes.
Certificate Names associated with this peer were
The serial number of this certificate is
The issuer of this certificate is Go Daddy Secure Certification Authority
The specific failure types and their counts are identified below.
Instance count   - Failure Type
30                 80004005

Event Xml:
<Event xmlns="">
    <Provider Name="OCS Protocol Stack" />
    <EventID Qualifiers="50153">14501</EventID>
    <TimeCreated SystemTime="2010-07-12T13:07:05.000000000Z" />
    <Channel>Office Communications Server</Channel>
    <Security />
    <Data>Go Daddy Secure Certification Authority</Data>

Answer : Cannot access voicemail on Exchange 2010 from OCS 2007R2. Failure Type 80004005

Issue fixed. Uninstalled OCS 2007R2, re-installed the server with Windows 2008 instead of 2008R2 and now everything is working fine. Issue was most likely with Windows 2008R2 even though Microsoft says that OCS 2007R2 can be installed on 2008R2, I guess it probably requires some trick to get it to work...
Random Solutions  
programming4us programming4us