Forum Discussion
Welcome everyone to the Skype for Business Server 2019 Preview Forum!
I just want to welcome everyone who has read the blog - SfB Server 2019 preview is ready for you to try. Be sure to post ALL your questions, comments, and feedback here.
64 Replies
Paul - I am experiencing the certificate issue in this old thread, even with the CU from July in my environment. Do you have any updates on when this might be fixed? 0xC3E93C0D SIP_E_STACK_TRANSPORT_CERT_NOT_FOUND
Thanks!
js
jsskype Paul Cannon Did you get any replies to this? I'm seeing it on several Skype for Business deployments. It seems to coincide with the auto renewal of the MS-Organization-P2P-Access certificates; in the Security log I can see the crypto store was accessed with a mention of the ID of one of the P2P certs at the same second that the SfB services stop.
- Hi,
I have not received any update on this, but it seems to not be occuring right now, or very sporadically, that we stopped checking if this was the issue. The fact is there are some issues still need to be worked out by the Product team, but let's hope with each update it gets better and better.
I keep reading in the forums that there is a known bug in Skype for Business 2019 on-premise.
We are unable to send messages to public Skype users by using their registered email address. For example, we are attempting to send an IM to a public Skype user with the email address of (a*****@gmail.com) and are receiving a message "The action couldn't be completed. Please try again later".
I have followed all of the directions listed on https://docs.microsoft.com/en-us/skypeforbusiness/deploy/deploy-skype-connectivity?toc=/SkypeForBusiness/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json#enabling-federation-and-public-im-connectivity-pic
Yet we still can not use this feature. Is this error part of the known bug that is expected to be addressed in the Skype for Business 2019 CU?
We're aware of this issue and investigations are in progress. Thanks.
Oh and one more, that just recently ocurred (maybe cause of Windows Updates for Windows Server 2019?), we cannot share PowerPoint presentations when homed on Skype for Business Server 2019.
It is working on Skype for Business Server 2015 with same OOS servers (I even updated OOS servers to latest version and Skype 2015 nor Sharepoint 2013/2016 have no issues with it).
But when trying to share in Skype 2019 it gets uploaded to the server but client is constantly showing Loading… or sometimes shows cannot connect to presentation server.
It worked before, but maybe after some Windows Server 2019 update it stopped, dunno. Anything you know about?:)
Paul CannonHi, we also deployed Skype for Business Server 2019 but run into two strange problems, we don't know what they are related to, cause we see no network issues with the VMs and SQL back-end.
1. Skype 2019 pool in another region sometimes once a day, sometimes 2-3 times a week has problems with communication with back-end in primary site (where the monitoring DB sits), which causes Front End Service to restart sometimes:
1a. Failed to execute a stored procedure on the back-end.Component: QoE Adaptor
Stored Procedure: HeartbeatFrontEnd
Error: System.Data.SqlClient.SqlException (0x80131904): A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.) ---> System.ComponentModel.Win32Exception (0x80004005): The semaphore timeout period has expired1b. Then it is immediately followed by this error:A Data Collection QoE adaptor has failed to connect to or lost a connection to the back-end. It will continue to try and reconnect to the back-end.Adaptor: QoE Adaptor
Connection String: Data Source=primarysiteSQL-BackEnd.domain.com;Initial Catalog=QoEMetrics;Integrated Security=True;Enlist=False;Pooling=True;Max Pool Size=5;Connect Timeout=60;Application Name=Microsoft.Rtc.Management.Core
Dependent Machine: primarysiteSQL-BackEnd.domain.com
Cause: This typically occurs when the back-end is down or not reachable.
Resolution:
Verify the back-end is up and this Skype for Business Server has connectivity to it. If the problem persists, notify your organization's support team with the relevant details.1c. and then we see:An attempt by Storage Service to replicate data via the fabric from the primary failedFabric Service Id=F0DF488FE78C536EB6DC68BC6B5E6E81. Exception: #CTX#{ctx:{traceId:258301240, activityId:"f2051b0b-d060-4668-a4bd-2de2ad5b9d5b"}}#CTX#System.ApplicationException: Read denied for [fabric:/lync/storage/F0DF488FE78C536EB6DC68BC6B5E6E81] - Access Status [ReconfigurationPending] ---> System.AccessViolationException: PartitionAccessStatus1d. and then:Failed to commit session data into the local Storage Service database.Error:
System.OperationCanceledException: Received queue operation request for fabric service id [F0DF488FE78C536EB6DC68BC6B5E6E81], but that group is not owned by this FE... requested operation unable to continue on this host. ---> Microsoft.Rtc.Internal.Storage.StorageApiParamValidationException: secondsiteFE1.domain.com1e. and finally even problem with connecting to sql back end in same site:Failed to connect to back-end database. Skype for Business Server will continuously attempt to reconnect to the back-end. While this condition persists, incoming messages will receive error responses.Back-end Database: rtcab Connection string of:
driver={SQL Server Native Client 11.0};Trusted_Connection=yes;AutoTranslate=no;server=secondsiteSQL-BackEnd.domain.com.domain.com;database=rtcab;
Cause: Possible issues with back-end database.
Resolution:
Ensure the back-end is functioning correctly.There are few other errors thrown in the event viewer after which it suddenly starts working2. Problem with uploading specifically QoE metrics to from second site to primary site SQL (where monitoring DB sits):The Quality-Metric server cannot be contacted. The Quality metric reports are not sent to the server.QoE Agent:
QoE GRUU: sip:secondsiteFEpool.domain.com@domain.com;gruu;opaque=srvr:QoS:nH-yhC2-dFWNhnvaPm7qGgAA
Exception: Microsoft.Rtc.Internal.Qoe.QoeSendException:This operation has timed out. ---> Microsoft.Rtc.Signaling.OperationTimeoutException:This operation has timed out.Is this something that you are aware of and will be fixed in new CU?Krzysztof Sienkiewicz , We tried to reproduce the issue you met yesterday, and ever things worked well. For investigate completely ASAP, we need further information, Cloud you help me to resolve the following confuses:
1.One of Strange problems that you met, Dose it look like this scenario?(I have 2 site New York and Washington, and they own a single one monitoring DB in New York, but now Washington's site Front End pools can not work .)if so, could you please tell me how other Server roles you have deployed with? or you can tell me what you did before the error occurred (such as restart primarysiteSQLBackEnd.domain.com and so on).
2.The other problem is operation has timed out, you mean it can not
upload specifically QoE metrics (which is from second site to primary site SQL) successfully, thus did you configure the firewall or Check the connection that all servers ping to DC?
Thank
Let me provide you with our setup:
Like with Skype for Business Server 2015 we deployed pools in two sites (Denmark (pri) and U.S. (sec))
Denmark pool:
3 Front Ends colocated with Mediation (prisiteFE01.domain.com, prisiteFE02..., prisiteFE03...)
1 SQL Back-End (with CMS DB, pool DBs and Monitoring DB) (prisiteSQLBackEnd.domain.com)
U.S. pool:
3 Front Ends colocated with Mediation (secsiteFE01.domain.com, secsiteFE02..., secsiteFE03...)
1 SQL Back-End (with pool DBs only) (secsiteSQLBackEnd.domain.com)
so US pool sends monitoring data to Denmark pool.
Like mentioned this is the same setup like we had in Skype 2015, we opened same ports, it's configured same and of course part of same topology.
I've been digging into problem nr 2 for few hours yesterday and it seems this is not ocurring constantly, only once in a while when a call completes in US it tries sending QoE metrics and times out and (as I read "by design") does not retry this ever again, jut goes to the next job. Sometimes it times out sometimes it does not. What is the timeout time exactly, do you know?
Firewall (Windows and Cisco) is configured same like it was for Skype 2015 so should be no issues there.
I managed to capture CLS logs when timeout happened and yeah, it shows that it sends the metrics (as it is SIP, it sends through the pool) but does not receive answer 202 OK, in all traffic captured when this one timeout occurs, this is the only SERVICE Out message that does not receive return message 202 OK, so it logs timeout.
I have NetMon logs, but will have to show it to a network guy to really understand it. I only see that one front end in US pool sends the metrics to another front end in the US pool (why?), maybe this other front end is then responsible for sending the metrics to Monitoring DB in pri site?
All servers ping DCs:)
In regards to issue nr1, I am still trying to reproduce, like I said it works sometimes for a few days then suddenly has a problem for 2-3 minutes, then back to normal, but nothing logged in SCOM from today yet.
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?
- Hi 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
- Will there be a certification coming out for Skype for Business Server 2019 similar to what was offered for Lync and Skype for Business Server 2015?
