CWA Activation problem RRS feed

  • Question

  • Hello, I have an error when I try to activate the CWA, the message error is:
        The subject of the certificate you selected doesn't match the current computer FQDN.

    But I check the certificate and the FQDName of the computer is as an ALT Name on the certificate.

    I create the certificate again, and stil the same.

    On the event viewer appear the following error, the name lcpool01.impsa.com.ar is loaded on the certificate also, I don't know if it is related but here it is:

    Log Name:      Office Communications Server
    Source:        OCS Protocol Stack
    Date:          30/10/2009 04:09:46 p.m.
    Event ID:      14428
    Task Category: (1001)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ARGMZASRV30.impsa.com.ar
    TLS outgoing connection failures.

    Over the past 1 minutes Office Communications Server has experienced TLS outgoing connection failures 1 time(s). The error code of the last failure is 0x80004005 (Unspecified error) while trying to connect to the host "lcpool01.impsa.com.ar".
    Cause: Wrong principal error could happen if the peer presents a certificate whose subject name does not match the peer name. Certificate root not trusted error could happen if the peer certificate was issued by remote CA that is not trusted by the local machine.
    For untrusted root errors, ensure that the remote CA certificate chain is installed locally. If you have already installed the remote CA certificate chain, then try rebooting the computer.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
        <Provider Name="OCS Protocol Stack" />
        <EventID Qualifiers="50153">14428</EventID>
        <TimeCreated SystemTime="2009-10-30T19:09:46.000000000Z" />
        <Channel>Office Communications Server</Channel>
        <Security />
        <Data>Unspecified error</Data>

    Friday, October 30, 2009 8:52 PM


  • Sorry, it was my mistake, problem solved, I was using an incorrect certificate, I was using a web certificate, I create a computer certificate then I can activate without problem.

    Friday, October 30, 2009 9:04 PM