Why is my data import with QIAGEN CLC Workbench failing?
Go Back This FAQ describes different reasons why import of your data into the Workbench(es) are failing. There are three common types of errors seen when importing data into the Workbench. These are:
Errors associated with the choice of importerErrors involving the term "Expected token" or "File not a X file" where the X could be something like "trace".Importing a file through the Standard import tool will usually run fine on properly formatted, intact files. When import fails with a message including the words "Expected token" or a message about the file not being imported because it is not a particular type of file, the usual cause is that the import option was set Force Import as Type and an inappropriate format type was selected. If you experience this, then please try the import again, this time selecting the import option "Automatic import". An example of the type of error message this pertains to is shown below, as it would appear in the Advanced tab of the error message window:
The Standard Import tool is described in more detail in the manual here: https://resources.qiagenbioinformatics.com/manuals/clcgenomicsworkbench/current/index.php?manual=Standard_import.html
Errors associated with corrupt dataThere are a number of different errors that can be associated with corrupt data. They include:
Errors like those in the list above indicate that the data is corrupt. This is a frequent problem when large files are copied across networks. When such errors arise, please check your data file to make sure it is intact. In some cases, it can be necessary to obtain a new copy from an original source. If you are not sure how to do this, we have some advice about how to check if data files are intact in a related FAQ entry: How can I check if my data file is corrupt?
Errors associated with misformatted dataGenbank files not importingThis topic is discussed in a related FAQ entry: Why isn't my Genbank file accepted for import? |