This could be just the nature of Batch files, something causing munge to be unable to do something it can do when directly typed….
I am running munge in a batch file with a simple find and replace of changing “/” to “.” I have used munge successfully in batches before, and when I type the command:
“munge munge.txt today.txt” the munge runs successfully. However when my line is put into a batch file, the munge fails with error:
Munge: unable to create symbol table
All of the files for the munge are in the working directory of the batch. The same problem is occurring on two NT workstations one SP5 and the other SP6A
I have read the article on munge and comments at www.winntmag.com, 2 techrepub references, and some useless crap atTechnet with no luck.
can someone please tell me the cause of the error, or the solution, or maybe why the nature of a batch file would change munge’s performance parameters and what I can try?
points and kudos for anything that directly leadsme to the fix