# tikzexternalize won't compile with windows 7 and texniccenter [closed]

i've got a problem compiling my latex document by using texniccenter, pdflatex and windows 7 (with windows xp everything is working fine..)

\usetikzlibrary{external}
\tikzexternalize[prefix=figures/]
\tikzexternalize


thats how i initiate tikzexternalize, the figures directory exists (its just a copy from my xp directory..)

i'm using pdflatex for 64bit with this command line arguments in texniccenter:

-max-print-line=120 -interaction=nonstopmode "%wm" -shell-escape BA.tex (as i do with windows xp)

i already tried to run texniccenter, pdflatex, .. with admin rights, but no change..

but now i get the follwing errors by using win7:

(C:\Auarbeitung\images/plots/synthOpeningVorne.tikz ===== 'mode=convert with system call': Invoking 'pdflatex -shell-escape -halt-on-error -interaction=batchmode -jobname " figures/BA-figure0" "\def\tikzexternalrealjob{BA}\input{BA}"' ======== runsystem(pdflatex -shell-escape -halt-on-error -interaction=batchmode -jobname "figures/BA-figure0" "\def\tikzexternalr ealjob{BA}\input{BA}")...executed.

! Package tikz Error: Sorry, the system call 'pdflatex -shell-escape -halt-on-error -interaction=batchmode -jobname "fig ures/BA-figure0" "\def\tikzexternalrealjob{BA}\input{BA}"' did NOT result in a usable output file 'figures/BA-figure0' ( expected one of .pdf:.jpg:.jpeg:.png:). Please verify that you have enabled system calls. For pdflatex, this is 'pdflate x -shell-escape'. Sometimes it is also named 'write 18' or something like that. Or maybe the command simply failed? Erro r messages can be found in 'figures/BA-figure0.log'. If you continue now, I'll try to typeset the picture.

See the tikz package documentation for explanation. Type H for immediate help. ...
l.295 \end{tikzpicture} This error message was generated by an \errmessage command, so I can't give any explicit help. Pretend that you're Hercule Poirot: Examine all clues, and deduce the truth by order and method.

i hope somebody can give me a hint how to fix this..

regards

-
I think the log files you posted are not complete: They don't end with an error or success message. Can you double check? – Jake Jul 2 '12 at 8:11
1. Don't try new code/methods (like externalizing) directly in your real document. Generate a small test document in a test folder. This avoids side effects, makes the log-file shorter and also allows you to show use the complete code you are using (and not only snippets). 2. If it doesn't work in TeXnicCenter compile on the command line. This helps to decide if the problem is with TeXnicCenter or with the document/pdflatex. 3. Admin rights are not necessary. – Ulrike Fischer Jul 2 '12 at 8:37
no. the logfiles are complete. thank you! i'll test it today. mmh, if i use this code: codepad.org/V7tPsshS everything is working fine... now it gets complicated :-( – Stefan Jul 4 '12 at 5:57
It's looking as though this might get closed as "too localised" at the moment. This is because based on your comment, it would appear that there's something particular to be tracked down before anyone can help you. If you can figure out what it is that is causing the problem but can't figure out the solution, please do ask a new question with that information. – Andrew Stacey Aug 20 '12 at 13:44

## closed as too localized by lockstep, Jake, Andrew Stacey, Joseph Wright♦Aug 20 '12 at 13:46

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, see the FAQ.