%3CLINGO-SUB%20id%3D%22lingo-sub-1106616%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20Skype%20Directory%20Search%20Service%20Connections%20May%20Fail%20if%20TLS%201.2%20Is%20Not%20Enabled%20on%20Ed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1106616%22%20slang%3D%22en-US%22%3E%3CP%3EAll%20I%20had%20to%20do%20was%20enter%20the%20registry%20keys%20here%20and%20reboot%20the%20edge%20server%20-%20took%20a%20few%20minutes%2C%20then%20started%20working%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fmanage%2Ftopology%2Fdisable-tls-1.0-1.1%23pre-requisite-registry-keys%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fmanage%2Ftopology%2Fdisable-tls-1.0-1.1%23pre-requisite-registry-keys%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1110013%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20Skype%20Directory%20Search%20Service%20Connections%20May%20Fail%20if%20TLS%201.2%20Is%20Not%20Enabled%20on%20Ed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1110013%22%20slang%3D%22en-US%22%3E%3CP%3EI%20had%20to%20install%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fmanage%2Ftopology%2Fdisable-tls-1.0-1.1%23pre-requisite-registry-keys%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eprerequisite%20registry%20keys%3C%2FA%3E%20and%20update%20.Net%20from%204.5%20to%204.7%20on%20the%20edge%20used%20for%20federation%20to%20resolve%20the%20issue.%26nbsp%3B%20We%20still%20use%20LPE%20so%20not%20disabling%20TLS%201.0%20allowed%20those%20phones%20to%20continue%20working.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1164180%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20Skype%20Directory%20Search%20Service%20Connections%20May%20Fail%20if%20TLS%201.2%20Is%20Not%20Enabled%20on%20Ed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1164180%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20updates%20on%20this%20topic%3F%3C%2FP%3E%3CP%3EWe%20had%20the%20issue%20for%20about%20a%20week%20ago%20and%20now%20it's%20working%20without%20we%20have%20to%20do%20any%20changes%20on%20the%20edge%20servers.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDid%20MS%20team%20found%20and%20fix%20something%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1212033%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%3A%20Skype%20Directory%20Search%20Service%20Connections%20May%20Fail%20if%20TLS%201.2%20Is%20Not%20Enabled%20on%20Ed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1212033%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F40331%22%20target%3D%22_blank%22%3E%40Luis%20Ramos%3C%2FA%3E%26nbsp%3Bapologies%20for%20the%20delayed%20response%2C%20yes%2C%20indeed%20TLS%201.0%2F1.1%20were%20re-enabled%20on%20skypgraph.skype.com%20so%20this%20should%20no%20longer%20be%20an%20issue.%26nbsp%3B%20They%20were%20disabled%20early%20by%20mistake.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1106499%22%20slang%3D%22en-US%22%3EKnown%20Issue%3A%20Skype%20Directory%20Search%20Service%20Connections%20May%20Fail%20if%20TLS%201.2%20Is%20Not%20Enabled%20on%20Edge%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1106499%22%20slang%3D%22en-US%22%3E%3CP%3E%3CEM%3E%3CSTRONG%3EOur%20investigation%20determined%20TLS%201.0%2F1.1%20were%20disabled%20pre-maturely%20on%20Skypegraph.skype.com%20-%20based%20on%20your%20feedback%20we%20re-enabled%20those%20protocols.%26nbsp%3B%20We%20apologize%20for%20the%20inconvenience.%26nbsp%3B%20%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%E2%80%99re%20investigating%20an%20emerging%20issue%20with%20%3CA%20title%3D%22deploy%20skype%20connectivity%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fdeploy%2Fdeploy-skype-connectivity%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESkype%20Directory%20Search%3C%2FA%3E%20for%20Skype%20for%20Business%20On-Premises%20to%20Skype%20Consumer%20chat%20capability.%20When%20searching%20for%20a%20Skype%20account%20in%20the%20Skype%20for%20Business%20Client%2C%20you%20might%20get%20the%20following%20error%20message%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3EAn%20error%20occurred%20during%20the%20search.%20Please%20try%20again%2C%20and%20contact%20your%20support%20team%20if%20the%20problem%20continues.%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAdditionally%2C%20you%20may%20find%20the%20following%20error%20in%20the%20Lync%20event%20log%20on%20the%20impacted%20Edge%20servers%3A%3C%2FP%3E%0A%3CPRE%3ELog%20Name%3A%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3BLync%20Server%3CBR%20%2F%3ESource%3A%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3BLS%20Web%20Components%20Server%3CBR%20%2F%3EDate%3A%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B1%2F13%2F2020%208%3A53%3A26%20AM%3CBR%20%2F%3EEvent%20ID%3A%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B4106%3CBR%20%2F%3ETask%20Category%3A%20(1074)%3CBR%20%2F%3ELevel%3A%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20Error%3CBR%20%2F%3EKeywords%3A%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3BClassic%3CBR%20%2F%3EUser%3A%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3BN%2FA%3CBR%20%2F%3EComputer%3A%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3BCE1210R2.contoso.com%3CBR%20%2F%3EDescription%3A%3CBR%20%2F%3EThe%20server%20selected%20for%20next%20hop%20could%20not%20be%20reached%2C%20or%20did%20not%20reply.%3CBR%20%2F%3E%3CBR%20%2F%3EA%20server%20selected%20as%20a%20proxy%20target%20for%20HTTP%20traffic%20could%20not%20be%20reached%20or%20did%20not%20reply%3A%20skypegraph.skype.com.%26nbsp%3B%3CBR%20%2F%3EPerformance%20Counter%20Instance%3A%20%26nbsp%3B%3CBR%20%2F%3EFailure%20occurrences%3A%204%2C%20since%201%2F13%2F2020%204%3A51%3A18%20PM.%26nbsp%3B%3CBR%20%2F%3EFailure%20Details%3A%20WebException%3A%20The%20underlying%20connection%20was%20closed%3A%20An%20unexpected%20error%20occurred%20on%20a%20send.%3CBR%20%2F%3ECause%3A%20The%20remote%20server%20may%20be%20experiencing%20problems%20or%20the%20network%20is%20not%20available%20between%20these%20servers.%3CBR%20%2F%3EResolution%3A%3CBR%20%2F%3EExamine%20the%20event%20logs%20on%20the%20indicated%20server%20to%20determine%20the%20cause%20of%20the%20problem.%3C%2FPRE%3E%0A%3CP%3EBased%20on%20our%20initial%20investigation%20it%20appears%20that%20the%20Skype%20Directory%20Search%20endpoints%20are%20refusing%20TLS%201.0%20connections.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EWorkaround%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3ETo%20fix%20this%20issue%20you%20need%20to%20enable%20your%20Edge%20servers%20to%20use%20TLS%201.2.%26nbsp%3B%20Your%20Lync%20or%20Skype%20for%20Business%20Servers%20may%20require%20dependency%20updates%2C%20including%20.Net%20framework%20updates.%26nbsp%3B%20All%20the%20requirements%20for%20enabling%20TLS%201.2%20are%20documented%20here%3A%3C%2FP%3E%0A%3CP%3E%3CFONT%20size%3D%221%22%3E%3CA%20title%3D%22disable%20TLS%20sfb%202015%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fmanage%2Ftopology%2Fdisable-tls-1.0-1.1%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CSPAN%20style%3D%22text-align%3A%20left%3B%20color%3A%20%23171717%3B%20text-transform%3A%20none%3B%20line-height%3A%201.3%3B%20text-indent%3A%200px%3B%20letter-spacing%3A%20normal%3B%20font-family%3A%20Segoe%20UI%2CSegoeUI%2CSegoe%20WP%2CHelvetica%20Neue%2CHelvetica%2CTahoma%2CArial%2Csans-serif%3B%20font-size%3A%202.5rem%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20text-decoration%3A%20none%3B%20word-spacing%3A%200px%3B%20display%3A%20inline%20!important%3B%20white-space%3A%20normal%3B%20orphans%3A%202%3B%20float%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20overflow-wrap%3A%20break-word%3B%20background-color%3A%20%23ffffff%3B%22%3EDisable%20TLS%201.0%2F1.1%20in%20Skype%20for%20Business%20Server%202015%3C%2FSPAN%3E%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENote%2C%20this%20procedure%20is%20also%20supported%20on%20Lync%20Server%202013%2C%20for%20more%20information%20refer%20to%20the%20following%20blog%20post%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20title%3D%22tls%20blog%22%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fskype-for-business-blog%2Fdisabling-tls-1-0-1-1-in-skype-for-business-server-2015-part-1%2Fba-p%2F621485%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3EDisabling%20TLS%201.0%2F1.1%20in%20Skype%20for%20Business%20Server%202015%3A%20Part%201%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOnce%20all%20the%20pre-requisite%20software%20updates%20are%20completed%2C%20you%20then%20need%20to%20deploy%20the%20%3CA%20title%3D%22prerequisite%20registry%20keys%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fmanage%2Ftopology%2Fdisable-tls-1.0-1.1%23pre-requisite-registry-keys%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eprerequisite%20registry%20keys%3C%2FA%3E.%20This%20will%20enable%20your%20Edge%20servers%20to%20negotiate%20TLS%201.2%20connections%20to%20the%20Skype%20Graph%20web%20service%20endpoints.%20You%20do%20NOT%20need%20to%20%3CSTRONG%3Edisable%3C%2FSTRONG%3E%20TLS%201.0%20on%20the%20impacted%20Edge%20servers.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EMore%20Information%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EOur%20investigation%20determined%20TLS%201.0%2F1.1%20were%20disabled%20prematurely%20on%20skypegraph.skype.com%20endpoints.%26nbsp%3B%20You%20should%20no%20longer%20have%20to%20set%20pre-requisites%20to%20work%20around%20this%20issue.%26nbsp%3B%20We%20apologize%20for%20the%20inconvenience.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1106499%22%20slang%3D%22en-US%22%3E%3CP%3EWe%E2%80%99re%20investigating%20an%20emerging%20issue%20with%20Skype%20Directory%20Search%20for%20Skype%20for%20Business%20On-Premises%20to%20Skype%20Consumer%20chat%20capability.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1106499%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ENextHop%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESkype%20for%20Business%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

