java.io.IOException

Error in line 1394 or above: Empty text token. This could be caused by a missing comma between two fields.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web20996

  • via GitHub by mtecfred
    , 11 months ago
    Error in line 1394 or above: Empty text token. This could be caused by a missing comma between two fields.
  • via jabref by vengoroso
    , 1 year ago
    Error in line 3 or above: Empty text token. This could be caused by a missing comma between two fields.
  • Error in line 1357 or above: Empty text token. This could be caused by a missing comma between two fields.
  • Stack trace

    • java.io.IOException: Error in line 1394 or above: Empty text token. This could be caused by a missing comma between two fields. at net.sf.jabref.importer.fileformat.BibtexParser.parseFieldContent(BibtexParser.java:599)[JabRef-3.6dev--snapshot--2016-08-10--master--4c1c13b.jar:?] at net.sf.jabref.importer.fileformat.BibtexParser.parseField(BibtexParser.java:547)[JabRef-3.6dev--snapshot--2016-08-10--master--4c1c13b.jar:?] at net.sf.jabref.importer.fileformat.BibtexParser.parseEntry(BibtexParser.java:531)[JabRef-3.6dev--snapshot--2016-08-10--master--4c1c13b.jar:?] at net.sf.jabref.importer.fileformat.BibtexParser.parseAndAddEntry(BibtexParser.java:227)[JabRef-3.6dev--snapshot--2016-08-10--master--4c1c13b.jar:?] at net.sf.jabref.importer.fileformat.BibtexParser.parseFileContent(BibtexParser.java:197)[JabRef-3.6dev--snapshot--2016-08-10--master--4c1c13b.jar:?] at net.sf.jabref.importer.fileformat.BibtexParser.parse(BibtexParser.java:158)[JabRef-3.6dev--snapshot--2016-08-10--master--4c1c13b.jar:?] at net.sf.jabref.importer.fileformat.BibtexParser.parse(BibtexParser.java:98)[JabRef-3.6dev--snapshot--2016-08-10--master--4c1c13b.jar:?] at net.sf.jabref.importer.fileformat.BibtexImporter.importDatabase(BibtexImporter.java:78)[JabRef-3.6dev--snapshot--2016-08-10--master--4c1c13b.jar:?] at net.sf.jabref.importer.fileformat.ImportFormat.importDatabase(ImportFormat.java:90)[JabRef-3.6dev--snapshot--2016-08-10--master--4c1c13b.jar:?] at net.sf.jabref.importer.fileformat.BibtexImporter.importDatabase(BibtexImporter.java:70)[JabRef-3.6dev--snapshot--2016-08-10--master--4c1c13b.jar:?] at net.sf.jabref.importer.OpenDatabaseAction.loadDatabase(OpenDatabaseAction.java:341)[JabRef-3.6dev--snapshot--2016-08-10--master--4c1c13b.jar:?] at net.sf.jabref.importer.OpenDatabaseAction.loadDatabaseOrAutoSave(OpenDatabaseAction.java:395)[JabRef-3.6dev--snapshot--2016-08-10--master--4c1c13b.jar:?] at net.sf.jabref.JabRefGUI.openLastEditedDatabases(JabRefGUI.java:236)[JabRef-3.6dev--snapshot--2016-08-10--master--4c1c13b.jar:?] at net.sf.jabref.JabRefGUI.openWindow(JabRefGUI.java:113)[JabRef-3.6dev--snapshot--2016-08-10--master--4c1c13b.jar:?] at net.sf.jabref.JabRefGUI.<init>(JabRefGUI.java:79)[JabRef-3.6dev--snapshot--2016-08-10--master--4c1c13b.jar:?] at net.sf.jabref.JabRefMain.lambda$start$1(JabRefMain.java:118)[JabRef-3.6dev--snapshot--2016-08-10--master--4c1c13b.jar:?]

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.