locked
Lync 2010 Integration with Exchange 2010 SP2 OWA RRS feed

  • Question

  • I am facing a very strange issue

    as per the subject i have exchaneg 2010 sp2 and when integrating with Lync 2010  , the owa is not working

    in the logs i am getting the below error

    TL_ERROR(TF_CONNECTION) [0]027C.2E44::04/23/2012-15:18:16.961.00011cea (SIPStack,SIPAdminLog::TraceConnectionRecord:SIPAdminLog.cpp(160))$$begin_record
    LogType: connection
    Severity: error
    Text: The peer is not a configured server on this network interface
    Peer-IP: X.X.X.X:34578
    Transport: TLS
    Result-Code: 0xc3e93d6a SIPPROXY_E_CONNECTION_UNKNOWN_SERVER
    Data: fqdn="web.mail.X.Y"
    $$end_record

    the Name of the cert is the same name as the trusted application


    john yassa

    Sunday, May 6, 2012 6:57 PM

Answers

  • Hi,John,

    Seems you have the external exchange FQDN web.mail.x.y as the subject name,would you please creating a new cert in Exchange (against internal CA) with the subject as the machine's internal FQDN,configure the InstantMessaging parameters with new certificate thumbprint and do IISreset to see if it works?

    You can refer Jeff's blog to configure Lync and Exchange OWA integration.

    http://blog.schertz.name/2010/11/lync-and-exchange-im-integration/

    And here is another blog post mentioned the same error "The peer is not a configured server on this network interface" when create trust application for your reference.

    http://mikestacy.typepad.com/mike-stacys-blog/2010/09/creating-static-routes-in-lync-server-2010.html

    Hope these useful!

    B/R

    Sharon


    Sharon Shen

    TechNet Community Support

    ************************************************************************************************************************

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.

    Tuesday, May 8, 2012 7:59 AM
    Moderator

All replies

  • That means that Lync is not allowed to talk to the Exchange Server

    Did you publish the Topology after making the changes?


    - Belgian Unified Communications Community : http://www.pro-lync.be -

    Tuesday, May 8, 2012 7:54 AM
  • Hi,John,

    Seems you have the external exchange FQDN web.mail.x.y as the subject name,would you please creating a new cert in Exchange (against internal CA) with the subject as the machine's internal FQDN,configure the InstantMessaging parameters with new certificate thumbprint and do IISreset to see if it works?

    You can refer Jeff's blog to configure Lync and Exchange OWA integration.

    http://blog.schertz.name/2010/11/lync-and-exchange-im-integration/

    And here is another blog post mentioned the same error "The peer is not a configured server on this network interface" when create trust application for your reference.

    http://mikestacy.typepad.com/mike-stacys-blog/2010/09/creating-static-routes-in-lync-server-2010.html

    Hope these useful!

    B/R

    Sharon


    Sharon Shen

    TechNet Community Support

    ************************************************************************************************************************

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.

    Tuesday, May 8, 2012 7:59 AM
    Moderator
  • Hi there,

    I'm experiencing a similar issue with Exchange 2010 SP2 and Lync IM integration on Windows 2008 R2 64bit Enterprise Server. I'm following the blog here: http://blog.schertz.name/2010/11/lync-and-exchange-im-integration/

    The problem I'm encountering is on running CWAOWASSP.Msp to upgrade Microsoft Office Communications Server 2007 R2, Web Service Provider Install Package verison 3.5.6907.57 to 3.5.6907.202 as described in the blog above.

    On running this I receive the message "The upgrade patch cannot be installed by the Windows Install service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program".

    However, I can see OCS 2007 R2 WSP version 3.5.6907.57 is installed.

    Could this be due to the fact I'm using Exchange 2010 SP2 Unified Communcations edition?

    Thanks,

    Chris L.

    Wednesday, September 19, 2012 8:57 PM
  • Managed to resolve this.

    I uninstalled Microsoft Unified Communucations Managed API. Installed this http://www.microsoft.com/downloads/en/details.aspx?familyid=CA107AB1-63C8-4C6A-816D-17961393D2B8&displaylang=en, it extracts several files to the installation path, I then installed these starting with UmcaRedist.msi followed by CWAOWASSP.Msi. This created the dll required c:\exchange\Microsoft.Rtc.UCWeb.dll which I then moved to {ExchangeDir}\Client Access\Owa\Bin and referenced in the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchange OWA\InstantMessaging\ImplementationDllPath string.

    Wednesday, September 19, 2012 10:10 PM