SOTI Pulse Logo

DataWedge Import not working on VC8300 running Android 14 - SOLVED

Solved
AC
Austin Coy
Uline

We’re running into an issue with our Zebra VC8300 devices on Android 14 where DataWedge configurations are not importing.

Our current process works fine on Android 13 — the .db file is stored on the device in /sdcard/, and we push it via SOTI MobiControl using the DataWedgeMgr XML.

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

On Android 14, the same .db file will not import — even if I go into the DataWedge app on the device and attempt to import it manually. No errors appear; it simply doesn’t apply the configuration. I also tried creating a new StageNow Profile with a higher MX but that did not solve the problem.

Has anyone run into this with Android 14?

  • Did the import location change?

  • Is there a new permission requirement for DataWedge to access files?

  • Is .db importing deprecated in favor of another method?

Any insight or workaround would be appreciated.

android 14 datawedge
Edited 3 months ago
SOTI MobiControl
ANSWERS
CK
Chad Kohls
3 months ago

Is your .db a single DataWedge Profile or is it full configuration export?  I've had some problems with auto importing single profiles and have yet to figure it out, so I've resorted to exporting the full configuration in the meantime.

If it helps, I've typically pushed DataWedge configs to devices via a package.  I send the .db file to the folder below and then run a post-install script.  FYI, I sometimes I have reboot the device with this method, it just depends if the DataWedge app was open when this got pushed.  Hope it helps!

Destination on device: /enterprise/device/settings/datawedge/autoimport/

Post-Install script: __chmod 777 /enterprise/device/settings/datawedge/autoimport/datawedge.db

Solution
MD
Matt Dermody Diamond Contributor
3 months ago

I prefer this method as well over the MX driven method. It has worked very well for me historically on Zebra devices managed by SOTI.

If you're having issues with single profiles it might be because you've renamed the files? Try to avoid renaming the .db files that are created or they can fail to import.

For Austin I recommend you attempt to create a fresh new datawedge.db export on a VC8300 A14 and then try to leverage that using either your MX driven package process or the autoimport process. You may be having issues importing an older version of a .db created on an older version of DW. We are starting to see import issues with old .db files emerge as an issue again. 

AC
Austin Coy
3 months ago

Matt,

Thi

I went ahead and recreated the datawedge.db on A14 and now I'm at least having success with the manual import. I'm going to try updating the saved location to /enterprise/device/settings/datawedge/autoimport/datawedge.db as well vs. the sd card location. 

MD
Matt Dermody Diamond Contributor
3 months ago

I prefer this method as well over the MX driven method. It has worked very well for me historically on Zebra devices managed by SOTI.

If you're having issues with single profiles it might be because you've renamed the files? Try to avoid renaming the .db files that are created or they can fail to import.

For Austin I recommend you attempt to create a fresh new datawedge.db export on a VC8300 A14 and then try to leverage that using either your MX driven package process or the autoimport process. You may be having issues importing an older version of a .db created on an older version of DW. We are starting to see import issues with old .db files emerge as an issue again. 

AC
Austin Coy
3 months ago

After creating a new DataWedge Profile from an A14 device I used your advice to change the destination and added post-install script and it worked! Thank you for the help.

T
TLMOD@SOTI
3 months ago

Hi Austin,

Thanks for posting on SOTI pulse. Thanks Matt and Chad for responding to the post, your expertise and willingness to help are greatly appreciated!

Has your query been resolved? If not, or if you have any additional concerns, please don't hesitate to reach out. We are dedicated to providing assistance and support.

Also, if this post has helped you in solving your query, I would request you to mark the particular comment as "is solution", so that others may benefit from this information.

Similar Discussions