Forum Discussion
Welcome everyone to the Skype for Business Server 2019 Preview Forum!
Krzysztof Sienkiewicz were you able to determine which certificate serial number it was referring to at all? The error contains "The serial number is attached for reference" but no values within the details tab match any serial numbers for any certs I can see.
Rohit_Gupta_25 We had AlwaysOn logging enabled - can I share some CLS logs and corresponding Windows Event Logs for this issue with you at all?
I know what you mean. The thing is you (as I did) looked at certificate hashes, serial number is a different field and also the serial number in the event log is reversed in pairs from the serial number you see in the certificate details. Meaning: A678F5 in the cert would be F578A6 in the event log
Unfortunately we'd already moved our environment over by the time this issue came up, so don't have the luxury of reverting now.
We're not using WAP 2019 so can't help on that one I'm afraid.
Yes, this is a problem, we halted moving users to Skype 2019 because of this.
Also, like I mentioned earlier there's also an issue with WAP 2019, are you using Web Application Proxy server from Microsoft (along with AD FS) and noticed the issue with meet url/s when WAP 2019 is used?
It seems 2019 family product needs some fixes.
Amazing, thank you for that Krzysztof Sienkiewicz! Not the most intuitive of error formats!
I was able to confirm that the certificate referenced was indeed my pool certificate containing all SANs, as I'd suspected from the reference to 0.0.0.0:5061 in the event logs.
Like you, as soon as I started the front-end service again I was able to use the same certificate without any issues - it just seems to be the momentary disconnection from the certificate store rather than a problem with the certificate itself that causes the issue.
Would be good to get some feedback from Microsoft on this one as this is service affecting for us - again, the offer of CLS logs and event logs is there.