SOTI Pulse Logo

Not allowed to access MXMF, CSP Manager is not ready!!! net.soti.mobicontrol.androidwork: please try again

DM
D Malipatil
Daimler AG

Hello SOTI,

While I am excuting the XML file I am getting the subject error, where other XML have no issue with it.

Below is the Error I saw in Android Debug logs:

05-30 13:56:48.809 10223  2878  4742 E soti    : script-executor|E|DO|[net.soti.mobicontrol.xmlstage.b] Mxconfig falló: /sdcard/Download/10.2EnableProglovKeyboard.xml|net.soti.mobicontrol.device.m5: Process xml failed 
05-30 13:56:48.809 10223  2878  4742 E soti    :     at net.soti.mobicontrol.xmlstage.h.m(SourceFile:47)
05-30 13:56:48.809 10223  2878  4742 E soti    :     at net.soti.mobicontrol.xmlstage.b.execute(SourceFile:47)
05-30 13:56:48.809 10223  2878  4742 E soti    :     at net.soti.mobicontrol.script.r0.n(SourceFile:17)
05-30 13:56:48.809 10223  2878  4742 E soti    :     at net.soti.mobicontrol.script.r0.l(SourceFile:94)
05-30 13:56:48.809 10223  2878  4742 E soti    :     at net.soti.mobicontrol.script.r0.r(SourceFile:5)
05-30 13:56:48.809 10223  2878  4742 E soti    :     at net.soti.mobicontrol.script.r0.j(Unknown Source:0)
05-30 13:56:48.809 10223  2878  4742 E soti    :     at net.soti.mobicontrol.script.q0.run(Unknown Source:8)
05-30 13:56:48.809 10223  2878  4742 E soti    :     at net.soti.mobicontrol.script.r0.s(SourceFile:5)
05-30 13:56:48.809 10223  2878  4742 E soti    :     at net.soti.mobicontrol.script.r0.i(Unknown Source:0)
05-30 13:56:48.809 10223  2878  4742 E soti    :     at net.soti.mobicontrol.script.o0.run(Unknown Source:4)
05-30 13:56:48.809 10223  2878  4742 E soti    :     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
05-30 13:56:48.809 10223  2878  4742 E soti    :     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
05-30 13:56:48.809 10223  2878  4742 E soti    :     at java.lang.Thread.run(Thread.java:919)
05-30 13:56:48.809 10223  2878  4742 E soti    : Caused by: org.xmlpull.v1.XmlPullParserException: markup not allowed inside attribute value - illegal <  (position: START_TAG seen ...rameworkService: received request/configuration information is: \\ufeff<... @1:138) 
05-30 13:56:48.809 10223  2878  4742 E soti    :     at org.xmlpull.mxp1.MXParser.parseAttribute(SourceFile:863)
05-30 13:56:48.809 10223  2878  4742 E soti    :     at org.xmlpull.mxp1.MXParser.parseStartTag(SourceFile:617)
05-30 13:56:48.809 10223  2878  4742 E soti    :     at org.xmlpull.mxp1.MXParser.nextImpl(SourceFile:288)
05-30 13:56:48.809 10223  2878  4742 E soti    :     at org.xmlpull.mxp1.MXParser.next(SourceFile:4)
05-30 13:56:48.809 10223  2878  4742 E soti    :     at net.soti.mobicontrol.xmlstage.h.o(SourceFile:35)
05-30 13:56:48.809 10223  2878  4742 E soti    :     at net.soti.mobicontrol.xmlstage.h.n(SourceFile:10)
05-30 13:56:48.809 10223  2878  4742 E soti    :     at net.soti.mobicontrol.xmlstage.h.m(SourceFile:5)
05-30 13:56:48.809 10223  2878  4742 E soti    :     ... 12 more
05-30 13:56:48.809 10223  2878  4742 E soti    : |

a year ago
SOTI MobiControl
ANSWERS
RS
Rafael Schäfer
a year ago

Did you check that there's really no issue in the XML being used (also required MX version is available)?

