Forum Discussion
sinamotamedi_15
Jul 08, 2015Nimbostratus
Yeah that's not a bad thing to try. What's odd, however, is that I replaced that config.f5c file with a copy from a user that wasn't having issues and then I modified the username attribute in the config file to reflect the correct username and the corrupted message still appeared.
Sounds like we're in the same exact situation. We have about 4-5 IT folks testing it and unfortunately, two of them have the problem. We're about a week from going live and were hoping to use the client as a way around the incompatibilities with Chrome and potentially other browsers down the road.