Exit Code 128 is a generic OS error that means the process couldn't be created. Most likely in your case it refers to "cmd.exe" itself. Possible causes include path changes, DLL corruption, memory problems (e.g., out of process space), etc.
Wherever I go, I almost always create a little form that to let me run server-side commands via an active link using "@@:" notation. If I can run it manually through the form, I can be reasonably sure that it'll run on the server in a filter. Also, it lets me see the whole error, which might not have made it into the filter log. Tim Widowfield [EMAIL PROTECTED] http://www.widowfield.com ----- Original Message ---- From: Scott Parrish <[EMAIL PROTECTED]> To: [email protected] Sent: Wednesday, December 13, 2006 9:40:54 AM Subject: [ARSLIST] $PROCESS$ Issue have a filter set fields $PROCESS$ that copies a file from one directory to another and renames the file. This process has always worked in the past, but after a server restart, I am now getting an error when the filter executes. The filter log file shows Exit Code: 128. This is an exit code that I have never seen before. The $PROCESS$ command looks like this: $PROCESS$ cmd copy “e:\program files\ar system\arserver\db\Notify80.arn” “e:\program files\ar system\copyfields.itp” As I said, I have never had a problem with this process in the past, so I have to believe that there is no problem with the syntax (unless someone made some sort of change on the server that I don’t know about that could affect this syntax). ARS 6.3 Windows Server 2003 MS Sql 2000 Scott Parrish IT Prophets, LLC (770) 653-5203 http://www.itprophets.com _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
