Exception when I try to open .lei images

Hi!
I am trying to open my images (taken from Sp2 confocal mycroscope) with FIJI and I obtain this exception window:

(Fiji Is Just) ImageJ 2.0.0-rc-19/1.49m; Java 1.6.0_24 [64-bit]; Windows NT (unknown) 6.2; 33MB of 2971MB (1%)
 
java.lang.NullPointerException
    at loci.formats.in.LeicaReader.getTIFFList(LeicaReader.java:847)
    at loci.formats.in.LeicaReader.parseFilenames(LeicaReader.java:902)
    at loci.formats.in.LeicaReader.initFile(LeicaReader.java:489)
    at loci.formats.FormatReader.setId(FormatReader.java:1317)
    at loci.plugins.in.ImportProcess.initializeFile(ImportProcess.java:494)
    at loci.plugins.in.ImportProcess.execute(ImportProcess.java:144)
    at loci.plugins.in.Importer.showDialogs(Importer.java:141)
    at loci.plugins.in.Importer.run(Importer.java:79)
    at loci.plugins.LociImporter.run(LociImporter.java:81)
    at ij.IJ.runUserPlugIn(IJ.java:202)
    at ij.IJ.runPlugIn(IJ.java:166)
    at ij.IJ.runPlugIn(IJ.java:155)
    at HandleExtraFileTypes.openImage(HandleExtraFileTypes.java:421)
    at HandleExtraFileTypes.run(HandleExtraFileTypes.java:57)
    at ij.IJ.runUserPlugIn(IJ.java:202)
    at ij.IJ.runPlugIn(IJ.java:166)
    at ij.IJ.runPlugIn(IJ.java:155)
    at ij.io.Opener.openWithHandleExtraFileTypes(Opener.java:483)
    at ij.io.Opener.openImage(Opener.java:361)
    at ij.io.Opener.openImage(Opener.java:242)
    at ij.io.Opener.open(Opener.java:155)
    at ij.io.Opener.openAndAddToRecent(Opener.java:291)
    at ij.plugin.DragAndDrop.openFile(DragAndDrop.java:176)
    at ij.plugin.DragAndDrop.run(DragAndDrop.java:152)
    at java.lang.Thread.run(Thread.java:662)

Can someone help me?
Thanks in advance!
Diana

Hi @Dianagm,
have you tried to update Bioformats plugin?
Have a nice day,
Emanuele Martini

As @emartini suggests, your Fiji is quite out of date. Try Help :arrow_forward: Update… to get the newest Bio-Formats. And actually, downloading a new Fiji from http://fiji.sc/#download will give you an even newer one, using Java 8 now.

Let us know if the problem still persists with the latest version.

2 Likes