Our investigation determined TLS 1.0/1.1 were disabled pre-maturely on Skypegraph.skype.com - based on your feedback we re-enabled those protocols.  We apologize for the inconvenience. 

 

We’re investigating an emerging issue with Skype Directory Search for Skype for Business On-Premises to Skype Consumer chat capability. When searching for a Skype account in the Skype for Business Client, you might get the following error message:

 

An error occurred during the search. Please try again, and contact your support team if the problem continues.

 

Additionally, you may find the following error in the Lync event log on the impacted Edge servers:

Log Name:      Lync Server
Source:        LS Web Components Server
Date:          1/13/2020 8:53:26 AM
Event ID:      4106
Task Category: (1074)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      CE1210R2.contoso.com
Description:
The server selected for next hop could not be reached, or did not reply.

A server selected as a proxy target for HTTP traffic could not be reached or did not reply: skypegraph.skype.com. 
Performance Counter Instance:  
Failure occurrences: 4, since 1/13/2020 4:51:18 PM. 
Failure Details: WebException: The underlying connection was closed: An unexpected error occurred on a send.
Cause: The remote server may be experiencing problems or the network is not available between these servers.
Resolution:
Examine the event logs on the indicated server to determine the cause of the problem.

Based on our initial investigation it appears that the Skype Directory Search endpoints are refusing TLS 1.0 connections.

 

