Forum Discussion
Welcome everyone to the Skype for Business Server 2019 Preview Forum!
Already running SfB 2019 Server - but discovered some bug's that should be fixed in an upcoming CU.
Can you give any hint about the release of the CU or any hotfixes for SfB 2019?
Kind regards
Karsten
Karsten_Stolten We are working on the first CU. Can you share what the problem is?
- Karsten_StoltenMar 26, 2019Copper ContributorHi Rohit
Thank you for your reply!
It is an issue with search for external/public Skype contact (through Skype Phone book).
It does it work. MS support has identified it as a bug and said it would be fixed in the CU.
/Karsten- Rohit_Gupta_25Mar 27, 2019Brass Contributor
Karsten_Stolten We are aware of it, and working to include it in the first CU that comes out later this year. Hope this helps.
- Karsten_StoltenMar 27, 2019Copper Contributor
Thanks again for getting back.
Great to hear that the issue is addressed.
Any workarounds/hacks/hotfixes are much appriciated! :o)
"Later this year" - is that like Within a few days, weeks or months?
/Karsten
- Karsten_StoltenMar 26, 2019Copper ContributorHi Rohit
Thank you for your reply!
It is an issue with search for external/public Skype contact (through Skype Phone book).
It does it work. MS support has identified it as a bug and said it would be fixed in the CU.
/Karsten- James1May 07, 2019Brass Contributor
Hello Karsten_Stolten .
Can you please specify how did you identified the problem? Were there any errors, eventview logs?
Im having the same issue.
Is there any news about upcoming CU? Did you manage to fix the issue? And is there any official MS statement regarding this bug? It is a major issue.
Regards,
- Karsten_StoltenMay 07, 2019Copper Contributor
Hi James1
The following event is logged in the Application log on the frontend server when trying to search for public Skype (or SfB) contacts:
"Skype search request failed. Exception information : Fault occurred while attempting to proxy WCF message..."
I had a session with Microsoft Support and we gathered some logfiles from the server. The support representative confirmed the capture of the error in the logs and confirmed that a fix for this will be included in the upcoming CU. I have not seen any official statement regarding this specific problem/bug so this I guess, will be the closest you get to any aknowledgement… (so far)
The issue is not fixed and I have asked for workarrounds but unfortunately there is nothing to do but to wait for the CU.
Kind regards
Karsten Stolten