SOTI Pulse Logo

Error sending messag (error sending message (type=22), General Communication error)

RC
Roberto Criconia
loropianaxs

Hi everyone,

with mobicontrol and Zebra TC53 device with both Android 13 and 14, I update some display configurations (manual rotation button) trough Zebra Oem Config  14.2.0.1 using App Policy and managed configuration. Before that, this Policy was already applied to all devices. I have only modified the Display configurations parameter.

After that as of when the policy as been updated and applied, the log of each TC53 device reports the  "Error sending messag (error sending message (type=22), General Communication error)" every 9 - 10 seconds.

Please note, other zebra devices on the same network and same istance of Mobicontrol that are not involved with this policy does not reports this error.

Can everyone help me with some suggestions?

Thank you

 

2 months ago
SOTI MobiControl
ANSWERS
K
KSTMOD@SOTI
2 months ago

Hello Roberto,

Thank you for posting on SOTI Pulse.

We understand that you are encountering the error message: "Error sending message (type=22), General Communication error"
on Zebra TC53 devices running both Android 13 and 14 after updating the Display Configuration parameter through Zebra OEMConfig 14.2.0.1 using App Policy and managed configurations.

To help narrow down the root cause and better assist you, could you please clarify the following:

  1. Did this issue begin immediately after updating the Display Configuration, or were there any other changes made around the same time?
  2. Have you tried testing with a new blank policy that only includes the Display Configuration parameter to confirm if the error persists?
  3. Is this behavior reproducible on all TC53 devices running Android 14, or only on a specific subset of devices?
  4. Could you confirm the exact OEMConfig version installed on the affected devices? If possible, try updating to the latest version and let us know if the issue remains.
  5. Have you collected device logs (ADB or StageNow) while the error is occurring? These logs could help identify whether the issue is coming from OEMConfig or MobiControl.
  6. Can you verify if the affected devices are on the same network segment and confirm that DNS and connectivity tests (e.g., ping or nslookup) to the MobiControl server are successful?

In the meantime, you may also try reverting to the previous working policy to check if the issue stops, which could help isolate whether this behavior is directly related to the Display Configuration changes.

We appreciate your effort in providing these details, as they will help us investigate further and identify the best next steps.

Warm Regards,
KSTMOD

Similar Discussions