SOTI Pulse Logo

MX Command Erro

Solved
PC
Paul Courtney
nokiantyres

For some of our warehouses we have to load a datawedge profile.  We transfer the db file with a file transfer policy then run a script afterwards to load it.

<wap-provisioningdoc>
  <characteristic version="10.1" type="DataWedgeMgr">
    <parm name="ConfigurationFile" value="/sdcard/download/datawedge.db" />
    <parm name="AutoImporting" value="1" />
  </characteristic>
</wap-provisioningdoc>

This works fine on all of our MC9450 devices with this configuration.

MX OEM Data Wedge
13.2.032 13-15-17.00-TG-U00-STD-NEM-04 13.0.218

Monday we started a launch in a new warehouse with new devices.  MC9450's with this configuration

MX OEM Data Wedge
13.5.0.28 13-24-08.00-TG-U00-STD-NEM-04 14.1.32

All of the SOTI configurations are identical with these devices and the existing devices. However we are getting this error when trying to run the script.

Custom log (Mxconfig failed: /sdcard/download/SOTI_RMDataWedge.xml).  I have enrolled on of the devices with the older configuration with these devices and the script works.  I can't find anything on the zebra documentation.

One other note.  There is a custom application that we install on these, Manhattan Scale Warehouse Mobile.  This app usually installs two datawedge profiles to the device.  When I check after installation, the profiles are not there.  I can go to the device and go into the datawedge app and manually load the configuration from the db file that SOTI downloaded, which is the work around we are using now.

Anyone help would be appreciated.  Thanks all.

Datawedge MX
6 months ago
SOTI MobiControl
ANSWERS
RK
Radim Kadlec
6 months ago

Hi Paul,

Sounds really weird!
I use the same approach on MC93 with DataWedge 14.0.11 and it works fine.
I would recommend checking the path you are using to download the files. It should be /sdcard/Download/ (with a capital D).

PC
Paul Courtney
6 months ago

The files download fine.  The datawedge.db and the xml file for the script.  They are the same files for all of the devices. And I can go into the Datawedge app on the device and manually load the db file without incident.

  The only difference I can see is the difference in the MX and Datawedge version.

PC
Paul Courtney
6 months ago

Update

I load this xml file to the download directory.

<wap-provisioningdoc>
  <characteristic version="13.5" type="DisplayMgr">
    <parm name="ScreenShotUsage" value="1" />
  </characteristic>
</wap-provisioningdoc>

And send this

mxconfig /sdcard/download/testMXScripts.xml 

And it works fine, so it must be something with the XML script.  I am not sure what the difference is between the mx versions or why it would kick it out.

PC
Paul Courtney
6 months ago

Another Update

This works

wap-provisioningdoc>
  <characteristic version="10.1" type="DataWedgeMgr">
    <parm name="AutoImporting" value="1" />
    <parm name="ManualConfiguration" value="1" />
  </characteristic>
</wap-provisioningdoc>

This does not

<wap-provisioningdoc>
  <characteristic version="10.1" type="DataWedgeMgr">
    <parm name="ConfigurationFile" value="/sdcard/Download/datawedge.db" />
    <parm name="AutoImporting" value="1" />
    <parm name="ManualConfiguration" value="1" />
  </characteristic>
</wap-provisioningdoc>

Must be an issue with the db file.

PC
Paul Courtney
6 months ago

And Finally.

I deleted the datawedge.db file from the Download folder and exported the profile from the Datawedge app to the download folder and then ran the script that was generating errors and it worked fine.

A few points

* The datawedge.db file that SOTI download was exported from a MC9300 last December and has been working fine in all devices.

* This file from december, when downloaded to the device can be imported by using the Datawedge app.

* This file from december generated the mxerror only when trying to load it with a script.

* The third party app from Manhattan Scale is still unable to create its DW profiles on installation.

So.  I have a solution but I still have no idea why this is happening.

PC
Paul Courtney
6 months ago

2025-05-30 19:40:30.541|script-executor|D|DO|[net.soti.mobicontrol.xmlstage.d.execute:39] (/sdcard/download/SOTI_RMDataWedge.xml) Response: <wap-provisioningdoc><characteristic-error type="DataWedgeMgr" version="10.1" desc="ERROR"><parm-error name="ConfigurationFile" value="/sdcard/download/datawedge.db" desc=" Cannot read file"/><parm name="AutoImporting" value="1"/></characteristic-error></wap-provisioningdoc>|

