July 17, 20214 yr Community Expert That is a 6.8.3 issue due to a change at the remote end. It is fixed in 6.9.2 (although if for some reason you cannot upgrade to that release there is a workaround posted in the forums).
July 17, 20214 yr The proper solution is the update, if necessary the workaround can be found there :
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.