Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

The file that you are trying to import is not a supported file format. Only TAR file format is supported.

Hello,

I'm trying to import a .tar file exported from a UTM with the current firmware version 9.718005 into an XGS 136, following this guide. However, I keep encountering the familiar error message "The file that you are trying to import is not a supported file format. Only TAR file format is supported."

Link to the guide:

The logs don't provide much insight. From the errors in the tail /log/csc.log -f |grep import logs, it seems like there's an issue with the import process.

Does anyone have any ideas on how to resolve this? Any help would be greatly appreciated.

XGS136_XN02_SFOS 20.0.0 GA-Build222# tail /log/apiparser.log -f
ERROR     Feb 06 16:05:48Z [28174]: XML file is not valid. So Exiting with status 10...
ERROR     Feb 06 16:23:55Z [1280]: XML file is not valid. So Exiting with status 10...

XGS136_XN02_SFOS 20.0.0 GA-Build222# tail /log/csc.log -f |grep import
MESSAGE   Feb 06 16:05:48Z  [worker:28117]: {"request":{"method":"opcode","name":"upload_text_import_file","version":"1.2","type":"json","length":393,"data":{ "___serverport": 4444, "importtype": "2", "___component": "GUI", "transactionid": "1807", "mode": 727, "currentlyloggedinuserid": 3, "importfile": "\/sdisk\/upload\/00f8c69b-6c9d-4bcb-a5e2-e7a35dd84098.tar", "APIVersion": "2000.1", "___serverprotocol": "HTTP", "___username": "admin", "___meta": { "sessionType": 1 }, "___serverip": "172.16.16.16", "currentlyloggedinuserip": "172.16.16.1" }}}
ERROR     Feb 06 16:05:48Z  [timer:6002]: delete_sched_node: timer clean_importfiles do not exist
ERROR     Feb 06 16:05:48Z  [upload_text_import_file:28117]: csc_execve: Child exited with status 10
ERROR     Feb 06 16:05:48Z  [upload_text_import_file:28117]: log_exec: Failed Command: /usr/bin/crimport -s -i /sdisk/APIImport.tar  -a ?? -v /_conf/csc/IOMappingFiles/ -l /log/apiparser.log -C ?? -R ?? $CURR_API_DISPLAY_VERSION $ips_cat_corp_ver $ips_rules_cnt
WARNING   Feb 06 16:05:48Z  [upload_text_import_file:28117]: Action with NOFAIL Failed.
MESSAGE   Feb 06 16:05:48Z  [upload_text_import_file:28117]: opcode 'upload_text_import_file': time taken: 0.311405645 seconds with return status: '500'



This thread was automatically locked due to age.
Parents
  • When you export you might get a .tar file that just contains Entities.xml

    When you export you might get a .tar file that contains Entities.xml and also subdirectories containing files.  For example exporting certificates.  The XML will refer to the files.


    If you open the tar, edit the Entities and then re-tar the file, then (assuming that you haven't messed up the XML) it should work fine.  However I have a recollection that whenever the subdirectories are involved it gets messy and that error message can appear.

Reply
  • When you export you might get a .tar file that just contains Entities.xml

    When you export you might get a .tar file that contains Entities.xml and also subdirectories containing files.  For example exporting certificates.  The XML will refer to the files.


    If you open the tar, edit the Entities and then re-tar the file, then (assuming that you haven't messed up the XML) it should work fine.  However I have a recollection that whenever the subdirectories are involved it gets messy and that error message can appear.

Children
No Data