| | |
| | | supported in the task backend |
| | | INFO_TASKBE_BACKING_FILE_HEADER_132=This file contains the data used by the \ |
| | | Directory Server task scheduler backend. Do not edit this file directly, as \ |
| | | there is a risk that those changes will be lost. Scheculed and recurring \ |
| | | there is a risk that those changes will be lost. Scheduled and recurring \ |
| | | task definitions should only be edited using the administration utilities \ |
| | | provided with the Directory Server |
| | | SEVERE_ERR_TASKSCHED_DUPLICATE_RECURRING_ID_133=Unable to add recurring task \ |
| | |
| | | MILD_ERR_SCHEMA_MODIFY_CANNOT_READ_EXISTING_USER_SCHEMA_221=An error occurred \ |
| | | while attempting to read the contents of schema file %s: %s |
| | | MILD_ERR_SCHEMA_MODIFY_CANNOT_WRITE_NEW_SCHEMA_222=An error occurred while \ |
| | | attepting to write the updated schema: %s |
| | | attempting to write the updated schema: %s |
| | | MILD_ERR_SCHEMA_MODIFY_CANNOT_DECODE_NAME_FORM_223=An error occurred while \ |
| | | attempting to decode the name form "%s": %s |
| | | MILD_ERR_SCHEMA_MODIFY_CANNOT_DECODE_DCR_224=An error occurred while \ |
| | |
| | | server was able to restore the original schema configuration, so no \ |
| | | additional cleanup should be required |
| | | MILD_ERR_SCHEMA_MODIFY_CANNOT_WRITE_NEW_FILES_NOT_RESTORED_254=An error \ |
| | | occrred while attempting to write new versions of the server schema files: \ |
| | | occurred while attempting to write new versions of the server schema files: \ |
| | | %s. A problem also occurred when attempting to restore the original schema \ |
| | | configuration, so the server may be left in an inconsistent state and could \ |
| | | require manual cleanup |
| | |
| | | MILD_ERR_SCHEMA_MODIFY_DSR_OBSOLETE_NAME_FORM_288=Unable to add DIT structure \ |
| | | rule %s because its name form %s is marked OBSOLETE in the server schema |
| | | MILD_ERR_SCHEMA_MODIFY_DSR_OBSOLETE_SUPERIOR_RULE_289=Unable to add DIT \ |
| | | structure rule %s because it references superior rule %s whihc is marked as \ |
| | | structure rule %s because it references superior rule %s which is marked as \ |
| | | OBSOLETE in the server schema |
| | | MILD_ERR_SCHEMA_MODIFY_MRU_OBSOLETE_MR_290=Unable to add matching rule use %s \ |
| | | because its matching rule %s is marked OBSOLETE in the server schema |