News:Ensembl 103 has been released
Entering edit mode
Last seen 18 months ago
United Kingdom

Dear all

The new Ensembl marts for release 103 are now live on If you are using biomaRt, you can change your host to access our most recent data:

ensemblmart103 <- useEnsembl(biomart=“ensembl")

PS: if you want force one previous version you can use: ensembl_101 <- useEnsembl(biomart = "ensembl", version = 101)

On behalf of Ensembl Team.

biomaRt ensembldb Ensembl ensemblVEP Biomart • 1.1k views
Entering edit mode

I tried this (it works fine with ensembl version 99)

ensembl_102 = useEnsembl(biomart="ensembl", version=102)

ensembl_102 = useDataset("hsapiens_gene_ensembl", mart=ensembl_102)

getBM(attributes=c('ensembl_gene_id', 'ensembl_gene_id_version',

  • 'ensembl_transcript_id', 'ensembl_transcript_id_version',
  • 'external_gene_name'),
  • filters = c('ensembl_gene_id'),
  • values = lungSet1_filter1$ensgene,
  • mart = ensembl_102)

and I get:

NULL Error in .processResults(postRes, mart = mart, sep = sep, fullXmlQuery = fullXmlQuery, : The query to the BioMart webservice returned an invalid result. The number of columns in the result table does not equal the number of attributes in the query. Please report this on the support site at

Is there something wrong with my code or am I being too impatient?

I've tried setting the address of the archived version 102 as host, but it doesn't work. listMarts for version 102 returns this:

listMarts(host="") biomart version 1 ENSEMBL_MART_ENSEMBL Ensembl Genes 103 2 ENSEMBL_MART_MOUSE Mouse strains 103 3 ENSEMBL_MART_SNP Ensembl Variation 103 4 ENSEMBL_MART_FUNCGEN Ensembl Regulation 103

Entering edit mode

Hi there, sorry for the late reply, I failed to reproduce your error, I don't have the values specified in your example, of course. Can you confirm the issue is still present?

Thanks for your patience. Marc (on behalf of EnsEMBL production team)


Login before adding your answer.

Traffic: 740 users visited in the last hour
Help About
Access RSS

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6