2025-05-30 19:40:30.545|script-executor|E|DO|[net.soti.mobicontrol.xmlstage.d.execute:109] Mxconfig failed: /sdcard/download/SOTI_RMDataWedge.xml|net.soti.mobicontrol.device.a6: Process xml failed with errors characteristic-error - [DataWedgeMgr,ERROR],parm-error - [/sdcard/download/datawedge.db, Cannot read file],
    at net.soti.mobicontrol.xmlstage.j.m(SourceFile:36)
    at net.soti.mobicontrol.xmlstage.d.execute(SourceFile:47)
    at net.soti.mobicontrol.script.q0.m(SourceFile:21)
    at net.soti.mobicontrol.script.q0.t(SourceFile:27)
    at net.soti.mobicontrol.script.q0.k(SourceFile:54)
    at net.soti.mobicontrol.script.q0.i(SourceFile:8)
    at net.soti.mobicontrol.script.p0.run(SourceFile:1)
    at net.soti.mobicontrol.script.q0.h(SourceFile:8)
    at net.soti.mobicontrol.script.o0.run(SourceFile:1)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
    at java.lang.Thread.run(Thread.java:1012)

MD
Matt Dermody Diamond Contributor
6 months ago

I generally recommend creating new datawedge.db exports from the specific device models you intend to import them on. You can sometimes be successful importing across device models (i.e MC9300 to MC9450 in your situation) but I've experienced enough strange behavior attempting it historically that I've resorted to always building and exporting datawedge.db that are unique for the models that I'm targeting. Creating things from scratch on a MC9450 and then exporting that file to have a targeted install for that model is probably the best bet.  

I want to say Warehouse Mobile doesn't create the DataWedge profiles until after login, and possibly only after the first scan is then attempted. 

PC
Paul Courtney
6 months ago

Thanks Matt

I exported the current profile from one of the new devices, copied it to a different device and same error. 

This is working on the existing MC9450's that we had.  Just these new ones giving issues.

Someone must have fed the gremlins after midnight.

PC
Paul Courtney
6 months ago

I created a fresh profile on one of the 9450's and then copied to the file to another.  Same thing. Same error.

PC
Paul Courtney
6 months ago

When i manually import the file, the datawedge does not initially recognize the db file in the download folder (the first radio button).  I hit browse and open the download folder and this is where it thinks that file is. (second radio button).   I don't know enough about android to know if this is an issue.

E
ENMod
5 months ago

Hey Paul,

Thanks for posting on SOTI pulse. So as from what I can understand is that you have even tried exporting the profile from one of the new devices and you're still facing issues. Just for testing have you tried pushing the files to a much more accessible location like /enterprise/usr/ and executing the MXCofig file?

<parm-error name="ConfigurationFile" value="/sdcard/download/datawedge.db" desc=" Cannot read file"/> - suggests that DataWedge via MXCongfig no longer has permission to read that file at the location (/sdcard/download/)

Please let me know if you have any updates on the same. Thank you!!

Technical Support, SOTI | Call Us | SOTI.net | Discussion Forum | Log a Case Online

PC
Paul Courtney
5 months ago

Just tried it.  Same result.

2025-06-06 02:32:42.715|script-executor|E|DO|[net.soti.mobicontrol.xmlstage.d] Mxconfig failed: /enterprise/usr/SOTI_RMDataWedge_1.xml|net.soti.mobicontrol.device.a6: Process xml failed with errors characteristic-error - [DataWedgeMgr,ERROR],parm-error - [/enterprise/usr/datawedge.db, Cannot read file],

E
ENMod
5 months ago

Hey Paul,

Thank you for your response. This seems to be something which needs to be investigated further. I recommend you to log a case for the issue so that we can test this more efficiently and get a resolution for the same.

Technical Support, SOTI | Call Us | SOTI.net | Discussion Forum | Log a Case Online

PC
Paul Courtney
5 months ago

This runs with no errors.  Must be a difference between the lifeguard updates on how the mx system translates the url.

<wap-provisioningdoc>
    <characteristic version="13.5." type="DataWedgeMgr">
        <parm name="dwApiDatabaseImport" value="1" />
        <parm name="ConfigurationFile" value="%sdcard%/download/datawedge.db" />
        <parm name="AutoImporting" value="1" />
    </characteristic>
</wap-provisioningdoc>

mxconfig /storage/emulated/0/download/RM_DataWedge_Base.xml

Solution

Similar Discussions