looks for me like an issue in the xml itself> " Caused by: org.xmlpull.v1.XmlPullParserException: markup not allowed inside attribute value - illegal <  (position: START_TAG seen ...rameworkService: received request/configuration information is: \\ufeff<... @1:138) " 

DM
D Malipatil
a year ago

its a simple xml file which I exported from the Zebra StageNow app , its just to enable the application and set the defualt keyboard 

<wap-provisioningdoc>
  </characteristic>
  <characteristic version="9.3" type="AppMgr">
    <parm name="Action" value="EnableApplication" />
    <parm name="Package" value="de.proglove.connect" />
  </characteristic>
  <characteristic version="10.1" type="UiMgr">
    <parm name="InputMethodAction" value="1" />
    <characteristic type="InputMethodDetails">
      <parm name="InputMethodOption" value="4" />
      <parm name="InputMethodPackageName" value="de.proglove.connect" />
      <parm name="InputMethodClassName" value="de.proglove.keyboard.LatinIME" />
    </characteristic>
  </characteristic>
</wap-provisioningdoc>

RS
Rafael Schäfer
a year ago

But it doesn't look correct for me (i may be wrong):

Line 2:  </characteristic> with no opening <characteristic ...> before
And later a characteristic inside a characteristic one also sounds strange for me. < seem to be fine like that

Let me check that on my end.

Also your device supports MX 10.1 and higher?

RS
Rafael Schäfer
a year ago

I get this:

<wap-provisioningdoc>
  <characteristic version="9.3" type="AppMgr">
    <parm name="Action" value="EnableApplication" />
    <parm name="Package" value="de.proglove.connect" />
  </characteristic>
  <characteristic version="10.1" type="UiMgr">
    <parm name="InputMethodAction" value="1" />
    <characteristic type="InputMethodDetails">
      <parm name="InputMethodOption" value="4" />
      <parm name="InputMethodPackageName" value="de.proglove.connect" />
      <parm name="InputMethodClassName" value="de.proglove.keyboard.LatinIME" />
    </characteristic>
  </characteristic>
</wap-provisioningdoc>

So, maybe only line 2 from yours needs to be removed.

DM
D Malipatil
a year ago

Rafel, still same error

DM
D Malipatil
a year ago

The code is autogenerated from the StageNow tool, we not made any chages after the export.

RS
Rafael Schäfer
a year ago

Mine as well (SN 5.10) and your line 2 is missing in mine and i wont expect it to be there as well.

MD
Matt Dermody Diamond Contributor
a year ago

Can you provide the following:

  • Device Model
  • Device BSP version
  • MC version
  • Agent Version

I am suspecting you need an Agent Upgrade. If an MX XML is attempted to be processed by the SOTI Agent too soon after a device is booted up the MX can fail to apply if the MX service has not fully initialized. This also typically results in the MX layer getting in a strange state where MX XML will continue to fail until the device is rebooted. There are newer Agent versions that insert a delay in the Agent start up procedure to wait for the MX layer to fully initialize before proceeding with any MX based actions.

Note you can also end up in this state if you have other applications that leverage MX such as the Zebra Enterprise Browser which uses it to check it's licensing status that are launched too quickly on a device restart. Older devices like the WT6000 seem to be more impacted by this issue. Once the MX layer gets into this state you typically have to restart the device before you can try again.  

DM
D Malipatil
a year ago

Hello Matt,

Here the details

Device Make & Model: Zebra TC52,TC52X

MX Version : 10.5.1.1

BSP & LG(OEM): 10-16-10.00-QG-U142-STD-HEL-04

MC: 15.6

Agent Version:15.4.2 Build 1025

About device reboot so its failed, no I tried it just sent a xml file and executed with mxconfig /sdcard/Download/<Filename.xml>

 
 
A
AKMOD@SOTI
a year ago

Hi D Malipatil,

I believe this need thorough investigation so I would highly recommended that you log a case so that we can delve deeper into the matter.

We request you to please raise a support case at log a case so that our agent can work on your query as quickly as possible .

Similar Discussions