## LaTeX forum ⇒ WinEdt ⇒ Editor controlled Compilaton fails

Information and discussion about WinEdt, a commercial integrated LaTeX environment for Windows
raniya
Posts: 1
Joined: Mon Aug 12, 2013 9:21 am

### Editor controlled Compilaton fails

Dear team,

I have been using WinEdt smoothly. Yesterday it started giving error.

The only unusual things that happened meanwhile are

1. Ene document which was saved in folder "adaptive "was open in WinEdt.
2. I accidentally moved the folder "adaptive" to some other location.
3. Then when I run the .tex file which was already open, it gave error "File does not exist".
4. At that time only I realized the accidental moving of folder "adaptive" in which the text file was saved.
5. So I brought back the adaptive folder to the original location.
Then reopened the .tex file and compiled. But not working!

Error starting texify! See WinEdt's configuration wizard

I tried restoring my PC to two days back, but no use. Even the .tex file which was working fine months back and is in another folder is also not working now.

File: "C:\CTeX\WinEdt\TeX.log"
Date: Monday, August 12, 2013 at 10:25

Summary
===========

Your TeX installation appears to be fine. If you experience problems after an application has been launched this usually isn't a WinEdt-related matter. In such case, you should test a problematic application from the Command Prompt, consult the documentation that comes with your software, and try to locate the real source of your problem...
________________________________________________________

WinEdt 5 (v. 5.4) [Build: 20050701]

*** OS: Windows 5.1 [Build: 2600] Service Pack 2
*** Account Status: Power User+
*** Configuration: MiKTeX
*** TeX System: MiKTeX
*** User Profile: Disabled
*** %B: C:\CTeX\WinEdt
*** %b: C:\CTeX\WinEdt

*** WinEdt PATH:
"C:\CTeX\texmf\miktex\bin;
C:\CTeX\WinEdt;
C:\CTeX\LOCALT~1\ty\bin;
C:\CTeX\LOCALT~1\cct\bin;
C:\CTeX\texmf\miktex\bin;
C:\CTeX\gs\gs8.51\bin;
C:\CTeX\WinEdt;
C:\WINDOWS\system32;
C:\WINDOWS;
C:\WINDOWS\system32\WBEM;
C:\MATLAB701\bin\win32;
C:\Program Files\MiKTeX 2.9\miktex\bin\"

*** Windows PATH:
"C:\CTeX\WinEdt;
C:\CTeX\LOCALT~1\ty\bin;
C:\CTeX\LOCALT~1\cct\bin;
C:\CTeX\texmf\miktex\bin;
C:\CTeX\gs\gs8.51\bin;
C:\CTeX\WinEdt;
C:\WINDOWS\system32;
C:\WINDOWS;
C:\WINDOWS\system32\WBEM;
C:\MATLAB701\bin\win32;
C:\Program Files\MiKTeX 2.9\miktex\bin\"

________________________________________________________

Searching for Executables:
==========================

WinEdt will try to locate external executables based on the information stored in the variables that were imported from Windows Registry in its Startup Macro. If some components are not found follow the instructions. Some applications such as, for example, TtH or HHC are optional; you can ignore any messages about the "missing" accessories that you are not intending to use...

TeX-Root: OK
C:\CTeX\texmf
TeX-Bin: OK
C:\CTeX\texmf\miktex\bin

LaTeX-Help Folder: OK
C:\CTeX\texmf\doc\latex\help
LaTeX-Help: (latex2e.chm) OK
C:\CTeX\texmf\doc\latex\help\latex2e.chm

DVIView: OK (PATH yap.exe)
C:\CTeX\texmf\miktex\bin\yap.exe

TeX-Bin (TeX.exe): OK
C:\CTeX\texmf\miktex\bin\tex.exe
TeX-Bin (LaTeX.exe): OK
C:\CTeX\texmf\miktex\bin\latex.exe
TeX-Bin (AMSTeX.exe): OK
C:\CTeX\texmf\miktex\bin\amstex.exe
TeX-Bin (PDFTeX.exe): OK
C:\CTeX\texmf\miktex\bin\pdftex.exe
TeX-Bin (PDFLaTeX.exe): OK
C:\CTeX\texmf\miktex\bin\pdflatex.exe
TeX-Bin (BibTeX.exe): OK
C:\CTeX\texmf\miktex\bin\bibtex.exe
TeX-Bin (MakeIndex.exe): OK
C:\CTeX\texmf\miktex\bin\makeindex.exe
TeX-Bin (dvips.exe): OK
C:\CTeX\texmf\miktex\bin\dvips.exe
TeX-Bin (dvipdfm.exe): OK
C:\CTeX\texmf\miktex\bin\dvipdfm.exe

MiKTeX-Bin (TeXify.exe): OK
C:\CTeX\texmf\miktex\bin\texify.exe

****************************************************
TtH is an optional LaTeX to HTML convertor. If TtH is installed on your system you should modify the PATH to include its location (or else place "tth.exe" to TeX's Binary folder or somewhere else on WinEdt's PATH).

Tags:

Johannes_B
Site Moderator
Posts: 3602
Joined: Thu Nov 01, 2012 4:08 pm
raniya wrote:... you should test a problematic application from the Command Prompt, ...

That would have been my first suggestion, too.

Create a new document within Winedt and save the following code. Try to run it using winedt. Does it work? Does winedt give any errors?
\documentclass{article}\begin{document}test\end{document}

If this doesn't work, open a terminal/console (under windows, you can press [wind0ws + r] and enter cmd, confirm with enter), change to the folder with the tex-file and run
pdflatex NameOfYourFile

Alternatively, hold shift, right click the folder with the tex-file in it, and click "open command window here". Then run pdflatex.

Does it produce a pdf? If yes, the problem is within Winedt, if not, please post the log-file.

Best regards
Johannes
The smart way: Calm down and take a deep breath, read posts and provided links attentively, try to understand and ask if necessary.