Force imagex to dump a verbose error log?

[pete]

I have a scheduled task that runs imagex /capture against a series of directory trees and dumps them to a remote location.

 

This worked fine until yesterday when it breaks on 2 of the 11 directory trees with "parameter is incorrect". Files in the trees aren't open or being locked by anything and this script has worked for the best part of three months without changes..

 

I believe it's caused by an illegal character in a filename or a permission issue somewhere in the directory tree, but as they're quite massive, wading through them (or imagex-ing at a secondary level in the trees to narrow it down) would take a while.

 

Is there a way to get imagex to tell me where it's having the issue?

Edited March 12, 2009 by pete