MIB Error Type and Suggested Solutions

Error 1.1: An error occurred. (MIB type in uploaded file does not match selected MIB type.)

Suggested solution: To check whether the MIB uploaded is correct or not, follow the below-mentioned steps:

A. Download the MIB from the publish portal you’re trying to upload.

Rename the file extension ".mib" and enter ".zip" instead. If the system asks you if you wish to do this, click "yes" or "use .zip" depending on your OS.

 

B. Double click on the file to unzip a folder named as your GUID and version number.

C. Go into the folder and you should find a folder named "verticals" and an "issue.xml"- file. Open the "issue.xml" with a text editor.

D. In the text editor you should see something similar to the screenshot below.

 

E. As highlighted in the above screenshot you can identify whether the MIB you uploaded is of which device and for which device you’re trying to upload on publish portal.

Error 1.2: An error occurred. (Validation failed: Guid base expected GUID-base to be ["VIDEOFEATURE.ANDROIDTABLET”] but got Alarm.hardware_android.)

Suggested solution: To elaborate, the ‘GUID’ of your MIB is automatically generated from the ‘BrandID’, ‘IssueID’, and ‘Version Number'. This is an internal identifier and is used by Publish to verify and serve the MIB. All MIB versions you upload to your issue in Publish should be created using the same GUID base- that is, IssueID and BrandID- but with a unique version number.

That said, it's important to note that once you’ve successfully uploaded a GUID for a particular device (i.e Apple iPad), that exact GUID must be used going forward (along with a new Version Number that has not been used yet). This ensures that any additional MIBs for that device will upload successfully in the future.

Now- although this is device-specific, and you can have different GUID's for different devices, we recommend that you keep them all the same (mentioned above) and just have the version number different/unique each time. Ultimately though, it’s up to you.

Error 1.3: An error occurred. (Validation failed: Guid version has already been taken)

Suggested solution: The reason for this error is because the GUID version number of the MIB file you are uploading is already in use. The GUID of your MIB is automatically generated from the BrandID and IssueID along with a sequence/version number. This is an internal identifier and used by Publish to verify and serve the MIB. All MIB versions you upload to your issue in Publish need to be created using the same GUID base, that is IssueID and BrandID, but with a unique sequence/version number. Within the Production Tool, you can double-click in the GUID field to manually edit the version number at the end of the string. If you are creating multiple MIBs at once (for different devices) with the Create MIB button, the Production Tool will version them automatically.

Another way to fix this is by manually changing the "GUID" and/or "Version Number" (via the xml) by following the steps from Manually change the GUID of a MIB very carefully. Please note the GUID and Version Number cannot be changed simply by editing the filename externally, as Publish reads the xml code within for processing.

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk