The user gets the issue attached.
Is the problem reproducible? If so, how? >>create a simple poll and publish
only for 2-3 selected individuals inside Keystone community. I don’t know if
others are affected. Document upload works fine.
Can this error be reproduced by the
affected users consistently? If so, what are the steps to do so? Is it
affecting all users, or a subset of users? Is it triggered by accepting social
group invitations, or by clicking in Spotlight search?
Was the user actually logged out? >>no wasn’t
Are they able to continue browsing the
instance after facing the error, or are they forced to log back in? >>refresh doesn’t help, can only
close the poll.
When was a time (with timezone) and the
username of a user that ran into this? >>between 3:00 and 5:30 PM CET. Instance
is not on-prem, but hosted.
If your instance is On-Prem, please also
include your sbs.out, sbs.log, and jive-httpd-access logs that cover this same
Are there any Network issues? >>not for my knowledge. Don’t use
The easiest way to test this is to use
Google Chrome. Click the Menu button > Tools > Developer Tools, Network
tab. Click the ⃠
button, which will clear the Network pane, and then reproduce the error. Are
there any 400 or 500 errors that show up? They will show up as red. Click them
to expand them, and add them to the case.
Again, testing this is easiest in Google
up? They will show up as red. Click them to expand them, and add them to the
I'm sorry to hear about the issues you've received reports on. This will likely require targeted troubleshooting and I do see a support case has been field here:
A Jive Customer Support team member will be looking into this and will provide guidance. Please continue to follow the support case for updates.