I recently run into a problem where on my laptop i can compile a tex file using eps images but on my pc it does not work instead if i try to compile Libre Office is opening and showing the EPS file.
Running Texstudio with miktex on windows 10
This is the log
Package epstopdf Info: Source file: <Messungen/../../TestflugAuswertung/PosVelA
ccFiltered.eps>
(epstopdf) date: 2019-05-04 11:48:27
(epstopdf) size: 661425 bytes
(epstopdf) Output file: <Messungen/../../TestflugAuswertung/PosVelA
ccFiltered-eps-converted-to.pdf>
(epstopdf) Command: <epstopdf --outfile=Messungen/../../TestflugAus
wertung/PosVelAccFiltered-eps-converted-to.pdf Messungen/../../TestflugAuswertu
ng/PosVelAccFiltered.eps>
(epstopdf) \includegraphics on input line 13.
runsystem(epstopdf --outfile=Messungen/../../TestflugAuswertung/PosVelAccFilter
ed-eps-converted-to.pdf Messungen/../../TestflugAuswertung/PosVelAccFiltered.ep
s)...executed (allowed).
Package epstopdf Info: Result file: <Messungen/../../TestflugAuswertung/PosVelA
ccFiltered-eps-converted-to.pdf>.
! Package pdftex.def Error: File `Messungen/../../TestflugAuswertung/PosVelAccF
iltered-eps-converted-to.pdf' not found: using draft setting.
Best Answer
There are many reasons to get the dreaded (especially with TeXstudio)
You do not show any related warnings such as
Package epstopdf Warning: Shell escape feature is not enabled.
so I guess that is not the issue as in this case.NOTE most recent invocations of epstopdf on a standard TexLive do not need -shell-escape however depending on configuration I have sometimes found a need to add and remove it within some mixed MiKTeX configurations.
To ensure it is not a rogue file or "relative" location test your run with .eps in the same folder as .tex (avoid the use of relative folder/../../folder/ whilst testing)
For example we have no idea what /../../ represent they could include spaces etc.
Consider are paths constructed in "odd" fashion or have unusual characteristics (look for spaces Under_scores hy-phens "foreign" characters) many work under everyday circumstances but can misbehave when they are handed from shell application to application. Ensure test files are all lowercase.ext not CamelCase.EPS many work 99%\bUt- nOt_aLl/=\10o^ understandable? For an epstopdf example where simply a space was the culprit see
A common problem with epstopdf (and others) is it does not behave well with alien drives (do not use drop box or other server folders) If using
\\server\folder
ensure it is "mapped" to say s:\ or any other natural drive and use that. Avoid\graphicspath{{\\fileserver\TeX files}}
seeEpstopdf is in my experience "fragile" that is it may work on one run then due to poor editor configuration be blocked from succeeding on the next run, again this may be more common in some editors than others and the best test for this is to clear all auxiliary files and run outside the editor using the command line. In windows run
epstopdf --version
on its own and check for error messages. Then in the .EPS directory tryepstopdf --outfile=PosVelAccFiltered-eps-converted-to.pdf PosVelAccFiltered.eps
to see if the file conversion works to produce a pdf.