I saw this yesterday from a reporting user, but after refreshing the account connection, we could not reproduce it.
I did not delve into the reporting user's jive-for-office logs to examine the error, but it might be a good place to start if you can't get rid of it.
(go to Help > Report Issue, then instead of sending the mail, examine the log files) ;)
Hi Diana and Mike,
After reviewing through the office logs attached to the case you submitted, the following type of error was listed:
Failed to deserialize data to json string (Unexpected character encountered while parsing value: <. Path '', line 0, position 0.)
which is linked to a currently open issue being tracked as JENSO-7852.
Mike, if you too are seeing this behavior reported by users in your instance and would like to confirm and/or track the issue, please submit a case in your customer group ( MyJive Secret Support Group Administration FAQ ) and a member of our support team can assist with investigating the issue.