The File Server Resource Manager configuration file '%1' is out of sync or missing records. This could have been caused by inadvertent administrator action, or by incomplete backup/restore. FSRM will attempt to regenerate default records for interim use, but there may be some missing functionality. For example, quota or screening configurations may be missing notifications. It is recommended that the system or volume be restored from backup. %2
The File Replication Service was unable to create the directory "%1" to store debug log files. If this directory does not ...
The File Replication Service will not check access to the API "%1". Access checks can be enabled for "%1" by running regedit. ...
The File Replication Service will not check access to the API "%1". Access checks can be enabled for "%1" by running regedt32. ...
The File Server Resource Manager configuration file '%1' is missing. This could have been caused by inadvertent administrator ...
The File Server Resource Manager configuration file '%1' is out of sync or missing records. This could have been caused by ...
The File Server Resource Manager configuration file or import-export file '%1' is corrupted. If the corrupt file is a configuration ...
The File Server Resource Manager detected %1 unprocessed quota or screening notifications when the service or system was ...
The File Server Resource Manager global configuration cannot be accessed since the cluster service is not running. Please ...
The File Server Resource Manager server is managed remotely using the File Server Resource Manager snap-in or the dirquota.exe, ...