MX decoding error

Hi all,

I am trying to create a profile for a TC70x device. It's running Nougat 7.1.2, Lifeguard update 20. Settings show the MX as 9.0.4.3 . I tried to create a profile that is MX 8.0, but it was giving me batch decode errors about the MX version being newer than the one on the device. After checking out the Support/Downloads pages here: https://www.zebra.com/us/en/support-downloads/software/utilities/stageno... I noticed that Nougat only seems to support MX 7.0. That sucks, now I have to re-create my 28 step profile, but at least I know why it's broken right? Wrong! Even with the MX of 7.0 in the profile it still fails. I have restarted Stagenow, and the device, but there is no change.

Why is a device with an MX of 9+ unable to decode an MX of 7.0?

Thank you

edit: Error is now attached
2nd edit: Can't seem to see the image on this site, so here it is on Imgur: https://i.imgur.com/Wsel7U2.jpg

Attachments: 
Zachary Taylor
I need this addressed. Who do

I need this addressed. Who do I reach out to, if not this forum? I'd like to be clear that I'm not complaining, just looking for clarity.

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Zachary Taylor
Unfortunately, I am off-site

Unfortunately, I am off-site today. I will be back tomorrow with an exact error. I created that profile specifically to be MX 7.0 from scratch. It only had a few steps in it to test the MX mismatch issue, but it failed in the same manner.

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Richard Venderbosch
Reading installed Manager version numbers

I'm looking for an API to query the installed DSD versions on the device itself because they are what matters in the end ;-)

Richard.

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Darryn Campbell
Hi, so that StageNow

Hi, so that StageNow documentation link is confusing, although Nougat originally shipped with MX 7.0 you are right that the Lifeguard update 20 you have installed uses and should support MX 9.0.

Looking at the Batch Manager (https://techdocs.zebra.com/mx/batchmgr/) I notice there are some attributes like Batch Action and Trusted Mode Certificate file that require MX 9.2.  I know you said you created the profile with MX8.0 and so these attributes should not have been included in the profile but I wonder if some conversion issue happened somewhere down the line and MX 9.2 requirements got included in your profile, that would at least explain why you are getting the errors about your MX version being too old.

Another possibility is that the XML you are applying via the Batch Manager contains attributes that require an MX higher than 9.0 (I'm less sure about that as I've never used the batch manager)

A device with an MX of 9+ SHOULD be able to decode a profile whose MX is 7, as you say.

Could you try isolating the issue to a particular Manager? Or include the exact error details?

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Darryn Campbell
There is not a separate DSD

There is not a separate DSD version, there is just an MX version.  If you look at C:\Program Files (x86)\Symbol Technologies\Staging_Solution\DSD\DSD.zip under your StageNow installation you will see the different versions of the DSD definitions for each of the manager MX versions.  The version installed on your device should be the same as the MX version.  

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Zachary Taylor
Looks like the error is:

Looks like the error is:

'Batch Decoding -Exception, Could not decode profile data : DSD version invalid'

I've since tried with a different TC70x device with the same results...

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Richard Venderbosch
A bug?

That's also what I thought. Until I saw the "The DSD version is higher than current supported DSD" errors ...

Looks like there is a bug in some of the Nougat builds for the Atlas models.

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Richard Venderbosch
Similar problem with GPRS Manager

I saw similar errors when adding an APN on a TC75X running Android 7.1 with OS build number "02-07-08.00-NN-U01-STD" and "Mxmf" version "9.4.0.2".

Error message was (removed/changed some parameters for privacy reasons)
'<wap-provisioningdoc><characteristic-error type=\"GprsMgr\" version=\"8.4\" desc=\"The DSD version is higher than current supported DSD 8.4\"><parm name=\"GprsAction\" value=\"1\"/><parm name=\"GprsCarrier\" value=\"0\"/><characteristic type=\"gprs-details\"><parm name=\"ApnName\" value=\"xxxxxxx"/><parm name=\"ReplaceIfExisting\" value=\"1\"/><parm name=\"MakeDefault\" value=\"1\"/></characteristic><characteristic type=\"custom-details\"><parm name=\"CustomAccessPoint\" value=\"xxxxx.com\"/><parm name=\"CustomUserName\" value=\"xxx\"/><parm name=\"CustomPassword\" value=\"xxx\"/><parm name=\"CustomType\" value=\"default\"/><parm name=\"CustomAuthType\" value=\"4\"/><parm name=\"CustomMcc\" value=\"123\"/><parm name=\"CustomMnc\" value=\"45\"/><parm name=\"CustomProtocol\" value=\"1\"/><parm name=\"CustomRoamingProtocol\" value=\"1\"/></characteristic></characteristic-error></wap-provisioningdoc>'

According to the MX documentation parameters "CustomProtocol" and "CustomRoamingProtocol" require "MX: 9.3+".
With MX version "9.4.0.2" adding them should not be a problem.
But "GprsMgr" on the (non-GMS Nougat) TC75X device has only version "8.4" - and not 9.4 as expected or 9.3 as used by my code in the MX call.

Is there a way to query the individual manager version numbers?

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Darryn Campbell
>Is there a way to query the

>Is there a way to query the individual manager version numbers?

Please see https://techdocs.zebra.com/mx/ which breaks down the requirements for each manager's property (OSX, MX and Android API level)

Vote: 
Vote up!
Vote down!

Points: 0

You voted ‘up’


Topic locked