Page 1 of 1

[DOTA069F][FATAL] error during DOS batch processing

Posted: Mon Oct 16, 2017 9:12 pm
by rdelong
I'm trying to figure out why I publish html5 output from Oxygen 19.1, but not from a stand-alone installation of DITA-OT-2.5.2.

When run from DOS batch file, I get the following error message:
[Codebox=]Error: Failed to run pipeline: [DOTA069F][FATAL] Input file 'file:/C:/_working/build/DITA-OT-2.5.2/docsrc/samples/sequence.ditamap' cannot be located or read. Ensure that file was specified properly and that you have permission to access it.[/Codebox]

My batch file is the following:

Code: Select all

C:\DITA-OT-2.5.2>dita -i docsrc\samples\sequence.ditamap -f html5 -o=out\en\sequence -propertyfile=docsrc\samples\properties\sequence-html5.properties -d -v -l=log\sequence_html5.txt
and the properties file contains the following:

Code: Select all

args.gen.task.lbl = YES
args.cssroot = C:\\_working\\build\\DITA-OT-2.5.2\\docsrc\\resources
args.css = dita-ot-doc.css
args.copycss = yes
args.csspath = css
nav-toc = full
args.xhtml.toc = toc
Research that I've done on [DOTA069F][FATAL] error revealed that perhaps the DTD could not be found during process. However, I opened the boomap in Oxygen and ran a validation check and it came back clean. I've no clue how to resolve this issue.

Re: [DOTA069F][FATAL] error during DOS batch processing

Posted: Wed Oct 18, 2017 2:53 pm
by Costin
Hi rdelong,

I also tested the same transformation from both oXygen XML Editor v19.1 with DITA OT set to use the external DITA 2.5.2 and by executing your command line in the batch file. The transformation ran and completed successfully both ways, so I could not reproduce the issue at our side.

You should try downloading a clean copy of the official DITA-OT 2.5.2, extract it and use it as it is (without any customization). You should also leave the properties file as is without modifying it first time.
Also, make sure that you have administrative rights (write permission more specific) in the location where you extract the DITA-OT.

Then retry running the command line. If it still does not work for you, you could send use the resulted log file for investigation.

Best Regards,
Costin