You have a normal conversation in Skype for Business via Instant Messaging. The next day, you need to check the status of a task. You recall you mentioned this task in yesterday’s conversation. Better go check it in Conversation History.

Outlook is already open. You click the Conversation History folder and…wait, where’s the conversation? The last one you see is dated 2 weeks ago!

We ran up against this issue with a customer’s Skype for Business deployment. They had a server deployment, up and running since 2016. The Conversation History “delayed appearance” only started this past fall. Even more confusing, it didn’t occur for all users.

Work Conversation in Skype4B
“I KNOW I talked to Beth yesterday…”
Photo by rawpixel.com on Unsplash

The Cause: A Low Threshold for Conversation File Size

We checked all the obvious things, of course. But those were all clear. Only after testing & reviewing the Conversation History logs that did appear, followed by some MS research, did we find the cause.

Lync Server 2013 had an issue with long conversations. If a conversation’s history file ended up over 1MB in size, Lync Server could not upload the file to Exchange Server. This bug persisted into Skype for Business Server.

So if you end up having a long conversation with co-workers, plus a few images & documents shared around, your conversation grew past the server’s (tiny) 1MB limit!

The Solution: A Fix for Lync/Skype for Business Server, Then an Exchange Server Workaround

Microsoft did release a fix for this: KB3101496. It’s a security update issued November 10, 2015. Link to the update below.

This isn’t the only fix though. In fact, it might not even work for you. Not to worry…if it doesn’t, we have an alternative! The clever engineers posting on this thread determined it:
Lync 2013 Conversation History not taken from History Spooler by Outlook 2013 when bigger than 1 MB – TechNet

It’s an edit to an Exchange web.config file. Though from the thread and our own experience, we advise approaching the problem in this order:

  1. Apply the update first. Wait a few hours to determine if it took effect.
  2. If the update doesn’t work, use the following workaround.

Conversation History Bug Fix (KB3101496):

Security Update MS15-116 and MS15-123 for Lync 2013 (Skype for Business)
If your Skype for Business Server doesn’t already have this through Microsoft Update, you can download it here.

If Conversation History in Outlook doesn’t start updating within a few hours (happened for us after Hour 3), then try the web.config workaround.

Exchange Server Web.Config Workaround:

  1. Access your Exchange Server. Make sure you have write permissions.
  2. Navigate to the Exchange installation directory, e.g. C:\Program Files\Microsoft\Exchange Server.
  3. Open the version folder.
  4. Open the ClientAccess folder.
  5. Open the exchweb folder.
  6. Open the EWS folder.
  7. Edit the web.config file found here.
  8. Within the <appSettings> node, add the following line:
    <add key=”XmlMaxBytesPerRead” value=”1000000″ />
  9. Restart your IIS server.

Again, wait a few hours. The conversations should start trickling into Conversation History, in groups of 10 or so. You may need to restart Outlook & the Skype for Business client a few times to get everything.

Sometimes Conversation Logs Delay Their Appearance. Call Them Out on Stage with These Fixes!

This is an issue which can fly under the radar. Our customer saw no error messages, and had no Outlook crashes related to it. They only noticed when someone did exactly what I portrayed earlier—tried to check a previous Skype4B conversation via their Outlook Conversation History.

Take a second to review your Outlook Conversation History. Hopefully this bug doesn’t affect you…but it doesn’t hurt to check!

Have you experienced a Conversation History “delayed appearance” in Outlook, or something similar?

 

What to Do When Skype4B Conversations Take Weeks to Appear in Outlook
Facebooktwittergoogle_plusredditlinkedinmail

2 thoughts on “What to Do When Skype4B Conversations Take Weeks to Appear in Outlook

  • January 12, 2018 at 10:02 am
    Permalink

    Clever engineers? Thank you 🙂

    Reply
    • January 12, 2018 at 10:06 am
      Permalink

      Credit where it’s due, Fabien! Your efforts saved our team some time.

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *