Fix the error ‘I can’t write on file `document.pdf’

output

I attach the document code. I don't understand what's wrong. Before that, everything worked, but after updating the MiKTeX packages, this error appeared. I work in the Texstudio program.

\documentclass[14pt]{ncc}
\usepackage[a4paper, left=2cm, right=2cm, top=2cm, bottom=2cm, headsep=0.7cm, footskip=1cm]{geometry}
\usepackage[T2A]{fontenc} % Поддержка русских букв
\usepackage[utf8]{inputenc} % Кодировка utf8
\usepackage[english,russian]{babel} % Языки: русский, английский
\usepackage{fontspec} % Настройка для подключения
\setmainfont{Times New Roman} % шрифта Times New Roman
\usepackage{indentfirst} % Красная строка
\usepackage{xcolor} % Пакет для работы с цветами
\usepackage{hyperref} % Гиперссылки
%\usepackage{amsmath,amssymb,amsthm,amsfonts,amscd}
\usepackage{amsmath,amssymb}
\usepackage{esdiff}
\usepackage{graphicx}
\pagestyle{plain} % Номера страниц ставятся снизу и по центру
\usepackage{enumitem}
\setlist{nolistsep, labelsep=0.2cm, leftmargin=0cm} % Отступы номеров
% Настройка некоторых параметров ссылок
\hypersetup{
    colorlinks = true, % Ссылки цветные? - Да
    linkcolor = {blue!50!black}, % Цвет внутренних ссылок
    citecolor = {red!75!black}, % Цвет ссылок на библиографию
    urlcolor = red, % Цвет ссылок на внешние (Интернет) ресурсы
}

\DeclareSymbolFont{lsymb}{U}{euex}{m}{n}
\DeclareMathSymbol{\intop}{\mathop}{lsymb}{"52}
\DeclareMathSymbol{\ointop}{\mathop}{lsymb}{"48}
\DeclareMathSymbol{\smallint}{\mathop}{lsymb}{"52}

\begin{document}
    Текст
\end{document}

Best Answer

The cause of the error was Avast antivirus. He perceived the LuaLaTeX compiler as malicious. When the process started lualatex.exe, the antivirus issued a message in which I clicked the "Allow application" button, and the error disappeared.

Related Solutions

[Tex/LaTex] Understanding the Log file

Here are some elements of a .log file:

The .log file starts out by giving some information about the compiler that you are running. For example, running latex or pdflatex the output is
```
This is pdfTeX, Version 3.1415926-2.3-1.40.12 (Web2C 2011)
```
while running xelatex would output
```
This is XeTeX, Version 3.1415926-2.3-0.9997.5 (Web2C 2011)
```
Every file (including the document class .cls and style .sty files) that is loaded starts with an opening "(" and the file name. When the file has finished loading, a closing ")". All messages that happen during that file are written between those parenthesis. Sometimes this includes the file version or a short description of the file, as written by the package author).
```
(./test.tex (./hello.tex This is a message from hello.tex) [1] )
```
The page numbers are written in [ ] square brackets.
LaTeX issues "bad box" warnings whenever you have something contained within a box (the general TeX layout structure) that does not fit within it. Here's a small working example
```
\documentclass{article}
\begin{document}
Thisisaverylonglinethatdoesnotbreakproperlyattheendofthelineandcausesanoverfulhbox
\end{document}
```
that produces
```
Overfull \hbox (46.52866pt too wide) in paragraph at lines 3--4
[]\OT1/cmr/m/n/10 Thisisaverylonglinethatdoesnotbreakproperlyattheendofthelinea
ndcausesanoverfulhbox 
 []
```
in your .log file. This means that the contents of the box (in this case a box of width \linewidth) was exceeded by 46.52866pt at lines 3-4 in your code. An actual output code segment is also visible, with the fonts loaded to typeset that "bad" part of your document (OT1/cmr/m/n/10). These "bad boxes" are tallied and given at the very end of your compile (although this does not form part of the actual .log file):
```
LaTeX-Result: 0 Error(s), 0 Warning(s), 1 Bad Box(es), 1 Page(s)
```
You may sometimes get warnings such as
```
LaTeX Warning: Reference myref on page 1 undefined on input line 6.
```
This means that you have used \ref or one of its relatives without having the appropriate \label. In this case, you will also get
```
LaTeX Warning: There were undefined references.
```
at the end of your log file.
Similarly, if you define the same \label in multiple places, then you will get
```
LaTeX Warning: Label `mypage' multiply defined.
```
which will lead to
```
LaTeX Warning: There were multiply-defined labels.
```
at the end of your log file.

Sometimes fonts cannot be found. Either a font shape (for example slanted) or some requested font size is not available. Then you'll get a message like:

LaTeX Font Warning: Font shape `OT1/cmr/m/bx' undefined
(Font)              using `OT1/cmr/m/n' instead on input line 3.

LaTeX Font Warning: Font shape `OT1/cmr/m/n' in size <5.42497> not available
(Font)              size <5> substituted on input line 72.

Many of the aforementioned information is obtained by an issue of \typeout{<stuff>} which outputs <stuff> to the terminal window (and subsequently makes its way into the .log file). Warnings and errors, also included in the .log file, arise from an issue of \<cmd>Warning or \<cmd>Error where <cmd> either refers to Class or Package.

To some extent it is possible to have control over the information output to the .log file by using the silence package. It provides a means to filter or activate warnings, errors or other messages from packages.

[Tex/LaTex] I can’t write on file ‘foo.aux’

@DavidCarlisle proposed a solution in comment of the OP. It seems to be sufficient to create a subdirectory _out/text for the compilation to succeed.

Best Answer

Related Solutions

[Tex/LaTex] Understanding the Log file

[Tex/LaTex] I can’t write on file ‘foo.aux’

Related Question