a single user cannot create Skype for Business meeting via outlook or "meet now"

Question

We are using Lync 2010 (yea, we know) back end services with Skype for Business 2016 client (full, office 2016 is installed) on Windows 10 workstations in an VDI environment. We have 2 sites, with 1 Enterprise Edition server at each. We also have a Director and Monitoring/archiving server at the main site. Both Lync 2010 & Exchange 2016 are on-premise. All of our user's main email addresses are not the same as their SIP address. However, one of the aliased email address is the same as the SIP.

We have a single user (out of 20,000 users) who can't create a meeting. Not with the Outlook plug-in, not with "meet now". We have tried resetting his SIP profile, rebuilding his Outlook profile, rebuilding his entire user profile (short of removing him from the domain), removed his SIP and recreated it 20 hours later, even tried moving him to the 2nd site but nothing changed.

This user can logon Skype, can have 1-1 IMs and even join meetings without issue. He just can't create his own meetings at all.

In tracing, we are seeing some 409 Conflict errors on his contact card. We also see a 403 Forbidden error, referencing ms-diagnostics 4172 "no cert found for the user". However, the user has valid certs (from the domain AND the communications server) in their store. The 403 error message came from the Director server. Certificates in the domain are NOT AD integrated.

The only other error message we could find was in the user's event log:
Source: Microsoft-Windows-CertificateServiceClient-CredentialRoaming
Event ID: 1002
Description: Certificate services client: Credential Roaming failed to read from teh local store. Error code 14 (not enough storage is available to complete this operation)

Have found several articles that mention this error, or the inability to create a meeting but none of them solved our issue.

Ideas (short of upgrading to Skype, not a option right now)? I'm running out of ideas :(

Mike

Answer 1

@Mike w ,

Does this issue persist all the time? Or what changes does this affected user do before this issue happened?

Does this user try to use a totally different machine?

It recommends you check if there is any different policy between this affected user and other users.

---

If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

@Sharon Zhao-MSFT
Sorry for the delay in responding.
Yes, this user (since July) has not been able to create a "meet now" or meeting in outlook.
This user is using our eVDI (virtual desktops, currently over 5000 VMs) to access the network, essentially receiving a "new" computer every day. Even if he did manage to get the exact same VM, it is configured to restart when the user logs off and start with a "master image". For SIP, almost all the users have identical client policies. We have a "max contacts" policy that is limited to a handful of people, but everyone else gets <automatic> across the board, PC-to-PC. We have tried resetting his profile (user, outlook AND sip) and this didn't change the issue.
He's not a "new user". This whole thing started back in July because he couldn't create a Skype meeting in Outlook. The initial issue was the icon disappeared from the ribbon. Once it was re-enabled, the user still couldn't create a meeting in Outlook. Received an error message: "Create Skype Meeting failed. Please make sure that Skype for Business is running and signed-in and try again". During troubleshooting, they discovered that using the "meet now" also didn't work. It just went through several Tier 1-2 folks before reaching me. Looking through the Trace files with Snooper, I found the errors above.
Major recent changes are migration to Exchange 2016 and migration to eVDI. Excluded patching as it would most likely show for more than 1 user.. as would the migration to Exchange or eVDI.

Answer 3

We had this problem, and it turns out that the people affected were the company secretaries.
There seems to be a server side setting that limits the number of meetings you can send out is limited to 1000.
Most people don't hit that, but this particular group send out lots of meeting invites and they'd hit 1000.

I can't find anything in Microsoft's tech notes on this at all.

I'm sure this one user issue is now resolved (the case if from a year ago) but if anyone else has it - ask whether the users affected send out lots of invites. If so, they could be hitting this limit.
It can be changed on the server end to a higher limit. I'd imagine Microsoft set it because 1000 seems such a lot of meetings and they never expected it to be breached.