LateX error : I can't write on file 'Rapport.pdf'

  • Context: LaTeX 
  • Thread starter Thread starter DePaco
  • Start date Start date
  • Tags Tags
    Error File Latex
Click For Summary

Discussion Overview

The discussion revolves around an error encountered while compiling a LaTeX document, specifically the inability to write to the output file 'Rapport.pdf'. Participants explore various potential causes and solutions related to file access issues, including interactions with antivirus software and file permissions.

Discussion Character

  • Technical explanation
  • Debate/contested

Main Points Raised

  • One participant reports an error stating they cannot write to 'Rapport.pdf' and suggests closing the PDF file as a potential solution.
  • Another participant proposes moving the file away before compiling as a troubleshooting step.
  • A different participant mentions that a PDF viewer might be holding the file open and suggests terminating the viewer or clearing its list.
  • One participant identifies antivirus software as the cause of the issue, stating that deactivating it resolves the problem.
  • Another participant expresses concern about deactivating antivirus software for compilation, suggesting alternative methods like using a different directory or USB stick.
  • One participant confirms that they resolved the issue by changing the directory permissions and acknowledges the risks of deactivating antivirus protections.
  • Another participant reiterates the importance of not excluding temp or user home directories from antivirus scanning to avoid access violations.

Areas of Agreement / Disagreement

Participants express differing views on the appropriateness of deactivating antivirus software, with some agreeing it is not a good solution while others suggest it may be necessary in certain contexts. The discussion remains unresolved regarding the best practices for handling file access issues in relation to antivirus software.

Contextual Notes

Participants mention various potential limitations, including file permissions, antivirus settings, and the possibility of other processes interfering with file access. These factors contribute to the complexity of the issue without reaching a definitive resolution.

DePaco
Messages
14
Reaction score
2
Hello,
I am trying to compile my lateX document but errors appear:

! I can't write on file 'Rapport.pdf'.
Please type another file name for output
! Emergency stop
l.55 ... obj {<< /pgfprgb (/Pattern /DeviceRGB] >>
! Fatal error occurred, no output pdf file produced!
Transcript written on Rapport.log

One of the solution is to close pdf file before compilation. I have already tried it and I have the same errors.

My script is:

\documentclass[12pt,twoside]{report}
\usepackage[french]{babel}
\usepackage[T1]{fontenc}
\usepackage{float}
\usepackage{graphicx}
\usepackage[latin1]{inputenc}
\usepackage[french]{minitoc}
\usepackage{array}
\usepackage{amsmath}
\usepackage{multirow}
\usepackage {hyperref}
\usepackage{geometry}
\usepackage{subfigure}
\usepackage{amssymb}
\usepackage[square]{natbib}
%\usepackage{bibtopic}
\usepackage{pifont}
\usepackage{soul}
\usepackage{chemist}
\usepackage{tikz}
\usepackage{fancyhdr}
\usepackage{fancybox}
\usepackage{nsheader}
\usepackage{setspace}
\hypersetup{%
colorlinks= true,
linkcolor = black,
anchorcolor = black,
citecolor = black,
filecolor = black,
urlcolor = black,
breaklinks=false,
pdfpagemode= UseOutlines,
pdfstartview={XYZ 0 1000 1.0}
}
\makeatletter
\newif\if@openbib
\makeatother

\geometry{hscale=0.78,vscale=0.8,centering}
\pagestyle{fancy}
%\pagestyle{myheadings}
\setcounter{tocdepth}{5}
\setcounter{secnumdepth}{5}
\setcounter{minitocdepth}{5}
\setcounter{secnumdepth}{5}
%DEFINITION DES VARIABLES
\def\bel{\textit{Bel}}
\def\pl{\textit{Pl}}\def\fdg{\text{$^{\text{18}}\text{F-FDG}$}}
\def\flu{\(^{\text{18}}\)F}
\def\flt{\(^{18}FLT\)}
\def\fmiso{\(^{18}FMISO\)}
\def\iod{\(^{131}I\)}
\def\tec{\(^{99m}Tc\)}


\begin{document}

\dominitoc

\makeatletter

\setlength{\parskip}{2pt}

\renewcommand{\tablename}{Tableau}
\renewcommand{\figurename}{Figure}
\newcommand{\tab}{\ \ \ \ }
\renewcommand{\baselinestretch}{1.2}
\newcommand{\etal}{\textsl{et al.} }

\renewcommand{\listfigurename}{Liste des Figures}
\renewcommand{\listtablename}{Liste des Tableaux}

\widowpenalty=10000 % empeche au maximum la coupure avant la derniere ligne
\clubpenalty=10000 % empeche au maximum la coupure apres la premiere ligne
\raggedbottom % empeche l'etirement des ressorts verticaux

\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\z@}%
{0.2cm \@plus 0ex \@minus .0ex}%
{0.0ex \@plus .0ex}
{\reset@font\texorpdfstring\normalsize\textbf\bfseries}}

