Warnings and errors that may be reported

If any issues are encountered during an archive or restore operation, they are listed on the Operation Complete dialog. The issues are also saved in a log file, the location and name of which are also displayed on the dialog.

Warnings

The following warnings may be reported. These warnings will not prevent an archive or restore operation from being completed:

<NUMBER> objects appear not to have been restored. They may still be located in the archive, which has consequently not been deleted. Please inspect the archive for unrestored data.

Can occur during	Restore operations.
Rarity	Extremely rare.
Possible cause	The most likely cause of this warning is that there has been a serious data error, possibly caused by data having been edited manually outside of Asta Powerproject, and therefore corrupted in some way.
Action to take	Examine the archive in question to identify whether any data that should have been restored is still in the archive. If you do find any such data in the archive, you could try copying it and then pasting it into the live project.

<OBJECT TYPE> with ID <OBJECT ID> has become invalid and has therefore been deleted.

Can occur during	Archive or restore operations.
Rarity	Very rare.
Possible cause	You are attempting to archive or restore a link that ended at a task at the time of a previous archive, where the task has been changed subsequently into an object at which a link cannot end, such as a hammock or an expanded task. For example, an archived link that ended at a task in the live project would become invalid during a restore operation if the task at which it ended had been changed subsequently into a hammock.
Action to take	No action required; the invalid object is deleted from the live project and the archive automatically.

Non-unique value found in <FIELD NAME> field for <OBJECT TYPE> with ID <OBJECT ID>.

Can occur during	Archive or restore operations.
Rarity	Rare.
Possible cause	As a result of an archive or restore, two or more objects were found that shared a value in a field that should be unique.
Action to take	No action required; Archive Manager resolves any such conflicts by changing any non-unique values to make them unique, as required for data integrity. You can take steps to avoid such conflicts from occurring.

<OBJECT TYPE> with ID <OBJECT ID> has been restored, but overlaps other tasks on the same bar.

Can occur during	Restore operations.
Rarity	Rare.
Possible cause	One or more tasks have been added to a bar from which an expanded or summary task has been archived, in the same location as the archived task. When the archived task is restored, it necessarily overlaps with the tasks that were added after the archive was made.
Action to take	Edit the project and move one of the tasks so that they no longer overlap.

<OBJECT TYPE> with ID <OBJECT ID> has been restored, but had previously been deleted from the project.

Can occur during	Restore operations.
Rarity	Rare.
Possible cause	A cross-chart link existed in the project, from which one of the charts in question was archived and the other was not. This resulted in one half of the link existing in the archive and the other half existing in the project. The half of the link that existed in the project has since been deleted and the chart in which the other half of the link existed has then been restored.
Action to take	Edit the project and delete the half of the link that has been restored.

Errors

The following errors may be reported. These errors will prevent an archive or restore operation from being completed:

Supposedly removed object (<OBJECT TYPE> with ID <OBJECT ID>) cannot be restored because it already exists in the destination project or baseline. The operation has been cancelled.

Can occur during	Restore operations.
Rarity	Extremely rare.
Possible cause	You have moved objects around that had previously been deleted in the live project by reverting to a baseline and merging into a baseline.
Action to take	Delete, then recreate the item in question in the offending project or baseline, so that it is assigned a different ID, then attempt to run the archive or restore again. You can take steps to avoid such conflicts from occurring.

Non-unique value found in <FIELD NAME> field for <OBJECT TYPE> with ID <OBJECT ID>. This field must be unique for data integrity and could not be fixed up automatically. The operation has been cancelled.

Can occur during	Archive or restore operations.
Rarity	Extremely rare.
Possible cause	One or more calendar exceptions share a value in a system field that is never displayed to the user and where it has not been possible to resolve the error automatically, because the project or baseline already contains the maximum allowable number of exceptions (30).
Action to take	Inspect the project and delete any exceptions that are not in use (if possible), then attempt to run the archive or restore again.

Archiving is not allowed when projects are still booked out.

Can occur during	Archive operations.
Rarity	Depends upon how often data is booked out from your projects.
Possible cause	You are attempting to archive data from a project from which data has been booked out for remote editing.
Action to take	Book in any data that is currently booked out (or cancel the book outs if appropriate) then attempt to run the archive again.