| Local Delete cannot connect to DIVAnet on start. |
An error message will be written to the log file and a reconnection attempt will be made after the period specified in the Check_Interval parameter in configuration file. |
| Connection to DIVAnet is lost. |
An error message will be written to the log file and a reconnection attempt will be made after the period specified in the Check_Interval parameter in configuration file. |
DIVAnet returns a DIVA_ERROR as a response to a getObjectDetailsList request. |
The error is logged and the current processing cycle is interrupted by Local Delete. After the configured amount of time specified in the Check_Interval parameter in configuration file has passed, a new processing cycle is started using the initialTime parameter value for the last cleaned object (this time is stored in a separate file each time when an object is cleaned). |
| Delete request failed. |
Local Delete will wait for the delete operation to finish. In case the delete request fails, the error will be logged and Local Delete will not attempt to retry the failed delete request. |
| Power Failure, Operational System Crash, and so on. |
The customer is responsible for configuring the Windows Scheduled Task for Local Delete that will restart the application. |
| Local Delete cannot read from, or write to, the file that stores the creation date of last cleaned object. |
The error is logged and Local Delete will periodically try to repeat the I/O operation. |
| Limitation: Only one instance of Local Delete can be run at a time in ASAP Mode. |
Only one instance of Local Delete can be run in ASAP Mode. It is possible to run multiple Local Delete instances in Delayed Purge Mode if unique Windows Services names are provided. The customer is responsible for following these limitations. |
| The configuration file is not accessible. |
The error is logged and Local Delete is stopped. |
| The configuration file is not valid. |
The error is logged and Local Delete is stopped. |