Sorry, but “MiKTeX Compiler Driver” did not succeed. FATAL texify - BibTeX failed for some reason











up vote
0
down vote

favorite












I am trying to run some latex files on a new computer. I am using an external hard drive that is a direct copy of my previous computer so the files all should be fine, however I am getting the error:



Sorry, but "MiKTeX Compiler Driver" did not succeed.
The log file hopefully contains the information to get MiKTeX going again:
C:/Users/******/AppData/Local/MiKTeX/2.9/miktex/log/texify.log
You may want to visit the MiKTeX project page, if you need help.


I have found lots of threads on this, but none of the solutions given have worked for me. I have tried deleting aux files and re-running, I have tried running from command prompt, I have tried uninstalling and reinstalling MiKTeX, I have tried running initexmf --mkmaps --verbose from the command prompt. The log file it directs me too reads as follows:



2018-03-15 11:36:30,425Z INFO  texify - starting with command line: 
"C:Program FilesMiKTeX 2.9miktexbinx64texify.exe" --pdf --synctex=1 --clean warwickthesis.tex
2018-03-15 11:36:49,382Z FATAL texify - BibTeX failed for some reason.
2018-03-15 11:36:49,382Z FATAL texify - Info:
2018-03-15 11:36:49,382Z FATAL texify - Source:
ProgramsMiKTeXtexifymcd.cpp
2018-03-15 11:36:49,382Z FATAL texify - Line: 1286


I have since tried running just pdflatex - this works but obviously does not create references etc. Running just bibtex does not work and returns this in the blg file:



