A couple of people have hit problems where the ESA Admin Console reports an unhandled exception when trying to schedule a Tidy Up task.
The error message given will typically start with something along the lines of:
RedGate.ExchangeArchiver.ArchiveService.Interface.ArchiveServiceException: This schedule is trying to set maintenace tasks controlled by 33e0a0a1-efe2-4dc7-a05b-12485fd32b82.
This bug has been fixed in the latest developments builds, but in the Pre-Release, the following workaround can be used:
1) Close the Admin Console, and stop the Archive Service
2) Open the ArchiveService.xml configuration file in a text editor. This is located in C:\Documents and Settings\All Users\Application Data\Red Gate\ESA\ESA Archive Service 1, assuming it's a Windows 2003 / XP machine (C:\ProgramData\Red Gate\ESA\ESA Archive Service 1 on Vista or Server 2008)
3) Under the Schedules element, locate the <Add Key...>...</Add> that has "TasksToRun='32'" attribute set on it. Delete that node - you may wish to take a backup of the configuration file before making changes.
4) Restart the archive service and admin console, and try scheduling the tidy up again.
This should clear the problem; if it recurs, you will need to repeat the steps above.
Thanks,
Robert
The error message given will typically start with something along the lines of:
This bug has been fixed in the latest developments builds, but in the Pre-Release, the following workaround can be used:
1) Close the Admin Console, and stop the Archive Service
2) Open the ArchiveService.xml configuration file in a text editor. This is located in C:\Documents and Settings\All Users\Application Data\Red Gate\ESA\ESA Archive Service 1, assuming it's a Windows 2003 / XP machine (C:\ProgramData\Red Gate\ESA\ESA Archive Service 1 on Vista or Server 2008)
3) Under the Schedules element, locate the <Add Key...>...</Add> that has "TasksToRun='32'" attribute set on it. Delete that node - you may wish to take a backup of the configuration file before making changes.
4) Restart the archive service and admin console, and try scheduling the tidy up again.
This should clear the problem; if it recurs, you will need to repeat the steps above.
Thanks,
Robert