[MiKTeX] "The input file could not be found"

[Alexandre Borovik]

Dear Friends, I could not find the answer to my problem in FAQs.

My MiKTeX (Windows 10, 64 bit) suddenly lost ability to see input file.
Reinstallation did not help. Could you please help?

Alexandre

<<<ERROR MESSAGE:

Command Line: texify.exe --pdf
--tex-option=--interaction=errorstopmode --tex-option=--synctex=-1
"C:\Users\AB\Documents\Current\10212
2016-17\10212_Slides_2016-17_Weeks_1-4.tex"
Startup Folder: C:\Users\AB\Documents\Current\10212 2016-17


Sorry, but texify did not succeed for the following reason:

The input file could not be found.

The log file hopefully contains the information to get MiKTeX going again:

C:/Users/AB/AppData/Local/MiKTeX/2.9/miktex/log/texify.log

You may want to visit the MiKTeX project page, if you need help.

_____________________________________________________________________

PDFTeXify Compilation Report (Pages: 0)

Errors: 0 Warnings: 0 Bad Boxes: 0
_____________________________________________________________________

END>>>


<<< CONTENT OF C:/Users/AB/AppData/Local/MiKTeX/2.9/miktex/log/texify.log:

2017-01-31 07:22:58,646Z INFO texify - running 'initexmf --quiet
--update-fndb' to refresh the file name database
2017-01-31 07:23:03,322Z FATAL texify - The input file could not be found.
2017-01-31 07:23:48,878Z FATAL texify - The input file could not be found.
2017-01-31 07:27:21,784Z FATAL texify - The input file could not be found.
2017-01-31 08:54:42,715Z FATAL texify - The input file could not be found.

END>>>

[Ulrike Fischer]

Post by Alexandre Borovik
My MiKTeX (Windows 10, 64 bit) suddenly lost ability to see input file.
Reinstallation did not help. Could you please help?
Alexandre
Command Line: texify.exe --pdf
--tex-option=--interaction=errorstopmode --tex-option=--synctex=-1
"C:\Users\AB\Documents\Current\10212
2016-17\10212_Slides_2016-17_Weeks_1-4.tex"
Startup Folder: C:\Users\AB\Documents\Current\10212 2016-17
The input file could not be found.

I can't reproduce the problem on windows 10 + miktex 32bit. But

- don't use spaces in folder/file names
- don't call texify (and other applications) with absolute files
names.
- don't use texify at all - imho it is a pain. It fails constantly
and its error messages are bad. If you want a tool for an automatic
compilation use latexmk or arara.

[Alexandre Borovik]

Thanks. I figure out the issue: it was in WinEdt 10 editor. Alexandre

Post by Ulrike Fischer

Post by Alexandre Borovik
My MiKTeX (Windows 10, 64 bit) suddenly lost ability to see input file.
Reinstallation did not help. Could you please help?
Alexandre
Command Line: texify.exe --pdf
--tex-option=--interaction=errorstopmode --tex-option=--synctex=-1
"C:\Users\AB\Documents\Current\10212
2016-17\10212_Slides_2016-17_Weeks_1-4.tex"
Startup Folder: C:\Users\AB\Documents\Current\10212 2016-17
The input file could not be found.

I can't reproduce the problem on windows 10 + miktex 32bit. But
- don't use spaces in folder/file names
- don't call texify (and other applications) with absolute files
names.
- don't use texify at all - imho it is a pain. It fails constantly
and its error messages are bad. If you want a tool for an automatic
compilation use latexmk or arara.

[Denis Navas]

I use windows 7 and recently lost the capacity to execute *.cmd and *.bat
files, that must be run manually with administrator privileges. Since I don't
know which windows parameter should be changed I can't solve my problem.