Why am I getting InDesign error code 29446?

Question

Hello,
I am using InDesign Server CS5 and on two file I keep getting error code #29446 when I try to use them.
this is the script that I get error #29446:
var strXMLFile = 'D:\\mssb\\incoming\\34695.xml';
var strINDDFile = '\\\\167.246.44.76\\MSSB\\templates\\RET010\\6256950-MSSB-RET010-BW-6 x9.indt';
var strJPGFile = 'D:\\mssb\\outgoing\\34695.jpg';
var strPDFFile = 'D:\\mssb\\outgoing\\34695.pdf';
var myFile = new File(strINDDFile);
var myDocument = app.open(myFile);
var myXMLFile = new File(strXMLFile);
var myXmlImport = myDocument.xmlImportPreferences;
myXmlImport.importStyle = 1481469289;
myXmlImport.ignoreUnmatchedIncoming = true;
myXmlImport.importTextIntoTables = true;
myXmlImport.removeUnmatchedExisting = true;
myDocument.importXML(myXMLFile);
myDocument.exportFile(ExportFormat.jpg, new File(strJPGFile));
myDocument.exportFile(ExportFormat.pdfType, new File(strPDFFile));
myDocument.close();
I have approximately 200 other InDesign documents that use this script and for the exception of two they all work. I can confirm that this file does exist, it is not being used by any other application (the only application that can access it and use it on that machine is InDesign Server) and the permissions are the same as all the other InDesign files that are on the box.
What else could generate this error?
-fw

Answer 1

The error number is for the internal C++ constant named "kFileDoesNotExistError".
You should be able to single step even on InDesign Server using ExtendScript Toolkit.
Even without, a bit of log file output should show you the exact problem statement.
When you wrap it with try / catch, you may (or not) find more information in the exception object.
Iterate over all properties using something like code below.
Of course, $.writeln only makes sense with an attached ESTK debugger, otherwise you'll just waste CPU cycles.
try {
} catch( ex ) {
  for( n in ex ) { $.writeln(ex[n]); }
Note that the problem might not be in the indd file - e.g. have you checked all image href attributes within the XML?
For digging deeper:
On a Mac I'd use dtrace or Instruments to watch file system calls for error codes.
Windows should have similar tools, for example this one sounds promising (I never used it):
http://technet.microsoft.com/en-us/sysinternals/bb896645
Dirk