The log file is the first place to look if import of a xar.xml file fails. Some advice on using it:

  • Often the actual error message is cryptic, but the success/info messages above it should give you an indication of how far the import progressed before it encountered the error.
  • The most common problem in importing xar.xml files is a duplicate LSID problem. In example 1 of the XAR Tutorial, the LSIDs have fixed values. This means that this xar.xml can only be imported in one folder on the whole system. If you are sharing access to a LabKey Server system with some other user of this tutorial you will encounter this problem. Subsequent examples in the tutorial will show you how to address this.
  • A second common problem is clashing LSID objects at the run level. If an object is created by a particular ProtocolApplication and then a second ProtApp tries to output an object with the same LSID, an error will result.
  • LabKey Server does not offer the ability to delete protocols or starting inputs or in a folder, except for deleting the entire folder. This means that if you import a xar.xml in a folder and then change a protocol or starting input without changing its LSID , you won't see your changes. The XarReader currently checks first to see if the protocols in a xar.xml have already been defined, and if so will silently use the existing protocols rather than the (possibly changed ) protocol descriptions in the xar.xml. See example 3 in the XAR Tutorial for a suggestion of how to avoid problems with this.
  • Sometimes a xar.xml will appear to import correctly but report an error when you try to view the summary graph. This seems to happen most often because of problems in referencing the Starting Inputs.


Was this content helpful?

Log in or register an account to provide feedback

expand all collapse all