fastqsanger.gz file not recognized in


I uploaded a paired-end SRR file using fastq-dump. The filetype says it is a fastqsanger.gz but when I try to run Trimmomatic or Trim Galore, they both say they cannot find any fastqsanger.gz datasets.
Is this not the correct way to do this?

1 Like

Hi @ajnaram!

That is the correct way.

Both of the fastqsanger.gz datasets are green in color? And this datatype was assigned by the tool used (not assigned/reassigned by you?)

If the data upload was successful, check to make sure you are launching the tool forms with the target datasets in the currently active history? Click on the “refresh history” icon to confirm:


If the history content changes, then go to your saved histories, switch to the history with your data in it, and try again.

One last thing to double check (would be rare now) is if the data is in a related format of fastqcssanger.gz. (Note the “cs” in the name). Sometimes people assign this datatype by accident or the data uploaded really is in the color space format. The tool Fastq Groomer can be used to transform to fastqsanger (if actually needed – use the tool FastQC to check).

FAQs that might help (see the first three):

Let us know how that goes and we can follow up from there. Please confirm that you are working at Galaxy Main as indicated by the tags added to the post.


Yes the datasets are green and the datatype was assigned by the upload tool.

My correct history was active.

I didn’t have any cs files but I ran through fastq groomer just in case. Still the same problem.

The same error occurred in the .eu version, but I initially saw it in the .org version.


1 Like

Could you please post a screenshot of one of the unrecognized fastq datasets? Expand it first (click on the dataset “name”). We might be able to identify the problem from that view.

If that doesn’t work, I’ll need to look at your account at Galaxy Main as an admin.

  • If your registered email here at this site is the same as used for your account at the “org” server, just post back the name of the history and a few of the problematic dataset numbers.
  • If the email addresses are different, please send me a direct message here with your email address with the same history/dataset info. You don’t need to post your email address publicly.

But let’s try a posted screenshot first. This Q&A might help others, later on, should they run into the same type of issue.


History name is Grantia

1 Like

Hi - I couldn’t find your account at

That said, this looks like an interlaced fastq dataset in compressed format. It should be recognized by tools based on the assigned datatype “fastqsanger.gz”. But you might run into problems after that.

Most tools will expect that paired end data is in two distinct datasets – one representing the forward reads, one representing the reverse reads. This includes Trimmomatic and Trim Galore!.

Run the tool Fastq De-interlacer to split up your current data, then see if the tools find your inputs correctly.



Thank you for the help!
I’ll try the de-interlacer though it was buggy for me the last times I tried it (reported bug).

1 Like

Hum, ok, if failed there is probably something wrong with the sequence identifiers. The tool requires some specific formatting to split the reads.

The FAQ has an alternative method that is custom, based on your identifiers, whatever they may be. There are also a few other ways to do this – let us know if continue to have problems and I’ll look directly at your data and help. Not every bug report has the data examined in granular detail (for obvious reasons) … but we try :slight_smile: and can help, especially if you get completely stuck at some step.