• 4043636 Skype for Business on Mac can’t retrieve meeting information in Skype for Business Server 2015

This issue occurs because the Unified Communications Web API (UCWA) module in Skype for Business Front End server doesn’t implement this feature.

• 4043634 Sign-in dialog box is always displayed when you try to access external web services in Skype for Business Server 2015

• 4043638 Incorrect format of location information about an E911 call from Skype for Business on Mac

• 4043641 Update to add a Strict-Transport-Security header to the path of all web service responses in Skype for Business Server 2015

• 4043637 Update to enable Skype for Business on Mac to restrict external access in Skype for Business Server 2015

• Globally

  Set-CsPlatformServiceSettings -EnableExternalAccessCheck $false

• On a per-user basis

  Set-CsExternalAccessPolicy -EnableOutsideAccess $false

• 4043633 Synthetic transactions fail after installing February 2017 update for Skype for Business Server 2015

Error Message: Failed creating application activity.

Inner Exception: Method not found:

‘System.Threading.Tasks.Task`1

<Microsoft.Rtc.Internal.

Ucwa.ClientModel.Interfaces.IHttpResult>

Microsoft.Rtc.Internal.

Ucwa.ClientModel.Interfaces.

IMeService.MakeMeAvailableAsync(Microsoft.Rtc.Internal.Ucwa.ClientModel.

ApplicationSignInProperties)’.

• 4043635 You cannot sign in Web Scheduler in Skype for Business Server 2015

• 4036633 “We can’t sign you in because you aren’t set up to use Skype for Business” error in Skype for Business Server 2015

• You run the Set-CsPlatformServiceSettings cmdlet to set the value of the enableExternalAccessCheck parameter to true in Microsoft Skype for Business Server 2015.
• You run the Set-CsExternalAccessPolicy cmdlet to set the value of the EnableOutsideAccess parameter to false per user.

In this scenario, when you try to sign in to Unified Communications Web API (UCWA) clients, you receive the following error message:

We can’t sign you in because you aren’t set up to use Skype for Business. Please contact your support team

After you apply this update, you receive the following error message:

Your account does not allow access from outside your organization’s network. Please contact your organization’s network and then try signing in

• 4036631 Can’t join an application sharing session of meeting in Skype for Business Server 2015 that has May 2017 update applied

• You apply May 2017 cumulative update for Microsoft Skype for Business Server 2015.
• Some Video-based Screen Sharing (VbSS) supported clients and legacy clients are in a Skype for Business meeting.

In this scenario, you might be unable to join the application sharing session of the meeting.

This issue occurs because Skype for Business Application Sharing Server (ASMCU) doesn’t include the rtcp-mux attribute in the Session Description Protocol (SDP) after the application sharing session is failed from VbSS to the remote desktop protocol (RDP) session.

• 4036632 UCWA clients still can sign in from external networks when the external access is disabled in Skype for Business Server 2015

• You run the Set-CsExternalAccessPolicy cmdlet to set the value of the EnableOutsideAccess parameter to false in Microsoft Skype for Business Server 2015.
• Users are using Microsoft Skype for Business mobile apps and Microsoft Skype for Business on Mac clients.

In this scenario, Unified Communications Web API (UCWA) clients still can sign in from external networks even if the external access setting is disabled by the policy.

• 4036630 Can’t schedule or join a meeting after you apply May 2017 Cumulative Update for Skype for Business Server 2015

• You apply May 2017 Cumulative Update for Microsoft Skype for Business Server 2015.
• The version of .Net Framework that’s installed on the Skype for Business Server 2015 Front-End Server is less than 4.6.2.
• You enable the System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing security setting on the Front-end Server.

In this scenario, you can’t schedule or join a meeting by using the Meet Now option or Outlook Skype Meeting add-in.

This issue occurs because Meeting functionality dependency: SHA256 Managed implementation is incompatible with Federal Information Processing Standard (FIPS) guidelines in Cumulative Update 5.

• 4036625 Enables the peer-to-peer file transfer feature for Skype for Business on Mac clients in Skype for Business Server 2015

• 4036627 Event ID 16385 floods in Skype for Business Server 2015 Director pools

Log Name: Microsoft-Windows-WindowsFabric/Admin

Source: Microsoft-Windows-WindowsFabric

Date: Date/Time

Event ID: 16385

Task Category: Reliability

Level: Warning

Keywords: Default

User: NETWORK SERVICE

Computer: computer-FQDN NAME

Description: FM resolving failed with FABRIC_E_PARTITION_NOT_FOUND Event Xml

This issue occurs because the Windows Fabric cluster isn’t set up properly in Skype for Business Server 2015 Director pools that have more than two servers.

• 4023993 LS Data MCU events 41024, 41025 and 41026 are constantly generated after you install the May 2017 .NET Framework update

• You deploy Microsoft Lync Server 2010, Microsoft Lync Server 2013, or Microsoft Skype for Business Server 2015.
• The Microsoft .NET Framework 4.5.2 or a later version is installed (Lync Server 2013 or Skype for Business Server 2015).
• You install the May 2017 .NET Framework Security and Quality Rollup.

In this scenario, you experience the following symptoms:

• Web Applications users cannot use some features such as PowerPoint presentations, Q&A sites, and whiteboard sharing.
• Shared Object Messaging (PSOM) protocol connectivity with Microsoft Edge fails.
• External users cannot use such features as PowerPoint presentations, Q&A pages, or Whiteboard sharing.
• The Lync Server 2010, Lync Server 2013, or Skype for Business Server 2015 Front End server generates the following LS Data MCU event 41026 error.

  Note The Front End server alternatingly generates this event and event 41025. Event 41025 states that connectivity has succeeded.

  Log Name: Lync Server
  Source: LS Data MCU
  Date: Date/Time
  Event ID: 41024
  Task Category: (1018)
  Level: Error
  Keywords: Classic
  User: N/A
  Computer: FrontEnd-computer-FQDN
  Description:
  No connectivity with one of the Web Conferencing Edge Servers.
  Edge Server Machine FQDN: Edge-computer-FQDN, Port:XXXX
  If the problem persists this event will be logged again after 20 minutes
  Cause: Service may be unavailable or Network connectivity may have been compromised.

  Log Name: Lync Server
  Source: LS Data MCU
  Date: Date/Time
  Event ID: 41025
  Task Category: (1018)
  Level: Information
  Keywords: Classic
  User: N/A
  Computer: FrontEnd-computer-FQDN
  Description:
  Connection to the Web Conferencing Edge Server has succeeded
  Edge Server Machine FQDN: Edge-computer-FQDN, Port:XXXX

  Log Name:      Lync Server
  Source:        LS Data MCU
  Date:          date time
  Event ID:      41026
  Task Category: (1018)
  Level:         Error
  Keywords:      Classic
  User:          N/A
  Computer:      frontend1.contoso.com
  Description:
  No connectivity with any of Web Conferencing Edge Servers. External Lync clients cannot use Web Conferencing modality.
  Cause: Service may be unavailable or Network connectivity may have been compromised.
  Resolution:
  Verify all Web Conferencing Edge Services in the topology are running, and network connectivity is available.

• 4036621 Mid-call control like “Stop my video” fails if a call occurs from a VTC endpoint in Skype for Business Server 2015

• You integrate Video Interop Server (VIS) with Cisco Unified Communication Manager (CUCM) in a Microsoft Skype for Business Server 2015 environment.
• You use a Cisco teleconferencing system (VTC) endpoint, such as SX20 to make a call to a Skype for Business client.
• An Audio/Video call is established between the endpoint and the client.

In this scenario, after some seconds, when the Skype for Business client makes some mid-call controls, such as clicking stop my video or start my video, or both options, the call is dropped.

This issue occurs because after Skype for Business client answers an incoming call from Cisco VTC endpoint, VIS keeps sending INVITEs request to Cisco VTC or CUCM every second. However, Cisco VTC endpoint starts to reply 503 service unavailable from the 24th INVITE onwards. Therefore, VIS drops both legs of the call when Skype for Business client does a mid-call control operation.

• 4036622 “ONLINE_USER_COUNT_SETTING is immutable” error occurs if you manage chat user roles with BeginAddUsersOrGroupsToRole

• You are a developer in a Microsoft Skype for Business Server 2015 environment.
• You use Persistent Chat Software Development Kit (SDK) to manage user roles in a chat room by invoking BeginAddUsersOrGroupsToRole method.

In this scenario, the method call may fail, and you receive the following error message:

NodeSetting.ONLINE_USER_COUNT_SETTING is immutable

This issue occurs because room search command tries to set a parameter value that’s an external read-only field

• 4036623 “Action couldn’t be completed” error when you upload a file to a persistent chat room in Skype for Business Server 2015

The action couldn’t be completed. Please try again later.

This issue occurs because the program cannot convert the file name that’s encoded by UTF-8.

• 4036615 Sets the default value of the “EnableDelegateManagement” attribute to “true” in Skype for Business Server 2015

• 4036614 “From number” is missing in the Peer-to-Peer Session Detail Report when you dial a PSTN number in Skype for Business Server 2015

This issue occurs because the Microsoft Unified Communication Web API (UCWA) does not send TelNumber in P2PSessiondata.

• 4036620 Can’t join meeting by using Skype for Business Room System or Surface Hub devices in Skype for Business Server 2015

This issue occurs because all subsequent sign-in processes fail for these devices after a rare race condition occurs in Microsoft Skype for Business Server 2015 Front End service.

• 4036618 Meeting URLs are visible in search results of a search engine in Skype for Business Server 2015

• You schedule a Microsoft Skype for Business meeting.
• The meeting URL is posted somewhere publicly online.

In this scenario, when you search for “Skype for Business Web App” in search engines such as Google, Bing or Yahoo, you can see the meeting URL publicly.

Additionally, other people can join the meeting randomly if you enable the anonymous meeting join feature.

This issue occurs because search engines browse the public site, see the meet.lync.com URL, then crawl it, and index it into the search engines.

• 4036619 Lync or Skype for Business client can’t be started to join meeting if default browser is Firefox 52 or a later version

This issue occurs because the Netscape Plugin Application Programming Interface (NPAPI) plugin is deprecated in Firefox 52 or a later version. NPAPI is currently used as part of the client detection process for the Lync or Skype for Business client when you join a meeting by clicking a link. When NPAPI is disabled, the webpage can’t determine whether you have the client installed.

• 4036612 Event Id 53530 is logged and connection to SQL database is lost in Skype for Business Server 2015 Persistent Chat Server

Time: Date/Time

ID: 53530

Level: Error

Source: LS Persistent Chat Server

Machine: ServerName

Message: The Persistent Chat database connection was lost.

The Skype for Business Server 2015, Persistent Chat lost connection to the database using connection string:

Data Source=sql.contoso.com;Initial Catalog=mgc;Integrated Security=SSPI;

Cause: An unexpected error occurred that caused the loss of the Persistent Chat database connection.

Resolution:

Check the state of the database.

This issue occurs because the procProcessADUpdates stored procedure takes more than 30 seconds to run. Default Skype for Business Server 2015 Persistent Chat Servertime-out is 30 seconds so that the stored procedure execution will be aborted.

• 4036617 User move fails and many SIP messages are queued after you apply August 2016 update for Skype for Business Server 2015

• You deploy multiple Front-End pools
• You deploy the August 2016 Cumulative Update
• You move users between these Front-End pools

In this scenario, the user move fails. Additionally, you see many SIP messages are queued on Front-End servers.

This issue occurs because of a failure in the RtcUpdateResourceAttributes stored procedure that’s caused by time-out.