This is BibTeX, Version 0.99dThe top-level auxiliary file: warwickthesis.aux
The style file: unsrt.bst
Database file #1: library.bib
Repeated entry---line 1242 of file library.bib
: @article{Takishita2015
: ,
I'm skipping whatever remains of this entry
Repeated entry---line 1396 of file library.bib
: @article{Grassie2005
: ,
I'm skipping whatever remains of this entry
Warning--I didn't find a database entry for "Haidemenopoulos2016"
Warning--I didn't find a database entry for "Hughes2015"
Warning--I didn't find a database entry for "Blitz1997"
Warning--I didn't find a database entry for "Bieber1998"
Warning--I didn't find a database entry for "Tian2005"
Warning--I didn't find a database entry for "Mina1997"
Warning--I didn't find a database entry for "Drinkwater2006"
Warning--I didn't find a database entry for "Grimberg2006"
Warning--I didn't find a database entry for "Edwards2008a"
Warning--I didn't find a database entry for "Gros1999"
Warning--I didn't find a database entry for "Hughes2014"
Warning--I didn't find a database entry for "Honarvar2013"
Warning--I didn't find a database entry for "Alvarez-Arenas2013"
Warning--I didn't find a database entry for "Kang2017"
... etc (few more of these)
Warning--empty journal in Ewert2013
Warning--can't use both author and editor fields in Achenbach1999
Warning--empty journal in Blake1990
Warning--empty note in Thring2018
(There were 2 error messages)


This is odd as the references are in my library created by Mendeley and the referencing works fine on a different computer.



Any suggestions?










share|improve this question
















bumped to the homepage by Community 9 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 3




    Don't use texify when you have a problem. It's error messages are often bad or meaningless. Call the tools individually.
    – Ulrike Fischer
    Mar 15 at 12:40










  • Ulrike Fischer, I'm sorry I don't know how to do that, could you elaborate for me?
    – Claire Thring
    Mar 15 at 13:51










  • Delete the auxiliary files (toc, aux,bbl). Run only pdflatex. If it doesn't succeeds find out why pdflatex fails by checking the log-file and correct the error. If it succeeds run bibtex. Check the blg if it did succeed. If yes run pdflatex again.
    – Ulrike Fischer
    Mar 15 at 14:02










  • Ok, it now runs with just pdflatex, although it didn't before strangly. It does not run with bibtex. This is the log file: 2018-03-15 14:09:35,734Z INFO miktex-bibtex - starting with command line: "C:MiKTeK Program Filesmiktexbinx64miktex-bibtex.exe" warwickthesis 2018-03-15 14:09:35,805Z INFO miktex-bibtex - finishing with exit code 1 This error doesn't tell me any more though? It does not seem to like my library, however it is the same one I used on a different computer which worked fine?
    – Claire Thring
    Mar 15 at 14:11








  • 1




    Edit the question to add the info.
    – Ulrike Fischer
    Mar 15 at 16:00















up vote
0
down vote

favorite












I am trying to run some latex files on a new computer. I am using an external hard drive that is a direct copy of my previous computer so the files all should be fine, however I am getting the error:



Sorry, but "MiKTeX Compiler Driver" did not succeed.
The log file hopefully contains the information to get MiKTeX going again:
C:/Users/******/AppData/Local/MiKTeX/2.9/miktex/log/texify.log
You may want to visit the MiKTeX project page, if you need help.


I have found lots of threads on this, but none of the solutions given have worked for me. I have tried deleting aux files and re-running, I have tried running from command prompt, I have tried uninstalling and reinstalling MiKTeX, I have tried running initexmf --mkmaps --verbose from the command prompt. The log file it directs me too reads as follows:



2018-03-15 11:36:30,425Z INFO  texify - starting with command line: 
"C:Program FilesMiKTeX 2.9miktexbinx64texify.exe" --pdf --synctex=1 --clean warwickthesis.tex
2018-03-15 11:36:49,382Z FATAL texify - BibTeX failed for some reason.
2018-03-15 11:36:49,382Z FATAL texify - Info:
2018-03-15 11:36:49,382Z FATAL texify - Source:
ProgramsMiKTeXtexifymcd.cpp
2018-03-15 11:36:49,382Z FATAL texify - Line: 1286


I have since tried running just pdflatex - this works but obviously does not create references etc. Running just bibtex does not work and returns this in the blg file:



This is BibTeX, Version 0.99dThe top-level auxiliary file: warwickthesis.aux
The style file: unsrt.bst
Database file #1: library.bib
Repeated entry---line 1242 of file library.bib
: @article{Takishita2015
: ,
I'm skipping whatever remains of this entry
Repeated entry---line 1396 of file library.bib
: @article{Grassie2005
: ,
I'm skipping whatever remains of this entry
Warning--I didn't find a database entry for "Haidemenopoulos2016"
Warning--I didn't find a database entry for "Hughes2015"
Warning--I didn't find a database entry for "Blitz1997"
Warning--I didn't find a database entry for "Bieber1998"
Warning--I didn't find a database entry for "Tian2005"
Warning--I didn't find a database entry for "Mina1997"
Warning--I didn't find a database entry for "Drinkwater2006"
Warning--I didn't find a database entry for "Grimberg2006"
Warning--I didn't find a database entry for "Edwards2008a"
Warning--I didn't find a database entry for "Gros1999"
Warning--I didn't find a database entry for "Hughes2014"
Warning--I didn't find a database entry for "Honarvar2013"
Warning--I didn't find a database entry for "Alvarez-Arenas2013"
Warning--I didn't find a database entry for "Kang2017"
... etc (few more of these)
Warning--empty journal in Ewert2013
Warning--can't use both author and editor fields in Achenbach1999
Warning--empty journal in Blake1990
Warning--empty note in Thring2018
(There were 2 error messages)


This is odd as the references are in my library created by Mendeley and the referencing works fine on a different computer.



Any suggestions?










share|improve this question
















bumped to the homepage by Community 9 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 3




    Don't use texify when you have a problem. It's error messages are often bad or meaningless. Call the tools individually.
    – Ulrike Fischer
    Mar 15 at 12:40










  • Ulrike Fischer, I'm sorry I don't know how to do that, could you elaborate for me?
    – Claire Thring
    Mar 15 at 13:51










  • Delete the auxiliary files (toc, aux,bbl). Run only pdflatex. If it doesn't succeeds find out why pdflatex fails by checking the log-file and correct the error. If it succeeds run bibtex. Check the blg if it did succeed. If yes run pdflatex again.
    – Ulrike Fischer
    Mar 15 at 14:02










  • Ok, it now runs with just pdflatex, although it didn't before strangly. It does not run with bibtex. This is the log file: 2018-03-15 14:09:35,734Z INFO miktex-bibtex - starting with command line: "C:MiKTeK Program Filesmiktexbinx64miktex-bibtex.exe" warwickthesis 2018-03-15 14:09:35,805Z INFO miktex-bibtex - finishing with exit code 1 This error doesn't tell me any more though? It does not seem to like my library, however it is the same one I used on a different computer which worked fine?
    – Claire Thring
    Mar 15 at 14:11








  • 1




    Edit the question to add the info.
    – Ulrike Fischer
    Mar 15 at 16:00













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I am trying to run some latex files on a new computer. I am using an external hard drive that is a direct copy of my previous computer so the files all should be fine, however I am getting the error:



Sorry, but "MiKTeX Compiler Driver" did not succeed.
The log file hopefully contains the information to get MiKTeX going again:
C:/Users/******/AppData/Local/MiKTeX/2.9/miktex/log/texify.log
You may want to visit the MiKTeX project page, if you need help.


I have found lots of threads on this, but none of the solutions given have worked for me. I have tried deleting aux files and re-running, I have tried running from command prompt, I have tried uninstalling and reinstalling MiKTeX, I have tried running initexmf --mkmaps --verbose from the command prompt. The log file it directs me too reads as follows:



2018-03-15 11:36:30,425Z INFO  texify - starting with command line: 
"C:Program FilesMiKTeX 2.9miktexbinx64texify.exe" --pdf --synctex=1 --clean warwickthesis.tex
2018-03-15 11:36:49,382Z FATAL texify - BibTeX failed for some reason.
2018-03-15 11:36:49,382Z FATAL texify - Info:
2018-03-15 11:36:49,382Z FATAL texify - Source:
ProgramsMiKTeXtexifymcd.cpp
2018-03-15 11:36:49,382Z FATAL texify - Line: 1286


I have since tried running just pdflatex - this works but obviously does not create references etc. Running just bibtex does not work and returns this in the blg file:



This is BibTeX, Version 0.99dThe top-level auxiliary file: warwickthesis.aux
The style file: unsrt.bst
Database file #1: library.bib
Repeated entry---line 1242 of file library.bib
: @article{Takishita2015
: ,
I'm skipping whatever remains of this entry
Repeated entry---line 1396 of file library.bib
: @article{Grassie2005
: ,
I'm skipping whatever remains of this entry
Warning--I didn't find a database entry for "Haidemenopoulos2016"
Warning--I didn't find a database entry for "Hughes2015"
Warning--I didn't find a database entry for "Blitz1997"
Warning--I didn't find a database entry for "Bieber1998"
Warning--I didn't find a database entry for "Tian2005"
Warning--I didn't find a database entry for "Mina1997"
Warning--I didn't find a database entry for "Drinkwater2006"
Warning--I didn't find a database entry for "Grimberg2006"
Warning--I didn't find a database entry for "Edwards2008a"
Warning--I didn't find a database entry for "Gros1999"
Warning--I didn't find a database entry for "Hughes2014"
Warning--I didn't find a database entry for "Honarvar2013"
Warning--I didn't find a database entry for "Alvarez-Arenas2013"
Warning--I didn't find a database entry for "Kang2017"
... etc (few more of these)
Warning--empty journal in Ewert2013
Warning--can't use both author and editor fields in Achenbach1999
Warning--empty journal in Blake1990
Warning--empty note in Thring2018
(There were 2 error messages)


This is odd as the references are in my library created by Mendeley and the referencing works fine on a different computer.



Any suggestions?










share|improve this question















I am trying to run some latex files on a new computer. I am using an external hard drive that is a direct copy of my previous computer so the files all should be fine, however I am getting the error:



Sorry, but "MiKTeX Compiler Driver" did not succeed.
The log file hopefully contains the information to get MiKTeX going again:
C:/Users/******/AppData/Local/MiKTeX/2.9/miktex/log/texify.log
You may want to visit the MiKTeX project page, if you need help.


I have found lots of threads on this, but none of the solutions given have worked for me. I have tried deleting aux files and re-running, I have tried running from command prompt, I have tried uninstalling and reinstalling MiKTeX, I have tried running initexmf --mkmaps --verbose from the command prompt. The log file it directs me too reads as follows:



2018-03-15 11:36:30,425Z INFO  texify - starting with command line: 
"C:Program FilesMiKTeX 2.9miktexbinx64texify.exe" --pdf --synctex=1 --clean warwickthesis.tex
2018-03-15 11:36:49,382Z FATAL texify - BibTeX failed for some reason.
2018-03-15 11:36:49,382Z FATAL texify - Info:
2018-03-15 11:36:49,382Z FATAL texify - Source:
ProgramsMiKTeXtexifymcd.cpp
2018-03-15 11:36:49,382Z FATAL texify - Line: 1286


I have since tried running just pdflatex - this works but obviously does not create references etc. Running just bibtex does not work and returns this in the blg file:



This is BibTeX, Version 0.99dThe top-level auxiliary file: warwickthesis.aux
The style file: unsrt.bst
Database file #1: library.bib
Repeated entry---line 1242 of file library.bib
: @article{Takishita2015
: ,
I'm skipping whatever remains of this entry
Repeated entry---line 1396 of file library.bib
: @article{Grassie2005
: ,
I'm skipping whatever remains of this entry
Warning--I didn't find a database entry for "Haidemenopoulos2016"
Warning--I didn't find a database entry for "Hughes2015"
Warning--I didn't find a database entry for "Blitz1997"
Warning--I didn't find a database entry for "Bieber1998"
Warning--I didn't find a database entry for "Tian2005"
Warning--I didn't find a database entry for "Mina1997"
Warning--I didn't find a database entry for "Drinkwater2006"
Warning--I didn't find a database entry for "Grimberg2006"
Warning--I didn't find a database entry for "Edwards2008a"
Warning--I didn't find a database entry for "Gros1999"
Warning--I didn't find a database entry for "Hughes2014"
Warning--I didn't find a database entry for "Honarvar2013"
Warning--I didn't find a database entry for "Alvarez-Arenas2013"
Warning--I didn't find a database entry for "Kang2017"
... etc (few more of these)
Warning--empty journal in Ewert2013
Warning--can't use both author and editor fields in Achenbach1999
Warning--empty journal in Blake1990
Warning--empty note in Thring2018
(There were 2 error messages)


This is odd as the references are in my library created by Mendeley and the referencing works fine on a different computer.



Any suggestions?







miktex






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 16 at 9:11

























asked Mar 15 at 12:14









Claire Thring

62




62





bumped to the homepage by Community 9 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 9 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.










  • 3




    Don't use texify when you have a problem. It's error messages are often bad or meaningless. Call the tools individually.
    – Ulrike Fischer
    Mar 15 at 12:40










  • Ulrike Fischer, I'm sorry I don't know how to do that, could you elaborate for me?
    – Claire Thring
    Mar 15 at 13:51










  • Delete the auxiliary files (toc, aux,bbl). Run only pdflatex. If it doesn't succeeds find out why pdflatex fails by checking the log-file and correct the error. If it succeeds run bibtex. Check the blg if it did succeed. If yes run pdflatex again.
    – Ulrike Fischer
    Mar 15 at 14:02










  • Ok, it now runs with just pdflatex, although it didn't before strangly. It does not run with bibtex. This is the log file: 2018-03-15 14:09:35,734Z INFO miktex-bibtex - starting with command line: "C:MiKTeK Program Filesmiktexbinx64miktex-bibtex.exe" warwickthesis 2018-03-15 14:09:35,805Z INFO miktex-bibtex - finishing with exit code 1 This error doesn't tell me any more though? It does not seem to like my library, however it is the same one I used on a different computer which worked fine?
    – Claire Thring
    Mar 15 at 14:11








  • 1




    Edit the question to add the info.
    – Ulrike Fischer
    Mar 15 at 16:00














  • 3




    Don't use texify when you have a problem. It's error messages are often bad or meaningless. Call the tools individually.
    – Ulrike Fischer
    Mar 15 at 12:40










  • Ulrike Fischer, I'm sorry I don't know how to do that, could you elaborate for me?
    – Claire Thring
    Mar 15 at 13:51










  • Delete the auxiliary files (toc, aux,bbl). Run only pdflatex. If it doesn't succeeds find out why pdflatex fails by checking the log-file and correct the error. If it succeeds run bibtex. Check the blg if it did succeed. If yes run pdflatex again.
    – Ulrike Fischer
    Mar 15 at 14:02










  • Ok, it now runs with just pdflatex, although it didn't before strangly. It does not run with bibtex. This is the log file: 2018-03-15 14:09:35,734Z INFO miktex-bibtex - starting with command line: "C:MiKTeK Program Filesmiktexbinx64miktex-bibtex.exe" warwickthesis 2018-03-15 14:09:35,805Z INFO miktex-bibtex - finishing with exit code 1 This error doesn't tell me any more though? It does not seem to like my library, however it is the same one I used on a different computer which worked fine?
    – Claire Thring
    Mar 15 at 14:11








  • 1




    Edit the question to add the info.
    – Ulrike Fischer
    Mar 15 at 16:00








3




3




Don't use texify when you have a problem. It's error messages are often bad or meaningless. Call the tools individually.
– Ulrike Fischer
Mar 15 at 12:40




Don't use texify when you have a problem. It's error messages are often bad or meaningless. Call the tools individually.
– Ulrike Fischer
Mar 15 at 12:40












Ulrike Fischer, I'm sorry I don't know how to do that, could you elaborate for me?
– Claire Thring
Mar 15 at 13:51




Ulrike Fischer, I'm sorry I don't know how to do that, could you elaborate for me?
– Claire Thring
Mar 15 at 13:51












Delete the auxiliary files (toc, aux,bbl). Run only pdflatex. If it doesn't succeeds find out why pdflatex fails by checking the log-file and correct the error. If it succeeds run bibtex. Check the blg if it did succeed. If yes run pdflatex again.
– Ulrike Fischer
Mar 15 at 14:02




Delete the auxiliary files (toc, aux,bbl). Run only pdflatex. If it doesn't succeeds find out why pdflatex fails by checking the log-file and correct the error. If it succeeds run bibtex. Check the blg if it did succeed. If yes run pdflatex again.
– Ulrike Fischer
Mar 15 at 14:02












Ok, it now runs with just pdflatex, although it didn't before strangly. It does not run with bibtex. This is the log file: 2018-03-15 14:09:35,734Z INFO miktex-bibtex - starting with command line: "C:MiKTeK Program Filesmiktexbinx64miktex-bibtex.exe" warwickthesis 2018-03-15 14:09:35,805Z INFO miktex-bibtex - finishing with exit code 1 This error doesn't tell me any more though? It does not seem to like my library, however it is the same one I used on a different computer which worked fine?
– Claire Thring
Mar 15 at 14:11






Ok, it now runs with just pdflatex, although it didn't before strangly. It does not run with bibtex. This is the log file: 2018-03-15 14:09:35,734Z INFO miktex-bibtex - starting with command line: "C:MiKTeK Program Filesmiktexbinx64miktex-bibtex.exe" warwickthesis 2018-03-15 14:09:35,805Z INFO miktex-bibtex - finishing with exit code 1 This error doesn't tell me any more though? It does not seem to like my library, however it is the same one I used on a different computer which worked fine?
– Claire Thring
Mar 15 at 14:11






1




1




Edit the question to add the info.
– Ulrike Fischer
Mar 15 at 16:00




Edit the question to add the info.
– Ulrike Fischer
Mar 15 at 16:00










2 Answers
2






active

oldest

votes

















up vote
0
down vote













I've had a similar issue since I have started compiling my thesis on my laptop rather than the machine at work and I am guessing they are different versions of Miktex or TexWorks. This error seems to occur when a reference is in the the bibtex file twice.



However if you have citation names that are separated by an underscore it doesn't read past the underscore. My bibtex file is created automatically by Zotero using the format "author_firstwordtitle_year", i.e. jones_paper_2018 or jones_anotherpaper_2018. When you compile it, it reads these two references as the being the same and hence the error occurs. I've just about finished my thesis so have manually added a number at the beginning to give me 1jones_paper_2018 and 2jones_anotherpaper_2018 and it works. This would however be a pain if I was still working on it and updating my bibtex file regularly as I would have to keep manually updating the automatically generated list.



I have no idea what problem the update that I assume has been made to MikTex/TexWorks has solved as it just seems to me it has made the whole thing worse.






share|improve this answer




























    up vote
    0
    down vote













    I also encounter a similar problem. I.E. MiKTeX compiler driver did not succeed.



    The problem is that I give the LaTeX file a name that with spaces. When I deleted all the spaces in the file name, then everything was fine.






    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "85"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f420304%2fsorry-but-miktex-compiler-driver-did-not-succeed-fatal-texify-bibtex-faile%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      0
      down vote













      I've had a similar issue since I have started compiling my thesis on my laptop rather than the machine at work and I am guessing they are different versions of Miktex or TexWorks. This error seems to occur when a reference is in the the bibtex file twice.



      However if you have citation names that are separated by an underscore it doesn't read past the underscore. My bibtex file is created automatically by Zotero using the format "author_firstwordtitle_year", i.e. jones_paper_2018 or jones_anotherpaper_2018. When you compile it, it reads these two references as the being the same and hence the error occurs. I've just about finished my thesis so have manually added a number at the beginning to give me 1jones_paper_2018 and 2jones_anotherpaper_2018 and it works. This would however be a pain if I was still working on it and updating my bibtex file regularly as I would have to keep manually updating the automatically generated list.



      I have no idea what problem the update that I assume has been made to MikTex/TexWorks has solved as it just seems to me it has made the whole thing worse.






      share|improve this answer

























        up vote
        0
        down vote













        I've had a similar issue since I have started compiling my thesis on my laptop rather than the machine at work and I am guessing they are different versions of Miktex or TexWorks. This error seems to occur when a reference is in the the bibtex file twice.



        However if you have citation names that are separated by an underscore it doesn't read past the underscore. My bibtex file is created automatically by Zotero using the format "author_firstwordtitle_year", i.e. jones_paper_2018 or jones_anotherpaper_2018. When you compile it, it reads these two references as the being the same and hence the error occurs. I've just about finished my thesis so have manually added a number at the beginning to give me 1jones_paper_2018 and 2jones_anotherpaper_2018 and it works. This would however be a pain if I was still working on it and updating my bibtex file regularly as I would have to keep manually updating the automatically generated list.



        I have no idea what problem the update that I assume has been made to MikTex/TexWorks has solved as it just seems to me it has made the whole thing worse.






        share|improve this answer























          up vote
          0
          down vote










          up vote
          0
          down vote









          I've had a similar issue since I have started compiling my thesis on my laptop rather than the machine at work and I am guessing they are different versions of Miktex or TexWorks. This error seems to occur when a reference is in the the bibtex file twice.



          However if you have citation names that are separated by an underscore it doesn't read past the underscore. My bibtex file is created automatically by Zotero using the format "author_firstwordtitle_year", i.e. jones_paper_2018 or jones_anotherpaper_2018. When you compile it, it reads these two references as the being the same and hence the error occurs. I've just about finished my thesis so have manually added a number at the beginning to give me 1jones_paper_2018 and 2jones_anotherpaper_2018 and it works. This would however be a pain if I was still working on it and updating my bibtex file regularly as I would have to keep manually updating the automatically generated list.



          I have no idea what problem the update that I assume has been made to MikTex/TexWorks has solved as it just seems to me it has made the whole thing worse.






          share|improve this answer












          I've had a similar issue since I have started compiling my thesis on my laptop rather than the machine at work and I am guessing they are different versions of Miktex or TexWorks. This error seems to occur when a reference is in the the bibtex file twice.



          However if you have citation names that are separated by an underscore it doesn't read past the underscore. My bibtex file is created automatically by Zotero using the format "author_firstwordtitle_year", i.e. jones_paper_2018 or jones_anotherpaper_2018. When you compile it, it reads these two references as the being the same and hence the error occurs. I've just about finished my thesis so have manually added a number at the beginning to give me 1jones_paper_2018 and 2jones_anotherpaper_2018 and it works. This would however be a pain if I was still working on it and updating my bibtex file regularly as I would have to keep manually updating the automatically generated list.



          I have no idea what problem the update that I assume has been made to MikTex/TexWorks has solved as it just seems to me it has made the whole thing worse.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Apr 7 at 18:14









          James

          1




          1






















              up vote
              0
              down vote













              I also encounter a similar problem. I.E. MiKTeX compiler driver did not succeed.



              The problem is that I give the LaTeX file a name that with spaces. When I deleted all the spaces in the file name, then everything was fine.






              share|improve this answer



























                up vote
                0
                down vote













                I also encounter a similar problem. I.E. MiKTeX compiler driver did not succeed.



                The problem is that I give the LaTeX file a name that with spaces. When I deleted all the spaces in the file name, then everything was fine.






                share|improve this answer

























                  up vote
                  0
                  down vote










                  up vote
                  0
                  down vote









                  I also encounter a similar problem. I.E. MiKTeX compiler driver did not succeed.



                  The problem is that I give the LaTeX file a name that with spaces. When I deleted all the spaces in the file name, then everything was fine.






                  share|improve this answer














                  I also encounter a similar problem. I.E. MiKTeX compiler driver did not succeed.



                  The problem is that I give the LaTeX file a name that with spaces. When I deleted all the spaces in the file name, then everything was fine.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Oct 9 at 4:59









                  CarLaTeX

                  28.3k446122




                  28.3k446122










                  answered Oct 9 at 2:36









                  Yilong Xie

                  1




                  1






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to TeX - LaTeX Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f420304%2fsorry-but-miktex-compiler-driver-did-not-succeed-fatal-texify-bibtex-faile%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Accessing regular linux commands in Huawei's Dopra Linux

                      Can't connect RFCOMM socket: Host is down

                      Kernel panic - not syncing: Fatal Exception in Interrupt