K1000 Unhandled Exception when users comment, or create new ticket with emoji characters. Any workarounds until this gets fixed?

If users add any emoji character during creating a ticket, or simply replying to a comment, it causes the web view for that ticket to crash. We've lost at least a dozen tickets this way when people add smiley faces and the like to their comments or tickets, and it forces us to delete the ticket which is against our policy, and doesn't actually remove the character from the db. Is there any way to tell KACE to strip out encodings when users email it? Seems like this would be a basic feature if it's that easy to accidentally do.

Any advice or information would be helpful as this is a very frustrating issue for us.

0 Comments   [ + ] Show comments

Answers (1)

Posted by: jknox 5 years ago
Red Belt
The short answer is that there isn't a fix at this time and unless you can stop your mail server from sending emojis to the K1000, you will have to advise your users not to use emojis for now.

Support has a way to remove the emojis, but that is after the fact and is just a temporary solution as emojis will continue to be an issue until it is fixed in a later release.

  • Yeah I figured, thanks anyway. It's very frustrating to be working on a ticket and a user replies "Yes, thanks :)" and it's game over for that ticket. There should be a way to strip ASCII encoding in the system. - isudothings 5 years ago
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