The number one problem that user's can experience is to run Double Image via the user interface with success, then schedule the profile to run after users are logged off, and the backups do not start.

Solution:  Most often this is because Windows disconnects mapped drive letters when a user logs off Windows and thereby disallows any Double Image mapped drive references to be effective when logged off.  To overcome this problem, change the mapped drive letters to UNC paths. i.e., \\computername\shared_folder , \\computername\<driveletter>\<somefolder>

If the Administrator is not assigned a User Name and Password, scheduled entries will not work. This is a Windows limitation and for security reasons. Windows permits users to not logon when starting or restarting Windows. Windows Administrators are not required to have passwords on XP Home, XP Pro.

This is well and good, but it carries a problem over to the Windows Task Scheduler entries and the Double Image scheduled entries as well.
 

Solution:  Ensure that the Administrator User or Backup User or Server Operator has been assigned a Password. After the user has a password, modify the scheduled tasks to include the User, Password.

The User that is creating Double Image profiles and also the Double Image Scheduler entries also needs to be assigned to the Administrators or Backup Users or Server Operator Group, thereby inheriting their permissions.

Solution:  Assign a password for the user account for which you are scheduling the task. After the user has a password, modify the scheduled task to include the password.
 

The User Name and Password applied at the time a scheduled entry is created needs to be that of a user assigned to the Administrators Group or the Backup Users or Server Operator Group.

Solution:  Ensure that the User and Password being applied in the scheduled entry are assigned to an authority group that includes Administrator or Backup User.
 

On some Windows platforms, there is not an edit to ensure that the User\Password are entered or spelled correctly, when creating a scheduled entry. If not entered correctly the scheduled tasks will not run.

Solution: Ensure that the User\Passwords entered are correct.

Double Image Scheduler entries are created and include a User ID and Password.

Another way of saying this is - If backups are done on a local machine and the source is on a networked machine, then the User must also have Administrator or Backup User permissions for the remote machine. This rule does not apply to Windows 95,98,Me since these Windows platforms do not provide the level of security required by NT, XP, 2000 and 2003, Vista.

Solution:  Ensure that the User and Password being applied in the scheduled entry are assigned to an authority group that includes Administrator or Backup User.
 

Incorrect Scheduler RUN entry - path to Double Image executable program - Each scheduled entry contains the <path to the executable of Double Image or Double Image-O>, depending on which program was used when the scheduled entry was created.

When upgrading to Double Image-O (or vice versa), the RUN path in the scheduled entries will no longer be valid, because the path to the executable is not referencing the correct program.

Since Double Image and Double Image-O are treated as two different products and both can reside on the users machine, the established scheduled entries are not modified at install time.

Solution:  Delete the current scheduled entries. Then from the main Double Image/Double Image-O UI window:

• Open a Double Image/Double Image-O profile
• Select the Schedule Icon, which takes you to the scheduler window
• Click the 'Add Profile for Backup' icon [the right arrow icon]
• Enter your date/time to run + your user/password and the new path created will be accurate.
   

A scheduled task is set to run daily, hourly (or another occurrence) and you wonder why it did not run again at the scheduled time.

When Double Image is run via the scheduler and the Copy, Run backup option 'Auto-Exit at End' of Job is not checked, then Double Image never leaves the process list in Windows. This means the scheduled job is not finished.  This causes the scheduled default of 72 hours to pass before windows finally forces the task to end. A scheduled task will not run a duplicate job until the previous one is ended.

Solution:  Check the 'Auto-Exit at End' in the Copy, Run option in the user interface.

If a NT / 2000 / 2003 / XP security model is deployed crossed a network environment with changes for User / Password that are different from the already existing scheduled entries, then scheduled entries will no longer work due to the Windows security changes.  This condition usually applies to those that change their Windows User, Password but do not change their User, Password for the scheduled tasks.

If you have created a new User and Password to log on to your machine, but have not updated the NEW User and Password to the Scheduled Task entries, then most likely you will not see any Scheduled Tasks get run.

Solution: View each scheduled task entry and update the User and Password that was changed for Windows.  You may need to log off the computer and log on for your new password to takes effect in the Task Scheduler.

The Double Image profile was renamed or moved to another location and is different than what the scheduler entry has.

Task Scheduler Service may not be running - The Windows Task Scheduler is controlled by a service. If the service is Disabled then scheduled entries will not work. Ensure that it is run Automatic.

Solution: START > Programs > Administrative Tools > Services. In the details pane > Task Scheduler.  In the General tab > Startup type list box, select Automatic. Click OK.

The scheduled backup jobs no longer run.

Possible condition: The Double Image backup profile was saved to a different folder or file name AFTER the scheduled task entry was created.  This caused the RUN line in the scheduled task to point to a backup profile that could be incorrect or not present at all.

Solution: See the RUN line of the Scheduled entry and compare the profile path to that where the Double Image profile is located.  If different correct the RUN line.  It may be more simple to delete the scheduled task job and re-create it from the Double Image UI - click Scheduler icon.
 

Day Light Savings Time Changes might effect scheduled entries when the local machine's system drive is using a FAT32 file system due to the way time changes affect the file stamps.

Solution: This problem doesn't occur with NTFS file systems on your hard drives. We recommend using NTFS on your hard drives when using Windows NT, XP and Windows 2000 operating systems.  The only recourse is to re-set a time for each scheduled entry, until the drive file system is converted to NTFS. see the Windows CONVERT command in Windows Help.

This is a problem that can not be solved by HII, since it is related to the Windows operating system in conjunction with FAT32 file systems.

More research

Scheduler Log

The Scheduler log is created by Windows and is a rotating file, meaning that once it reaches its capacity, it starts over from its beginning. This prevents the log file from becoming too large and taking too much disk space.

