Command line hangs when user not logged in

[gkirsh]

I'm calling corecmd from a task scheduler job on Windows 2003. If the user that the task runs as is not logged in, the call to corecmd hangs. If the user is logged in, the job runs, and I see a svchost window pop up on the user's desktop. I'm using the -s option, and I tried -hide and -noicon. I'm using Pro V2.0 build 1505. Any ideas?
Thanks,
Gary

[tomh]

I recently had a similiar problem when the client is Windows Server 2008 though I did not have the problem on Windows Server 2003. I am running build 1637 of CoreFTP Lite Version 2.1

Anyway, a 2006 poster suggested the solution was to change the way CoreFTP stores configuration data so that it uses a file instead the default method which uses the registry. I checked the "Use default configuration file" box under View, Options, Data screen.

This helped but I also had to deal with the fact that coreftp.exe was using a different config file than corecmd.exe was for some reason. Basically, I made sure the settings were the same no matter which executable was being used. Another quirk was that corecmd.exe requires the "Run with highest privileges" box to be checked for the task -- or I could run the task with the admin account. Strangely, coreftp.exe did not have this issue. As near I can tell they both do the same thing so I guess I would recommend using coreftp over corecmd in this stuation.

Hope this helps someone

[MGByron]

I have tried to save files on the server and got each client to run the application but it says another instance of the program is running. Any more ideas anyone?
Works fine when one client is running the program.
Thanks
[url=http://cyberneticgroup.com/master.php]more...[/url]

[seanriddle]

Tom-

I upgraded from WS 2003 to WS 2008 to find out that corecmd no longer works correctly from a scheduled task. I have a program that shells out to corecmd to grab a directory listing with the -dira command, then the program processes that file list for new files, uses corecmd to download those, processes them, and uses corecmd to upload output files. Under WS 2008 the -dira command locks up. I've tried many different options in task scheduler and in CoreFTP, but nothing helps. If I run the program directly, everything works fine, but as soon as task scheduler tries to run it it locks up. I've tried running the task as myself, as administrator, with highest privileges, configured for Vista, configured for Windows 7, etc, with the same results.

I just tried your hint "use default configuration file", but that didn't help.

My understanding is that corecmd is just a blocking front-end for coreftp. When my scheduled task locks up, I see a corecmd process and a coreftp process. If I kill the coreftp process, the corecmd process exits. So I'm confused about coreftp using a different config file than corecmd. What did you do to make sure the settings were the same?

Note- I'm logged in the entire time.

Thanks-

Sean

[seanriddle]

Here's something odd- If my program calls corecmd with -s for silent and I run the program directly, it works fine. Here's the command and (redacted) log:

c:\progra~2\coreftp\corecmd -site x -s -dira abc dirdump.txt

Started on Monday February 14, 2011 at 02:03:AM
Resolving ftp.x.com...
Connect socket #828 to xxx.xx.xx.xxx, port 21...
220-###############################################################################
220-# message from ftp site #
220-###############################################################################
220-###############################################################################
USER xxxxxx
331 Please specify the password.
PASS **********
230 Login successful.
SYST
215 UNIX Type: L8
Keep alive off...
CWD abc
250 Directory successfully changed.
PASV
227 Entering Passive Mode (xxx,xx,xx,xxx,xxx,xx)
LIST
Connect socket #872 to xxx.xx.xx.xxx, port 40006...
150 Here comes the directory listing.
226 Directory send OK.
QUIT
221 Goodbye.

Now I've got the file directory in a text file ready for parsing.

But if I don't use -s, I get the following:

c:\progra~2\coreftp\corecmd -site x -dira abc dirdump.txt

Resolving ftp.x.com...
Connect socket #860 to xxx.xx.xx.xxx, port 21...
220-###############################################################################
220-# message from ftp site #
220-###############################################################################
220-###############################################################################
USER xxxxxx
331 Please specify the password.
PASS **********
230 Login successful.
SYST
215 UNIX Type: L8
Keep alive off...
CWD
550 Failed to change directory.
Error loading directory...

Note "CWD abc" in the working log and "CWD" in the non-working log. I specify abc in the -dira command, so why is it not there when I don't hide the window?

Sean