| Explanation | This message is for informational purposes only. |
| Action | No action is required. |
| Explanation | This message is for informational purposes only. |
| Action | No action is required. |
| Explanation | This message is for informational purposes only. |
| Action | No action is required. |
| Explanation | This message is for informational purposes only. |
| Action | No action is required. |
| Explanation | This message is for informational purposes only. |
| Action | No action is required. |
| Explanation | This message is for informational purposes only. |
| Action | No action is required. |
| Explanation | This message is for informational purposes only. |
| Action | No action is required. |
| Explanation | This message is for informational purposes only. |
| Action | No action is required. |
| Explanation | The system cannot create the full checkpoint successfully because an exception occurred. |
| Action | Use the information from the nested exception to determine the cause of the problem. |
| Explanation | The system cannot create the delta checkpoint successfully because an exception occurred. |
| Action | Use the information from the nested exception to determine the cause of the problem. |
| Explanation | The system cannot restore the checkpoint successfully because an exception occurred. |
| Action | Use the information from the nested exception to determine the cause of the problem. |
| Explanation | The system cannot delete the checkpoint successfully because an exception occurred. |
| Action | Use the information from the nested exception to determine the cause of the problem. |
| Explanation | The current operation cannot be completed because the configuration repository is locked by another user. |
| Action | Retry the operation at a later time. |
| Explanation | The system failed to retrieve the specified attribute because an exception occurred. |
| Action | Use the information from the nested exception to determine the cause of the problem or retry at a later time. |
| Explanation | The system failed to set the specified attribute because an exception occurred. |
| Action | Use the information from the nested exception to determine the cause of the problem or retry at a later time. |
| Explanation | The system failed to start the repository checkpoint service because an exception occurred. |
| Action | Use the information from the nested exception to determine the cause of the problem or retry at a later time. |
| Explanation | This message indicates the progress of a checkpoint creation and is for informational purposes only. |
| Action | No action is required. |
| Explanation | This message indicates the progress of a checkpoint restoration is for informational purposes only. |
| Action | No action is required. |
| Explanation | This message indicates the progress of a checkpoint restoration and is for informational purposes only. |
| Action | No action is required. |
| Explanation | This message indicates the progress of a checkpoint restoration and is for informational purposes only. |
| Action | No action is required. |
| Explanation | The checkpoint name specified contains characters that are not valid. |
| Action | Specify a checkpoint name using only valid characters. |
| Explanation | The administrative repository save changes will not be audited. The audit records are not generated if the automatic checkpoint is not enabled. |
| Action | Verify that automatic repository checkpoint is enabled. |
| Explanation | The system cannot delete an intermediate delta checkpoint. |
| Action | Delete the oldest delta checkpoint. |
| Explanation | The current operation cannot be completed because the configuration repository is locked by another user. |
| Action | Retry the action at a later time. |
| Explanation | The current operation cannot be completed because the checkpoint name specified does not exist. |
| Action | Specify a valid checkpoint name. |
| Explanation | The system failed to retrieve the configuration repository. |
| Action | No action is required. |
| Explanation | The system failed to create the checkpoint document because an unknown document type was found. |
| Action | No action is required. |
| Explanation | The system failed to create or copy the checkpoint document because an exception occurred. |
| Action | Use the information from the nested exception to determine the cause of the problem. |
| Explanation | The system failed to create the repository context because the repository context does not exist. |
| Action | No action is required. |
| Explanation | The system failed to extract the resource document for checkpoint restoration because an exception occurred. |
| Action | Use the information from the nested exception to determine the cause of the problem. |
| Explanation | The system failed to update the configuration repository because an exception occurred. |
| Action | Use the information from the nested exception to determine the cause of the problem. |
| Explanation | The system failed to delete the checkpoint documents because an exception occurred. |
| Action | Use the information from the nested exception to determine the cause of the problem. |
| Explanation | The current operation cannot be completed because the checkpoint path specified cannot be expanded. |
| Action | Specify a valid checkpoint location path. |
| Explanation | The system failed to initialize the checkpoint builder because an exception occurred. |
| Action | Use the information from the nested exception to determine the cause of the problem. |
| Explanation | The system failed to create checkpoint builder because it already exists. |
| Action | No action is required. |
| Explanation | The checkpoint builder is not valid. This might be an internal error. |
| Action | No action is required. |
| Explanation | The checkpoint attribute specified is not valid. |
| Action | Specify a valid checkpoint attribute. |
| Explanation | The specified checkpoint name has been used previously. |
| Action | Specify a different checkpoint name. |
| Explanation | The system failed to initialize checkpoint variables because an exception occurred. |
| Action | Use the information from the nested exception to determine the cause of the problem. |
| Explanation | The system failed to set up the notification listener for the configuration repository lock. |
| Action | No action is required. |
| Explanation | The system failed to create the checkpoint summaries because an exception occurred. |
| Action | Use the information from the nested exception to determine the cause of the problem. |
| Explanation | The system failed to create the checkpoint summary for the checkpoint name specified. |
| Action | Specify a valid checkpoint name. |
| Explanation | The system failed to create the checkpoint documents because an exception occurred. |
| Action | Use the information from the nested exception to determine the cause of the problem. |
| Explanation | The system failed to create the checkpoint details because an exception occurred. |
| Action | Use the information from the nested exception to determine the cause of the problem. |
| Explanation | The system failed to initialize the checkpoint data builder because an exception occurred. |
| Action | Use the information from the nested exception to determine the cause of the problem. |
| Explanation | The system failed to create the checkpoint data builder because it already exists. |
| Action | No action is required. |
| Explanation | The user does not have sufficient privilege to acccess the document. |
| Action | Ensure that the user has sufficient privilege to access the document. |
| Explanation | The product cannot determine the user ID so will not store the user ID with other checkpoint data. The validity of the checkpoint data is not affected. |
| Action | No user action required. |