From a Double Image profile window, users can check the scheduler log by opening the Double Image Scheduler window {click the Scheduler Icon at the top of the Double Image window} -- then from the Scheduler window's menu > VIEW > 'Show Scheduler Log'.

You are then presented with a window showing a simple text file:

When the log reaches its capacity, you see the following event message:

[ ***** Most recent entry is above this line ***** ]

To view the Scheduler Log

1. From the Tools menu, click Schedule...
   (The Scheduler window appears.)
2. From the View menu in the Scheduler window, click Show Scheduler Log.
   -Or-
   Press Ctrl+L.
3. (The log appears.)

Events Found In The Schedule Log

1. Started <date> <time>
2. Exited <date> <time>
3. Task <task name> <program name>
4. Results

Example of Result Message:

The task completed with an exit code of (0).

This simply means that the task ended without any error conditions. Another way of stating this is to say the task went to 'End Of Job' successfully.

5. Errors

Example of Error Log Message:

** ERROR **

Unable to start task.

The specific error is:

0x80070002: The system cannot find the file specified.

Try using the Task page Browse button to locate the application.

Example of Log Detail:

"Task Scheduler Service"

Started at 04/14/2003 7:28:19 PM

"Double Image Backup Win2k C to C2 Firewire.bu 1.job" (Double Image.exe)

Started 09/15/2003 3:00:00 AM

"Double Image Backup Win2k D to D2 Firewire.bu 1.job" (Double Image.exe)

Started 09/15/2003 4:00:02 AM

"Double Image Backup Win2k C to C2 Firewire.bu 1.job" (Double Image.exe)

Finished 09/15/2003 8:47:38 AM

Result: The task completed with an exit code of (0).

"Double Image Backup Win2k D to D2 Firewire.bu 1.job" (Double Image.exe)

Finished 09/15/2003 8:47:38 AM

Result: The task completed with an exit code of (0).

"Task Scheduler Service"

Exited at 09/15/2003 12:37:51 PM

"Task Scheduler Service"

Started at 09/15/2003 12:40:35 PM

"Task Scheduler Service"

Exited at 09/15/2003 6:37:12 PM

"Task Scheduler Service"

Started at 09/15/2003 6:39:32 PM

"Task Scheduler Service"

Exited at 09/16/2003 1:07:46 AM

"Task Scheduler Service"

Started at 09/16/2003 1:09:02 AM

"Double Image Backup Win2k C to C2 Firewire.bu 1.job" (Double Image.exe)

Started 09/16/2003 3:00:00 AM

"Double Image Backup Win2k D to D2 Firewire.bu 1.job" (Double Image.exe)

Started 09/16/2003 4:00:31 AM

"Double Image Backup Win2k C to C2 Firewire.bu 1.job" (Double Image.exe)

Finished 09/16/2003 11:25:46 AM

Result: The task completed with an exit code of (0).

"Double Image Backup Win2k D to D2 Firewire.bu 1.job" (Double Image.exe)

Finished 09/16/2003 11:25:47 AM

Result: The task completed with an exit code of (0).

"Double Image Backup Win2k C to C2 Firewire.bu 1.job" (Double Image.exe)

Started 09/17/2003 3:00:00 AM

"Double Image Backup Win2k D to D2 Firewire.bu 1.job" (Double Image.exe)

Started 09/17/2003 4:00:00 AM

"Double Image Backup Win2k D to D2 Firewire.bu 1.job" (Double Image.exe)

Finished 09/17/2003 10:39:37 AM

Result: The task completed with an exit code of (0).

"Double Image Backup Win2k C to C2 Firewire.bu 1.job" (Double Image.exe)

Finished 09/17/2003 10:39:37 AM

Result: The task completed with an exit code of (0).

[ ***** Most recent entry is above this line ***** ]

---

Check List:

When scheduled jobs run, don't use drive letters in the backup profile to reference shared network folders or other network paths. Use a UNC path to reference network drive\folder\files..
i.e., \\computername\shared_folder , \\computername\<driveletter>\<somefolder>
 
Assure that the Administrator logs on with a password
 

Assure that Backup User logs on with a password
 

Assure that Users who create Double Image profiles and scheduled entries have a user permission assigned to Administrators Group and/or Backup Users Group

 

Ensure that the spelling of the User Name and Password are accurate when entering them for a scheduled entry.

 

When copying from/to a networked machine, then the Double Image user must also logon security permissions, described above, for the remote machine. Verify that this is correct.
 

Verify the following:
Did an Administrator or Backup User change their User Name and/or their Password?

If, so have all the scheduled entries been updated with the correct User Name and Password?

Has a Networked machine's Backup User's User Name and/or Password changed and not be reflected in the scheduled entries?

NOTE: Many large enterprises deploy a security model that is based on a mandatory password change for every User ID, for some other specific time period. If the User changes the system password but does not change any or all Double Image Scheduler related entry User passwords, then when the Double Image Profile launch attempt occurs the system will view the User ID as a sign on security violation and will lock that User ID out from any sign on authentication; I.E., the backup will not run for security reasons.

Did daylight saving time change and the system drive is FAT32?

Were the scheduled entries working before the daylight savings time changed?

If so, then it is likely that the scheduled entries date, time settings need to be reset for each entry.

 

Check modified scheduled entries as a result of reviewing the above possible conditions.

For a scheduled entry, set the time to 1-2 minutes ahead to see for yourself that your scheduled entry works.

If it does not, then see the scheduler job log. While in the Double Image scheduler window, VIEW > Show Scheduler Log. The Schedule Log will indicate most problems in the RUN line, if any.

If the test scheduled entry is now successful, ensure that the date, time setting to run the scheduled entry are now set to your production settings.