I recently changed to backend=biber
after some problems with encoding in bibtex8
( Biblatex encoding ). Everything seemed to work fine until I added some references and updated the bibliography file. The new references remained undefined. I removed all "additional" files (like .aux
etc.) from the project folder and ran LaTeX three times. All the references were now undefined and even no .blg
file is produced. So I had a look in the internet and found someone with a similar problem in a German LaTeX community. He used to work with Texmaker, and apparently the problem was that biber
was trying to get the information from .aux
file instead of .bcf
file. That user changed this manually in Texmaker and everything started working. However, another user suggested that within TeXnicCenter (which I am using) this doesn't need to be done as this is already indicated by %tm
. Now I am completely lost as to how to fix the problem.
Here is an MWE:
\documentclass{scrartcl}
\usepackage[british]{babel}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage[style=authoryear-comp, maxnames=1, doi=false, url=false, bibencoding=utf8, backend=biber]{biblatex}
\bibliography{litthesis}
\begin{document}
This is my text \parencite{Hong2006}
\newpage
\printbibliography
\end{document}
And here is the bibliography:
@article{Hong2006,
author = {Hong, Seungpyo and Leroueil, Pascale R and Janus, Elizabeth K and Peters, Jennifer L and Kober, Mary-Margaret and Islam, Mohammad T and Orr, Bradford G and Baker, James R and Holl, Mark M Banaszak},
title = {Interaction of polycationic polymers with supported lipid bilayers and cells: nanoscale hole formation and enhanced membrane permeability.},
journal = {Bioconjug Chem},
volume = {17},
number = {3},
pages = {728-734},
year = {2006}
}
Here is what's written in the .log
-file:
Package biblatex Info: Trying to load bibliographic data...
Package biblatex Info: ... file 'mwe.bbl' not found.
No file mwe.bbl.
Does anyone have an idea what's going wrong?
Best Answer
As we found out on golatex.de the problem is quite similar to the one in this question and this question.
biber
was complaining:The solution suggested by @egreg and @pmav99, resp., to the other questions -- namely deleting the
par-<some string>
directory in the temporary folder -- solved the issue here as well.