No mapping for the Unicode character exists in the target multi-byte code page

Content Authoring
1

We upgraded out BES from 9.5.5 to 9.5.8. The next day we upgraded all the relays to 9.5.8. The next day we upgraded all our clients to 9.5.8, after which, we started seeing these stream into the BESRelay.log. The two IPs shown are our two top level relays.

Mon, 12 Mar 2018 06:08:41 -0400 - /cgi-bin/bfenterprise/clientregister.exe (9652) - Uncaught exception in plugin ClientRegister with client 10.2.19.110: WindowsCharacterSetResult: Error 1113 (No mapping for the Unicode character exists in the target multi-byte code page.) in TranscodeU8ToU16
Mon, 12 Mar 2018 06:08:41 -0400 - /cgi-bin/bfenterprise/clientregister.exe (5916) - Uncaught exception in plugin ClientRegister with client 10.2.19.110: WindowsCharacterSetResult: Error 1113 (No mapping for the Unicode character exists in the target multi-byte code page.) in TranscodeU8ToU16
Mon, 12 Mar 2018 06:09:19 -0400 - /cgi-bin/bfenterprise/clientregister.exe (11116) - Uncaught exception in plugin ClientRegister with client 10.2.19.110: WindowsCharacterSetResult: Error 1113 (No mapping for the Unicode character exists in the target multi-byte code page.) in TranscodeU8ToU16
Mon, 12 Mar 2018 06:09:19 -0400 - /cgi-bin/bfenterprise/clientregister.exe (9620) - Uncaught exception in plugin ClientRegister with client 10.2.19.110: WindowsCharacterSetResult: Error 1113 (No mapping for the Unicode character exists in the target multi-byte code page.) in TranscodeU8ToU16

If I “walk” down to the Relay Log on one of the Top Level Relays, I have these; the IP being a Child Level Relay:

Tue, 13 Mar 2018 06:26:20 -0400 - /cgi-bin/bfenterprise/clientregister.exe (984) - Uncaught exception in plugin ClientRegister with client 10.20.4.172: HTTP Error 52: Server returned nothing (no headers, no data): Empty reply from server
Tue, 13 Mar 2018 06:26:21 -0400 - /cgi-bin/bfenterprise/clientregister.exe (4832) - Uncaught exception in plugin ClientRegister with client 10.20.4.172: HTTP Error 52: Server returned nothing (no headers, no data): Empty reply from server
Tue, 13 Mar 2018 06:27:07 -0400 - /cgi-bin/bfenterprise/clientregister.exe (888) - Uncaught exception in plugin ClientRegister with client 10.20.4.172: HTTP Error 52: Server returned nothing (no headers, no data): Empty reply from server

Walking that Relay Log, I have this; the IP(s) being endpoints:

Tue, 13 Mar 2018 18:27:08 +0800 - /cgi-bin/bfenterprise/clientregister.exe (16924) - Uncaught exception in plugin ClientRegister with client 10.113.130.89: HTTP Error 52: Server returned nothing (no headers, no data): Empty reply from server
Tue, 13 Mar 2018 18:29:27 +0800 - /cgi-bin/bfenterprise/clientregister.exe (26304) - Uncaught exception in plugin ClientRegister with client 10.196.135.62: HTTP Error 52: Server returned nothing (no headers, no data): Empty reply from server
Tue, 13 Mar 2018 18:29:28 +0800 - /cgi-bin/bfenterprise/clientregister.exe (4748) - Uncaught exception in plugin ClientRegister with client 10.196.135.62: HTTP Error 52: Server returned nothing (no headers, no data): Empty reply from server

The endpoint has many of these, going through the whole relay list. I’ve uninstalled BigFix and reinstalled and it does the same thing. It connects, so firewall and everything is good, it just keeps cycling through. And this is one example… Any ideas on how best to troubleshoot?

At 06:31:28 -0400 - 
   RegisterOnce: GetURL failed - General transport failure. - 'http://Relay.FQDN.com:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=9.5.8.38&Body=13690764&SequenceNumber=1001&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&MinHops=8&MaxHops=8&Root=http://bfx.arrisi.com%3a52311&AdapterInfo=00-21-86-f7-99-44_10.113.130.0%2f23_10.113.130.89_0&AdapterIpv6=00-21-86-f7-99-44%5efe80%3a%3aa8af%3a865a%3a61b0%3a20f%2f64_0' http failure code 0 - registration url - http://Relay.FQDN.com:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=9.5.8.38&Body=13690764&SequenceNumber=1001&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&MinHops=8&MaxHops=8&Root=http://bfx.arrisi.com%3a52311&AdapterInfo=00-21-86-f7-99-44_10.113.130.0%2f23_10.113.130.89_0&AdapterIpv6=00-21-86-f7-99-44%5efe80%3a%3aa8af%3a865a%3a61b0%3a20f%2f64_0
2

Did you figure this one out? I just noticed we have some of these in our relay logs as well, and was about to start troubleshooting individual clients.

3

It’s a bug and IBM has the info [APAR IJ05780]

Here’s what happened on my end. The problem client starts contacting every relay and leaving its error message in their logs. To track it down, you need to “walk” the relay log from top to bottom until you find the IP of the actual client. Then you need to downgrade that client to 9.5.5. Then the issue goes away.

Likely, if using the 9.5.8 QnA running the relevance info of client on the problem client, you’ll get an error.

2 Likes
4

Much appreciated, thanks for the information.

5

Sorry, missed this thread, but similar and maybe related to an issue that’s come up here a couple of times, including a couple of instances in my deployment.

At least two of us were able to identify acorrupt Client Setting as causing this. Mine occurred during client version upgrades as well, though I think mine were 9.5.5 -> 9.5.6, or 9.5.6 -> 9.5.7.

Easiest way to identify is to exported the client settings from the Registry (HKLM\software\wow6432node\bigfix\enterpriseclient\settings\client) and look for unprintable characters in the export. You may delete those settings alone, or delete all of the client settings values and restart the besclient.

Never found a root cause, and only had a couple instances out of 1600 Windows clients; I haven’t encountered it on RHEL yet.