Troubles with <cfexecute>

[CF5/Win2k] I'm trying to run Verity Spider (vspider.exe) commands using <cfexecute>. Some of the commands stop mid-way through, and the process dies. I am using batch files to keep the <cfexecute> as uncomplicated as possible, and I'm also using long timeouts, as well as output files. The same batch files work like a champ from the command line itself, but as I stated, they hang early in the process, and then the process dies. I've tried the commands using cfx_exec and cfx_execute with the same results, which led me to believe it was somehow a permissions issue. We then changed the CF Application service's account to use local admin, and that's having the same problems. It just seems that no matter how I try to get CF to execute this batch file, it just dies under the influence of CF itself. So... Any idea why this is happening? Also, does anyone know a good way to execute a batch file in some other creative way from a browser, or some other way to insulate the execution of the command from whatever's causing it to fail? Thanks, Jamie

>[CF5/Win2k] ----- Excess quoted text cut - see Original Post for more ----- <edited for clarity> >The same batch files work like a champ from the command line itself, >but as I stated, <cfexecute> commands hang early in the process, and >then the process dies. </edited for clarity> ----- Excess quoted text cut - see Original Post for more -----

Jamie, We're in the process of developing a K2-based search engine populated by vpsider, and I've ran into similar problems as well. While I haven't tested it enough to say so with any certainity, I have noticed that the vspider process hanging does seem to be roughly coincident with me opening the specified output text file while vspider is still running. I'm planning to do some more testing myself tomorrow, but I would suggest running it again via cfexecute, but then (if you haven't taken this precaution already) not opening the output file until the last modified time stamp hasn't changed for several minutes. Pete ----- Excess quoted text cut - see Original Post for more -----

Hi Pete, The output file thought crossed my mind, too, but I don't think that's it. Check out your processes right when you run your command, and you'll see the vspider process die an early death (that is, if we're in the same boat). (My problem is with early vspider process termination, rather than a real "hang.") If you find anything out, please let me know, and I'll do the same. Corrections to my original post, FWIW: It turns out I haven't tested the command using cfx_execute yet (having problems calling it), so I've really only tested using cfx_exec and cfexecute. Also, it also turns out that we temporarily changed the CF Application service to use a *domain* admin account, as opposed to a local admin account. Thanks, Jamie ----- Excess quoted text cut - see Original Post for more -----