Posts
I had a customer a few weeks ago that could not escalate to a conference. They were having a P2P call with someone, tried to add a third user to the conversation and received an error each time. The problem had been going on for about a week and they asked if I could take a look and see what was going on. I'll admit, I've heard of this issue before, but I had not seen it yet. I started parsing the Lync Event Log on the FE server and noticed a lot of the following SQL Errors: The 'General' tab included more data, but here is the most pertinent thing we need to focus on: The transaction log for database 'rtcxds' is full due to 'LOG_BACKUP'. I'm not a SQL expert, but shouldn't there be a way to increase or decrease the size of the logs? Well, there is, but it turned out to be more convuluted than I had hoped. I logged onto the BE SQL server where the rtcxds database is located. I right clicked on the database, went to 'Propert...
Well, this is odd. I was helping a customer in an Office 365 Hybrid Deployment. They decided to go with S4B on prem and Exchange in the cloud. The customer tested scheduling a S4B Meeting and noticed the following: ( Dial-In Conferencing Numbers are blacked out, but trust me, they're the same. ;) ) Why is this a thing? I wasn't for certain, however, my best guess was this was either being caused by the O365 Pro Plus Client or Exchange. Time to troubleshoot! I checked S4B Technet Forums and found a post from another user regarding this same issue. I followed the advice in the post above and had the customer schedule a meeting through OWA rather than through their client. Low and behold, scheduling the meeting through OWA listed the dial-in conferencing number once. Alright, now I'm getting somewhere, but what's going on with the client? The customer was running the most recent O365 First Release Deferred Channel Version (v 1701 as of June 2017)...