\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
{0.2cm \@plus 0.ex \@minus .0ex}%
{0.0ex \@plus .0ex}
{\reset@font\texorpdfstring\normalsize\textbf\bfseries}}
\makeatother
\pagestyle{fancy}
\fancyhf{}

\renewcommand{\chaptermark}[1]{\markboth{{\chaptername~\thechapter{}.\quad #1}}{}}
\renewcommand{\sectionmark}[1]{\markright{\thesection{}.\quad #1}}
\lhead[\thepage]{\rightmark}
\rhead[\leftmark]{\thepage}
\renewcommand{\headrulewidth}{1pt}
\renewcommand{\headsep}{20pt}
\renewcommand{\chaptermark}[1]{\markboth{{#1}}{}}
\addtocontents{toc}{\protect\chaptermark{Table des matières}}
\renewcommand{\sectionmark}[1]{\markright{{#1}}{}}
\addtocontents{toc}{\protect\sectionmark{Table des matières}}

\begin{spacing}{1.5}
%\pagestyle{plain}

% \input{chapitres/pgde.tex}
\input{chapitres/Pgarde.tex}
% \date\today
%\maketitle
% \input{chapitres/Thankly.tex}
\end{spacing}

\input{chapitres/Nodule.tex}



%BIBLIOGRAPHIE..
\newpage
~\newpage
\bibliographystyle{abbrvnat-fr}
\markboth{Bibliographie}{Bibliographie}\addcontentsline{toc}{part}{Bibliographie}
\bibliography{bibliographie}



\end{document}



Thank you for your help.
 
Physics news on Phys.org
What happens if you move the file away before you compile the code?
 
There may be another process holding the file open like a pdf viewer maybe on a secondary desktop (if you're using multiple desktops).

Sometimes when I've run into this kind of problem, I will terminate the pdf viewer via the kill command (linux, MacOSX) or via the Windows Task Manager and if that doesn't work, I will open a completely unrelated pdf file to clear the old one from the pdf viewer's list.

Other possibilities are the file rapport.pdf is read protected or in a read protected directory or in a directory not owned by you...
 
Hello,
I solve my problem. It is because of anti-virus. If I compile the project during anti-virus starting, I obtain this error. To solve it, I am oblige to deactivate it.
Think you for your answer.
 
That sounds real bad. I wouldn't deactivate antivirus to compile anything.
 
  • Like
Likes   Reactions: FactChecker
I use only one computer. Exactly file rapport.pdf is in a read protected directory. I have deactive this option so it ok.
Thank you for your contribution.
 
But still you open yourself up to a whole slew of attacks by doing that. Why not build it in another directory or even on a USB stick to avoid turning off the anti-virus.

Also you could consider getting another anti-virus program if you think that's the real issue.
 
Anti-virus is active but I would like to deactive directory protected. I am agree It's not a good solution. Now I use USB stick and it's ok.
Thank you.
 
  • Like
Likes   Reactions: stoomart and jedishrfu
DePaco said:
Anti-virus is active but I would like to deactive directory protected. I am agree It's not a good solution. Now I use USB stick and it's ok.
Thank you.
Excluding folders from realtime antivirus scanning is common for heavy I/O files like those for databases and VMs. It sounds like the AV was locking the file for inspection while still being written, causing an access violation. The important thing is to never exclude temp or user home directories.
 

Similar threads

  • · Replies 2 ·
Replies
2
Views
3K
  • · Replies 4 ·
Replies
4
Views
3K