MarqTastic's Posts

Thanks mpryor! Updating the client to 3.5.2 helped. No more error prompts and much better connectivity experience for the end users. In case I missed it, was a direct root cause to this error ever found/documented?

We're currently running client 3.5.0 on Windows 7 & 8.1 devices (HP Laptops & Surface Pro 3's, respectively) and in some cases are seeing this error. The unfortunate circumstance, is that we haven't been able to replicate the issue because we don't know the specific root cause. It happens seemingly random, across OS versions. Most of the hardware and images in our environment are fairly consistent, but I've also seen it affect some of our external engineers' machines as well. Has there been any more progress made on this issue?