Weird Unicode error in remedy when querying AD via the LDAP and a vendor form
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 those accounts that it happens, it happens every time for those accounts. Thanks, Gary Opela, Jr. Sr. Remedy Engineer Avaya Phone Admin RSP Cert, Sec+ 405 739 7006 x30043 ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: Where the Answers Are
Re: Weird Unicode error in remedy when querying AD via the LDAP and a vendor form
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 Technical Support Specialist State of North Carolina Office of Information Technology Services Service Delivery Division ITSM ITAM Services Office: 919-754-6543 ITS Service Desk: 919-754-6000 jennifer.me...@its.nc.govmailto:jennifer.me...@its.nc.gov http://its.state.nc.ushttp://its.state.nc.us/ E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties only by an authorized State Official. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Opela, Gary L CTR USAF AFMC 72 CS/SCBAH Sent: Monday, August 24, 2009 11:48 AM To: arslist@ARSLIST.ORG Subject: Weird Unicode error in remedy when querying AD via the LDAP and a vendor form 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 those accounts that it happens, it happens every time for those accounts. Thanks, Gary Opela, Jr. Sr. Remedy Engineer Avaya Phone Admin RSP Cert, Sec+ 405 739 7006 x30043 _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: Where the Answers Are
Re: Weird Unicode error in remedy when querying AD via the LDAP and a vendor form
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 same error. Thanks, Gary Opela, Jr. Sr. Remedy Engineer Avaya Phone Admin RSP Cert, Sec+ 405 739 7006 x30043 -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Meyer, Jennifer L Sent: Monday, August 24, 2009 11:00 AM To: arslist@ARSLIST.ORG Subject: Re: Weird Unicode error in remedy when querying AD via the LDAP and a vendor form ** 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 Technical Support Specialist State of North Carolina Office of Information Technology Services Service Delivery Division ITSM ITAM Services Office: 919-754-6543 ITS Service Desk: 919-754-6000 jennifer.me...@its.nc.gov http://its.state.nc.us http://its.state.nc.us/ E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties only by an authorized State Official. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Opela, Gary L CTR USAF AFMC 72 CS/SCBAH Sent: Monday, August 24, 2009 11:48 AM To: arslist@ARSLIST.ORG Subject: Weird Unicode error in remedy when querying AD via the LDAP and a vendor form 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 those accounts that it happens, it happens every time for those accounts. Thanks, Gary Opela, Jr. Sr. Remedy Engineer Avaya Phone Admin RSP Cert, Sec+ 405 739 7006 x30043 _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: Where the Answers Are__Platinum Sponsor: rmisoluti...@verizon.net ARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: Where the Answers Are
Re: Weird Unicode error in remedy when querying AD via the LDAP and a vendor form
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 with any (e.g., all, most, some) record, or just a specific one? What kind of field is it querying in AD? Lyle From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Meyer, Jennifer L Sent: Monday, August 24, 2009 10:00 AM To: arslist@ARSLIST.ORG Subject: Re: Weird Unicode error in remedy when querying AD via the LDAP and a vendor form ** 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 Technical Support Specialist State of North Carolina Office of Information Technology Services Service Delivery Division ITSM ITAM Services Office: 919-754-6543 ITS Service Desk: 919-754-6000 jennifer.me...@its.nc.govmailto:jennifer.me...@its.nc.gov http://its.state.nc.ushttp://its.state.nc.us/ E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties only by an authorized State Official. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Opela, Gary L CTR USAF AFMC 72 CS/SCBAH Sent: Monday, August 24, 2009 11:48 AM To: arslist@ARSLIST.ORG Subject: Weird Unicode error in remedy when querying AD via the LDAP and a vendor form 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 those accounts that it happens, it happens every time for those accounts. Thanks, Gary Opela, Jr. Sr. Remedy Engineer Avaya Phone Admin RSP Cert, Sec+ 405 739 7006 x30043 _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: Where the Answers Are__Platinum Sponsor: rmisoluti...@verizon.net ARSlist: Where the Answers Are_ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: Where the Answers Are
Re: Weird Unicode error in remedy when querying AD via the LDAP and a vendor form
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. Take a network dump of the ldap communication, examine all the data sent back to remedy, see if anything being sent exceeds the limits that Remedy supports (email address, login name, password, group list, notification method, etc.). If this is the case, the only recourse you really have is to upgrade the plugin, play with the available config parameters to avoid the data causing the issue, or write your own ldap area plugin. The libumem slab allocator on Solaris makes it easy to identify these types of memory issues... Not sure what options, if any, are available on Windows. Maybe someone can enlighten me. Axton Grams The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. On Mon, Aug 24, 2009 at 11:38 AM, Lyle Taylor tayl...@ldschurch.org wrote: ** 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 with any (e.g., all, most, some) record, or just a specific one? What kind of field is it querying in AD? Lyle *From:* Action Request System discussion list(ARSList) [mailto: arsl...@arslist.org] *On Behalf Of *Meyer, Jennifer L *Sent:* Monday, August 24, 2009 10:00 AM *To:* arslist@ARSLIST.ORG *Subject:* Re: Weird Unicode error in remedy when querying AD via the LDAP and a vendor form ** 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 Technical Support Specialist State of North Carolina Office of Information Technology Services Service Delivery Division ITSM ITAM Services Office: 919-754-6543 ITS Service Desk: 919-754-6000 jennifer.me...@its.nc.gov http://its.state.nc.us E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties only by an authorized State Official. -- *From:* Action Request System discussion list(ARSList) [mailto: arsl...@arslist.org] *On Behalf Of *Opela, Gary L CTR USAF AFMC 72 CS/SCBAH *Sent:* Monday, August 24, 2009 11:48 AM *To:* arslist@ARSLIST.ORG *Subject:* Weird Unicode error in remedy when querying AD via the LDAP and a vendor form 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 those accounts that it happens, it happens every time for those accounts. Thanks, Gary Opela, Jr. Sr. Remedy Engineer Avaya Phone Admin RSP Cert, Sec+ 405 739 7006 x30043 _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: Where the Answers Are__Platinum Sponsor: rmisoluti...@verizon.net ARSlist: Where the Answers Are_ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: Where the Answers Are
Re: Weird Unicode error in remedy when querying AD via the LDAP and a vendor form
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: arslist@ARSLIST.ORG Subject: Re: Weird Unicode error in remedy when querying AD via the LDAP and a vendor form ** 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. Take a network dump of the ldap communication, examine all the data sent back to remedy, see if anything being sent exceeds the limits that Remedy supports (email address, login name, password, group list, notification method, etc.). If this is the case, the only recourse you really have is to upgrade the plugin, play with the available config parameters to avoid the data causing the issue, or write your own ldap area plugin. The libumem slab allocator on Solaris makes it easy to identify these types of memory issues... Not sure what options, if any, are available on Windows. Maybe someone can enlighten me. Axton Grams The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. On Mon, Aug 24, 2009 at 11:38 AM, Lyle Taylor tayl...@ldschurch.orgmailto:tayl...@ldschurch.org wrote: ** 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 with any (e.g., all, most, some) record, or just a specific one? What kind of field is it querying in AD? Lyle From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of Meyer, Jennifer L Sent: Monday, August 24, 2009 10:00 AM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Re: Weird Unicode error in remedy when querying AD via the LDAP and a vendor form ** 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 Technical Support Specialist State of North Carolina Office of Information Technology Services Service Delivery Division ITSM ITAM Services Office: 919-754-6543 ITS Service Desk: 919-754-6000 jennifer.me...@its.nc.govmailto:jennifer.me...@its.nc.gov http://its.state.nc.ushttp://its.state.nc.us/ E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties only by an authorized State Official. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of Opela, Gary L CTR USAF AFMC 72 CS/SCBAH Sent: Monday, August 24, 2009 11:48 AM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Weird Unicode error in remedy when querying AD via the LDAP and a vendor form 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 those accounts that it happens, it happens every time for those accounts. Thanks, Gary Opela, Jr. Sr. Remedy Engineer Avaya Phone Admin RSP Cert, Sec+ 405 739 7006 x30043 _Platinum Sponsor: rmisoluti...@verizon.netmailto:rmisoluti...@verizon.net ARSlist: Where the Answers Are__Platinum Sponsor: rmisoluti...@verizon.netmailto:rmisoluti...@verizon.net ARSlist: Where the Answers Are_ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. _Platinum Sponsor: rmisoluti...@verizon.netmailto:rmisoluti...@verizon.net ARSlist: Where the Answers Are_ _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access
