ARERR [9062] Error encountered during string conversion from Unicode : string
;yêÇÕáB¬b Ûã=·Ø
Remedy 6.3 (no patch)
Windows/Sql Server
Has anyone seen the above error message when querying AD? Is there a fix that
doesn't involve patching?
It only happens on some accounts, but on
Does the user's name perhaps contain a character that Remedy can't read? For
example, if you have installed the English language pack, but not the Japanese
language pack, and the user has a Japanese character in his or her name, an
error of this sort might occur.
Jennifer Meyer
Remedy
Nope, standard American name (whatever that is these days). Nothing special. We
even checked all of the Unicode fields in AD to make sure there weren't any
bazaar characters in there. There was one field with a bazaar character, so we
left that field off of the vendor form, but it still had the
I don't have an answer for Gary's question, but wanted to point out that you
shouldn't need to install a foreign language pack in order to handle foreign
characters. Remedy's ability to handle foreign characters depends entirely on
it being set up for Unicode.
However, Gary, does this happen
6.3 does not support multiple localizations; back then a separate arserver
was required for each localization set, though every localization set
supported english.
This may not even be a case of Unicode data. You can get garbage like that
when applications perform illegal memory operations.
That's right - I forgot about that that was the case with 6.3 (my time with 6.3
was limited - fortunately...). Thanks for the correction, Axton.
Lyle
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Axton
Sent: Monday, August 24, 2009 3:07 PM
To:
6 matches
Mail list logo
