{"id":241,"date":"2014-08-12T21:58:28","date_gmt":"2014-08-12T19:58:28","guid":{"rendered":"http:\/\/www.vatland.no\/?p=241"},"modified":"2014-08-12T21:58:28","modified_gmt":"2014-08-12T19:58:28","slug":"lync-federation-failes-for-some-partners","status":"publish","type":"post","link":"https:\/\/www.vatland.no\/index.php\/lync-federation-failes-for-some-partners\/","title":{"rendered":"Lync federation failes for some partners."},"content":{"rendered":"

\"Lync2013\"<\/a>You have installed Lync edge server and have\u00a0issues federating with some or all of your partners. If you check the eventlog you might see multiple errors\u00a0like \u00a0event Source\u00a0:\u00a0“LS Protocol Stack” and Event ID 14428.<\/p>\n

\"LyncEdge2\"<\/a><\/p>\n

Event description might mislead you to think that there is something wrong with\u00a0your partners certificate.\u00a0 The text state that “Target principal name name is incorrect means that the peer certificate does not contain the name that the local server used to connect…”. Also the event mentions the DNS name of your partners edge server.<\/p>\n

\"LyncEdge3\"<\/a><\/p>\n

This could\u00a0be as easy asthat \u00a0you have not imported the intermediate certificate authority certificates. Download the Intermediate certificates from the\u00a0certificate authority issuing the\u00a0public\/external\u00a0certificate . Import this\/them into the local machine certificate store of the edge server.<\/p>\n

The reason\u00a0for federation to\u00a0fail only with some partners are that they have probably\u00a0not\u00a0update Windows on their edge server for a while.<\/p>\n","protected":false},"excerpt":{"rendered":"

You have installed Lync edge server and have\u00a0issues federating with some or all of your partners. If you check the eventlog you might see multiple errors\u00a0like \u00a0event Source\u00a0:\u00a0“LS Protocol Stack” and Event ID 14428.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[6,10],"tags":[19,17,18],"class_list":["post-241","post","type-post","status-publish","format-standard","hentry","category-lync","category-windows","tag-certificates","tag-event-id","tag-lync-edge-server"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_likes_enabled":false,"jetpack-related-posts":[{"id":57,"url":"https:\/\/www.vatland.no\/index.php\/lync-phone-unable-to-sign-in-after-windows-update-on-lync-server\/","url_meta":{"origin":241,"position":0},"title":"Lync phone unable to sign in after windows update on Lync Server.","author":"Atle","date":"January 2, 2013","format":false,"excerpt":"After update to Root Sertificates ( KB931125) http:\/\/support.microsoft.com\/kb\/931125\u00a0You are constantly getting Warning in the eventlog. Also Lync Phones will be unable to sign in. The error message on the phone is that the \"Registrar FQDN could not be resolved\". UPDATED: On new Phones you will only get a message that\u2026","rel":"","context":"In "Lync"","block_context":{"text":"Lync","link":"https:\/\/www.vatland.no\/index.php\/category\/lync\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":645,"url":"https:\/\/www.vatland.no\/index.php\/exchange-um-event-id-1400\/","url_meta":{"origin":241,"position":1},"title":"Exchange UM event ID 1400","author":"Atle","date":"February 12, 2016","format":false,"excerpt":"This is a rather confusing event. It occurs on the Exchange server 2010 that is holding the Unified Messaging role. \"The following UM IP gateways did not respond as expected to a SIP OPTIONS request\", and at the end \"This operation has timed out\". The server mentioned in the erro\u2026","rel":"","context":"In "Exchange"","block_context":{"text":"Exchange","link":"https:\/\/www.vatland.no\/index.php\/category\/exchange\/"},"img":{"alt_text":"exevent1400","src":"https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2016\/02\/exevent1400.jpg?resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2016\/02\/exevent1400.jpg?resize=350%2C200 1x, https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2016\/02\/exevent1400.jpg?resize=525%2C300 1.5x"},"classes":[]},{"id":277,"url":"https:\/\/www.vatland.no\/index.php\/lync-server-2010-rtchost-exe-crashes-after-windows-update\/","url_meta":{"origin":241,"position":2},"title":"Lync server 2010 rtchost.exe crashes after Windows Update.","author":"Atle","date":"September 11, 2014","format":false,"excerpt":"\u00a0After running Windows update on a Lync 2010 edge server\u00a0I was unable to communicate with external contacts. I could see their presence but no\u00a0chat\/video or audio.\u00a0The eventlog contained lots of event 1001 \"Information\"(Why\u00a0not error\u00a0!!!!!) that RTCHOST.EXE crashed. Probably failed installation of KB2982385. Why are these only information events. Even more\u2026","rel":"","context":"In "Lync"","block_context":{"text":"Lync","link":"https:\/\/www.vatland.no\/index.php\/category\/lync\/"},"img":{"alt_text":"Lync2013","src":"https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2014\/05\/Lync2013.gif?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":56,"url":"https:\/\/www.vatland.no\/index.php\/lync-edge-server-stopped-replicating-cms\/","url_meta":{"origin":241,"position":3},"title":"Lync Edge server stopped replicating CMS","author":"Atle","date":"January 3, 2013","format":false,"excerpt":"At some time Lync\u00a0edge server stopped replicating changes\u00a0in configuration. Also a\u00a0\"get-csmanagementstorereplicationstatus\" show False on\u00a0Edge server. Investigation shows\u00a0that the firewall has not changed and you can telnet from frontend to edge on port 4443. Alse got\u00a0the same error\u00a0in systemlog on edge server\u00a0: Description: When asking for client authentication, this server sends\u2026","rel":"","context":"In "Lync"","block_context":{"text":"Lync","link":"https:\/\/www.vatland.no\/index.php\/category\/lync\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":408,"url":"https:\/\/www.vatland.no\/index.php\/keep-your-lync-public-certificates-up-to-date\/","url_meta":{"origin":241,"position":4},"title":"Keep Your Lync Public certificates up to date.","author":"Atle","date":"January 15, 2015","format":false,"excerpt":"Here is one reason why you should cleanup SAN's in your certificates.\u00a0Experienced\u00a0one scenario where a customer moved from one hosting provider to another and was unable to federate after the\u00a0move.\u00a0 This is not\u00a0about defining these hosting providers in the \"hosting provider\" configuration in Lync. The reason to do that\u00a0is if\u2026","rel":"","context":"In "Lync"","block_context":{"text":"Lync","link":"https:\/\/www.vatland.no\/index.php\/category\/lync\/"},"img":{"alt_text":"ssl-certificate","src":"https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2015\/01\/ssl-certificate-300x300.jpg?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":55,"url":"https:\/\/www.vatland.no\/index.php\/abserver-exe-crashes-every-4-minutes\/","url_meta":{"origin":241,"position":5},"title":"ABServer.exe crashes every 4 minutes.","author":"Atle","date":"January 4, 2013","format":false,"excerpt":"Issue: Abserver.exe in Lync crashes every 4 minutes. Event ID 12330:Failed starting a worker process. Process: 'C:\\Program Files\\Microsoft Lync Server 2010\\Server\\Core\\ABServer.exe' Exit Code: C3E8302D!_HRX! (The worker process failed to initialize itself in the maximum allowable time.!_HRM!). Cause: This could happen due to low resource conditions or insufficient privileges. Resolution: Try\u2026","rel":"","context":"In "Lync"","block_context":{"text":"Lync","link":"https:\/\/www.vatland.no\/index.php\/category\/lync\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/posts\/241","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/comments?post=241"}],"version-history":[{"count":3,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/posts\/241\/revisions"}],"predecessor-version":[{"id":247,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/posts\/241\/revisions\/247"}],"wp:attachment":[{"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/media?parent=241"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/categories?post=241"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/tags?post=241"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}