Workaround:

To fix this issue you need to enable your Edge servers to use TLS 1.2.  Your Lync or Skype for Business Servers may require dependency updates, including .Net framework updates.  All the requirements for enabling TLS 1.2 are documented here:

Disable TLS 1.0/1.1 in Skype for Business Server 2015

 

Note, this procedure is also supported on Lync Server 2013, for more information refer to the following blog post: 

Disabling TLS 1.0/1.1 in Skype for Business Server 2015: Part 1

 

Once all the pre-requisite software updates are completed, you then need to deploy the prerequisite registry keys. This will enable your Edge servers to negotiate TLS 1.2 connections to the Skype Graph web service endpoints. You do NOT need to disable TLS 1.0 on the impacted Edge servers.

 

More Information:

Our investigation determined TLS 1.0/1.1 were disabled prematurely on skypegraph.skype.com endpoints.  You should no longer have to set pre-requisites to work around this issue.  We apologize for the inconvenience.  

4 Comments

All I had to do was enter the registry keys here and reboot the edge server - took a few minutes, then started working: https://docs.microsoft.com/en-us/skypeforbusiness/manage/topology/disable-tls-1.0-1.1#pre-requisite-...

New Contributor

I had to install the prerequisite registry keys and update .Net from 4.5 to 4.7 on the edge used for federation to resolve the issue.  We still use LPE so not disabling TLS 1.0 allowed those phones to continue working.

Occasional Contributor

Any updates on this topic?

We had the issue for about a week ago and now it's working without we have to do any changes on the edge servers.

 

Did MS team found and fix something?

Microsoft

@Luis Ramos apologies for the delayed response, yes, indeed TLS 1.0/1.1 were re-enabled on skypgraph.skype.com so this should no longer be an issue.  They were disabled early by mistake.