Scheduled task does not dot anything

Hello,

First of all DeltaCopy looks like to be the product I was looking for. It is well easy to use and easy to deploy (just unpack the zip !). Congratulation for the products. It would be nice to implement some others paremeters of the rsync program, but this is another story.

Now, I can get DeltaCopy working perfectly with the GUI (Run now) or by double clicking on the .dcp profile file, but when I schedule the task, it launch the program, seems to start rsync (can see them in the task manager), but nothing is copied. It looks like if the login process failed but I do not get any error and I can't see anything into the log file (deltac.log). Besides if I checked the destination folder on the rsync server, nothing is copied !

What can I do to solve this problem.

I am only using the client version under Windows XP Pro SP2
The rsync "server" is running on an Ubuntu Server 8.04

thanks in advance.

Hello, me again,

If I change into the task scheduler the run: field from "F:\Apps\DeltaCopy\myDeltaCopy.dcp" to "F:\Apps\DeltaCopy\DeltaC.exe myDeltaCopy.dcp" then it works. Why this ? Would it not better then to generate such task from within DeltaCopy ?

Yours,

Your second posting suggests that either:

1. The extension DCP is registered to a different program on your machine
2. It is NOT correctly registered. Check the following registry entry.

HKEY_CLASSES_ROOT\.dcp\shell\open\command

What is the value for this entry? It should be:

C:\Program Files\Synametrics Technologies\DeltaCopy\DeltaC.exe "%1"

Notice the double quotes around "%1". Having these double quotes ensures that the complete path is passed to DeltaCopy from the OS and not just the file name until the first space.

Regards.

I am having the same issue. If I double-click on the .dcp file it runs just fine. If it is called from Scheduled tasks then no dice. DeltaC.exe, ssh.exe, and rsync.exe are all running. It initially opens an ssh session to the server but never sends any data.

Ideas?

I have the same issue with cwRsync. It's seem that when the ssh.exe try to establish the connection, it hang if there is no open session. Since 3 month the work around is to connect through Terminal Server and disconnect my session, then everything run smooth.

Same problem here! I have a new setup running Deltacopy using SSH under Windows 2003 SP2. When I run the task manually everything run well. But if I set a scheduled task, it will not work. What it’s strange when the scheduled task start it create a .ssh directory into the root of the C: drive… but not when I execute manually the .dcp file…

Any clue?

Okay... I managed to have a fix... actually, when the task is started from the scheduled task manager... the user home directly change/is set to the root of the C:... ssh.exe create a .ssh directoty there and he is actually looking for the know_hosts file at that place... but the real one is in C:\Documents and Settings\Administrator\.ssh (depends of the user)

For testing... I have copied the .ssh directory to that location (C:\) and it's work perfectly. So the solution it's to simply set environnement variables in a batch file and start the deltacopy backup from the same file...

EX:

SET HOMEDRIVE=C:
SET HOMEPATH=\Documents and Settings\Administrator
"C:\Program Files\Synametrics Technologies\DeltaCopy\yourfilename.dcp"

Guess it would be good to add that to the FAC...

Hey! I was habing the same problem with CWRSYNC, running the batch file under a scheduled task in windows 2008

It Task Scheduler would always return Last Run Result (0x41306), which means terminated I think.

heres the fix..

if you are using the standard batch examples for CWRSYNC on windows 2008 x64, the %HOMEPATH% variable used in the example doesn't exist.

I used powershell to CD into the env: drive and do a DIR which will give you all of the valid environment variables.

%homepath% doesn't exist, but %USERPROFILE% points to the C:\Users\<USERNAME>\ which contains the .ssh subdir.

change SET HOME=%HOMEDRIVE%HOMEPATH%
to
SET HOME=%USERPROFILE%

and you should be sweet.

This message was edited 1 time. Last update was at 12/16/2009 12:43:25

In my testing I found in a Domain environment, the domain controller can use a domain admin account for DeltaCopy Client, but a member server and workstations must use a local admin account.

Also, if you are using DeltaCopy Server, only the account used to start the DeltaCopy Server service will have full permissions, all other accounts will have no permissions.

This message was edited 1 time. Last update was at 02/17/2010 22:34:33

Thank you for posting this required environment variable:
SET HOME=%USERPROFILE%

Basically I have been attempting to run php scripts which shell out ssh commands via windows scheduled task but it would never utilize the known_hosts file. I just simply created a batch file to first set that environment variable and then to run my php script. Now it works perfectly! I was writing this to hopefully help anyone else out there that might have the same problem where the scheduled task runs but the ssh connection still prompts for the password (which if you run it under a different user it would just hang in the background until eventual timeout) even though they have the authorized keys and known hosts files setup properly.

basically my batch file looks like this:
@echo off
SET HOME=%USERPROFILE%
php mysshcommandfile.php
exit

I had the same problem - running my DeltaCopy Client Profile manually worked, but it failed as a scheduled task. Here's how I fixed it:

We are trying to sync a directory located on a mapped drive on a windows 2003 R2 server with an Rsync server on a Unix webserver. DeltaCopy Client was installed on the Windows 2003 Server.

My DeltaCopy Client profile originally specified, under "Files/Folders to Copy" the mapped path, like this:

U:\fileshare\

The result was inconsistent behavior with different credentials supplied to the "run as" task, and nearly universal failure with the Windows Task Scheduler task. Sometimes it would work when I gave it Domain Admin credentials, sometimes not. Sometimes it worked with a local admin, sometimes not.

However, after right-clicking on the path in DeltaCopy Client and selecting "Modify Selection", then changing the path to a UNC path, it worked.

Before: U:\fileshare\

After: \\ServerName\Path\Fileshare\

Now if I could just figure out why notifications are not consistently sent. :)