Symptoms
In a Microsoft Skype for Business Server 2019 or Skype for Business Server 2015 environment, you receive the following error message in the user's Skype for business App log of a UCWA client (Skype for Business on Mac, Skype for Business for Android, or Skype for Business for iOS) or in the WebInfrastructure CLS component of the server logs:
X-Ms-diagnostics 28042; reason="Too many outstanding requests for a single user.This issue prevents the user from signing in to the UCWA clients.
Cause
This error message can occur because of several causes that lead to the user having 40 outstanding requests with the server. Our analysis of the issue points to the pending connection requests between Skype for Business and Exchange Servers being one of the causes. You can further check for EventID: 32019 in the Application event logs, and run the Test-CsExStorageConnectivity synthetic transition to confirm that the connectivity exists between Skype for Business and Exchange Servers.
Resolution
We have introduced a design change to time out the pending connections instead of accumulating outstanding requests for a user.
To get this fix, install one of the following updates:
-
For Skype for Business Server 2019, install the December 2019 cumulative update 7.0.2046.151 for Skype for Business Server 2019, Core Components and the December 2019 cumulative update 7.0.2046.151 for Skype for Business Server 2019 and Unified Communications Managed API 5.0 Runtime.
-
For Skype for Business Server 2015, install the July 2019 cumulative update 6.0.9319.559 for Skype for Business Server 2015, Core Components and the July 2019 cumulative update 6.0.9319.559 for Skype for Business Server 2015 and Unified Communications Managed API 5.0 Runtime.
If this issue continues to occur after you apply the update, we encourage you to contact Microsoft support, and examine the output of Test-CsExStorageConnectivity synthetic transition and Debug-CsStorageServiceFailures synthetic transition for further troubleshooting on this issue.
Workaround
To work around this issue, you can restart the Front-End servers or reset the Internet Information Services (IIS).
