HEX

File: C:/Windows/System32/en-US/srm.dll.mui
MZ����@���	�!�L�!This program cannot be run in DOS mode.

$5�<�q�R�q�R�q�R�e���p�R�e�P�p�R�Richq�R�PEL�!@

`C�@ �=8.rdata�@@.rsrc@ >@@c�!
T88c�!$��8.rdata8x.rdata$zzzdbg 0.rsrc$0102,.rsrc$02 iU�;)��K�.�2�dg�ʚ���c�!(�8�P�(�@�X�x�Y�����������  �!8�"P�%h�&��'��(��)��,��-��3�?(�@@�AX�Bp�C��M��N��R��S��^�_�a0�bH�c`�dx�e��f��g��h��k��l�m �n8�qP�th�u��w��x��z��~��������(��@��X��p�������������	�
	�0	�H	�`	�x	��	��	��	��	��	�9
�: 
��8
��P
��h
���
���
���
���
���
�'�
�f��(��@��X��p����������T�����x�y0�	H	X	h	x	�	�	�	�	�	�	�	�	
	
	(
	8
	H
	X
	h
	x
	�
	�
	�
	�
	�
	�
	�
	�
			(	8	H	X	h	x	�	�	�	�	�	�	�	�			(	8	H	X	h	x	�	�	�	�	�	�	�	�			(	8	H	X	h	x	�	�	�	�	�	�	�	�			(	8	H	X	h	x	�	�	�	�	�	�	�	�		02���2���3���4��\5�d6:��6(��6~�H8X��:��0<b��=l�?�B�D���E���F���H.��Lr�,MF�tNr��P��hSH��T.��Z��p[:��[��h]���]���^J�$_���`��d���e�� i&�Hm�hn��Ho���qr�ht��wN��w��xx��${��$}f��~.�����h�����,�|�����8�����(��N�8���ܞX�4������ԩv�L�T�����,�`���b����������x�6�����x���,����� ����������������������Z������<���������l���l����^�|���l��������������+�P'�� +H%�hP 
�MUI����㓓r�@\H��x���镔v��~��<"���MUIen-USTemplateCommand ActionEmail ActionEventlog Action
Report Action
Eventlog TypeEventlog MessagePAMail To	Mail From
Mail Reply ToMail CcMail BccMail SubjectMessage TextExecutable PathAccountSidWorking DirectoryMonitor CommandKill Timeout
Log Result	ArgumentsMail ToReport TypeAction TypeAction NameRun Limit Interval
Last Run Time[Invalid User, SID=%s][all users]Process ID (%d)System ProcessPA
Unknown errorPAFSRM[Quota Path][Quota Remote Paths][Quota System Path]
[Quota Limit][Quota Limit KB][Quota Limit MB][Quota Threshold][Quota Used][Quota Used KB][Quota Used MB][Quota Used Percent]PA[Quota Peak][Quota Peak KB][Quota Peak MB][Quota Peak Percent][Quota Peak Time][Quota Free][Quota Free KB][Quota Free MB][Quota Free Percent][Source File Path][Source File Owner][Source File Owner Email][Source Process Id][Source Process Image][Source Io Owner][Source Io Owner Email][Server][Server Domain]
[Admin Email][Source File Remote Paths][Quota Limit GB][Quota Limit TB][Quota Used GB][Quota Used TB][Quota Peak GB][Quota Peak TB][Quota Free GB][Quota Free TB][Quota High Water Mark][Quota High Water Mark KB][Quota High Water Mark MB][Quota High Water Mark Percent][Quota High Water Time]
[Quota Owner][Quota Owner Email]PADirectory path of the quotaRemote paths of the quotaCanonical path of the quotaQuota limit in bytesQuota limit in KbytesQuota limit in MbytesQuota threshold (percent)Used quota in bytesUsed quota in KbytesUsed quota in MbytesQuota used percentPeak used quota in bytesPeak used quota in KbytesPeak used quota in MbytesPeak used quota percent"The time of the highest used quotaFree quota in bytesFree quota in KbytesFree quota in MbytesFree quota percentQuota event source fileQuota event source file owner#Quota event source file owner emailQuota event source process id%Quota event source process image nameQuota event source i/o owner"Quota event source i/o owner emailNETBIOS name of the serverServer domain name"Administrator email recipient list,Remote paths for the quota event source fileQuota owner account nameQuota owner email addressQuota limit in GbytesQuota limit in TbytesUsed quota in GbytesUsed quota in TbytesPeak used quota in GbytesPeak used quota in TbytesFree quota in GbytesFree quota in TbytesPA[File Screen Path][File Screen Remote Paths][File Screen System Path]PA[Violated File Group][Source File Path][Source File Owner][Source File Owner Email][Source Process Id][Source Process Image][Source Io Owner][Source Io Owner Email][Server][Server Domain]
[Admin Email][Source File Remote Paths]!Directory path of the file screenRemote paths of the file screen#Volume GUID path of the file screen#File screen event source file groupFile screen event source file#File screen event source file owner)File screen event source file owner email#File screen event source process id+File screen event source process image name"File screen event source i/o owner(File screen event source i/o owner emailNETBIOS name of the serverServer domain name"Administrator email recipient list2Remote paths for the file screen event source filePA
Operation:Context:Error-specific details:PAErrorAction typeEvent Log ActionEmail ActionCommand Action
Report ActionAction nameSMTP serverExecutable pathAccountWorking directoryMonitor commandPAKill timeout
Log result	Arguments)Validation of executable path <%s> failed.Validation of executable arguments <%s> failed?Validation of working directory <%s> for executable <%s> failed
Eventlog type
InformationalWarningError
Eventlog textAExpanded text is longer than the maximum allowed of %d charactersPAMail-to addressMail-from addressMail-reply-to addressMail-CC addressMail-BCC addressMail subjectMail message textDExpanded address is longer than the maximum allowed of %d charactersMail-to addressReport typeLarge files reportFiles by type reportLeast-recently accessed reportMost-recently accessed reportQuota usage reportFiles by owner report
Export reportFiles not backed-up reportDuplicate files reportBest practices reportFile screening audit report[The %1 '%%s' was initiated in response to quota %2 threshold exceeded notification on '%3'.gThe %1 '%%s' was initiated in response to quota %2 threshold exceeded notification on '%3' for user %4.^The %1 '%%s' was initiated in response to quota limit exceeded notification on directory '%3'.jThe %1 '%%s' was initiated in response to quota limit exceeded notification on directory '%3' for user %4.LGenerated in response to a quota %2 threshold exceeded notification on '%3'.XGenerated in response to a quota %2 threshold exceeded notification on '%3' for user %4.EGenerated in response to a quota limit exceeded notification on '%3'.QGenerated in response to a quota limit exceeded notification on '%3' for user %4./Report action for quota on %ws for threshold %d
Quota type
Quota pathPAFile IDUser SID	User nameReference timeThreshold percentPA
File group IDPAKThe %1 '%%s' was initiated in response to file screen notification on '%2'.<Generated in response to a file screen notification on '%2'.File screen pathFile screen file ID$Report action for file screen on %ws	WMI classVolume nameShadow copy volumeConfiguration fileImport-export file$The domain controller is unavailableFile screen audit logServerDomainFileNamePA
Is enabledModule namePAModule typeModule CLSIDModule account typeCompanyModule versionModule hosting phase
Scan phase	Rule nameProcess PIDHosting user accountMIIDFailed method callPossible ValuesNameTypeProperties setSupported extensionsExecution optionProperty valueProperty affectedNamespace roots.The following property definition was created:/The following property definition was modified:.The following property definition was deleted:.The following classification rule was created:/The following classification rule was modified:.The following classification rule was deleted:/The following custom classifier was registered:1The following custom classifier was unregistered:.The following storage provider was registered:0The following storage provider was unregistered:
Parameters
 (Deleted)
 (Deprecated)PA-Processing File Server Resource Manager eventQuota limit reached.Quota threshold reached.-Configuring auto apply quota on a new folder.2Quota folder deleted. Purging quota configuration.Quota volume online.Creating quota on folder '%s'.)Creating auto apply quota on folder '%s'.$Getting quota object on folder '%s'./Getting auto apply quota object on folder '%s'.0Getting restrictive quota object on folder '%s'. Enumerating quotas on path '%s'.!Enumerating quotas on the system.,Enumerating effective quotas on folder '%s'.Enumerating quotas on tag '%s'.+Enumerating auto apply quotas on path '%s'.#Performing quota scan on path '%s'. Committing quota on folder '%s'.+Committing auto apply quota on folder '%s'. Creating a collection of quotas.!Modifying a collection of quotas. Deleting a collection of quotas.1Regenerating missing quota configuration records.1Checking whether folder '%s' is subject to quota.Creating quota template.#Getting quota template object '%s'.PA*Importing quota templates from file, '%s'.Enumerating quota templates.(Exporting quota templates to file, '%s'.Upgrading quotas.PARunning email action.Running command line action.Running report action.Running event log action.#Handling a file screen audit event.>File screen folder deleted. Purging file screen configuration.0Sending file screen configuration to the driver.&Committing file screen on folder '%s'.Committing file group '%s'.,Trimming deleted file groups from the driver$Creating file screen on folder '%s'.#Getting file screen on folder '%s'.PA&Enumerating file screens on path '%s'.'Enumerating file screens on the system.NGetting file group with ID {%.8x-%.4x-%.4x-%.2x%.2x-%.2x%.2x%.2x%.2x%.2x%.2x}.Creating file group.Getting file group '%s'.Enumerating file groups.&Importing file groups from file, '%s'.$Exporting file groups to file, '%s'.PACreating file screen template."Getting file screen template '%s'."Enumerating file screen templates.0Importing file screen templates from file, '%s'..Exporting file screen templates to file, '%s'..Creating file screen exception on folder '%s'.-Getting file screen exception on folder '%s'.0Enumerating file screen exceptions on path '%s'.1Enumerating file screen exceptions on the system.Upgrading file screens.PACreating shadow copy set.+Scanning volume %s for storage report data..Starting File Server Resource Manager Service..Stopping File Server Resource Manager Service.EChecking the File Server Resource Manager global configuration store.1Installing the default file groups on the system.>Installing the default file screening templates on the system.5Installing the default quota templates on the system.PA5Installing the default storage modules on the system.8Installing the default classifier modules on the system.:Installing the default property definitions on the system.$Upgrading FSRM global configuration.$Upgrading FSRM volume configuration.PA3Initializing connection to file system filter '%s'.-Handling events from file system filter '%s'./Mapping local path '%s' to network share paths.Sending a WMI event.PA'Writing a file screen audit log record.(Flushing the file screen audit log file.-Sending backup components list to VSS system.Preparing for backup."Performing pre-restore operations.#Performing post-restore operations.1Initializing local to network share path mapping.PAInitializing Pipeline Module)IFsrmPipelineModuleImplementation::OnLoadPATRUEFALSE/<Unknown enum value %ld - configuration error?>	<Unknown>, PAFile Server Resource Manager*Manages directory quotas and file screens.Scheduled Storage TasksEManages configuration, scheduling, and generation of storage reports.&File Server Resource Manager Extension!Scheduled Storage Tasks ExtensionMicrosoft Corporation10.0UManages directory quotas, file screens, and storage reports for Windows file servers.File Server Resource Manager�Implements the File Server Resource Manager protocol for management of storage resources. It controls the management of quotas, file screens, storage reports, file management tasks, and file classification. The File Server Resource Manager service provides access to these capabilities through scriptable COM providers. When the File Server Resource Manager service is not running, quotas, file screens, storage reports, file management tasks and classification will not be active or enforced.#File Server Storage Reports Manager)The File Server Storage Reports Manager service implements the runtime functionality to run file server storage reports, file management tasks, and file classification. The service is started whenever one of these tasks is scheduled to start, and is shut down after the report or task is complete.
2 GB Limit
5 GB Limit10 GB LimitMonitor 3 TB Volume UsageMonitor 5 TB Volume UsageMonitor 10 TB Volume UsagePA100 MB Limit200 MB Limit Reports to UserMonitor 200 GB Volume UsageMonitor 500 MB Share!200 MB Limit with 50 MB Extension250 MB Extended LimitBlock Audio and Video FilesBlock Executable FilesBlock Image FilesBlock E-mail Files#Monitor Executable and System FilesAudio and Video FilesImage FilesOffice FilesE-mail FilesExecutable FilesSystem FilesCompressed FilesWeb Page Files
Text FilesBackup FilesTemporary FilesPA�User [Source Io Owner] has exceed the [Quota Threshold]% quota threshold for quota on [Quota Path] on server [Server]. The quota limit is [Quota Limit MB] MB and the current usage is [Quota Used MB] MB ([Quota Used Percent]% of limit).�User [Source Io Owner] has reached the quota limit for quota on [Quota Path] on server [Server]. The quota limit is [Quota Limit MB] MB and the current usage is [Quota Used MB] MB ([Quota Used Percent]% of limit).�The [Quota Threshold]% quota threshold for quota on [Quota Path] on server [Server] has been exceeded. The quota limit is [Quota Limit MB] MB and the current usage is [Quota Used MB] MB ([Quota Used Percent]% of limit).�The quota limit for quota on [Quota Path] on server [Server] has been exceeded. The quota limit is [Quota Limit MB] MB and the current usage is [Quota Used MB] MB ([Quota Used Percent]% of limit).+[Quota Threshold]% quota threshold exceededQuota limit exceeded Quota limit reached and extended9User [Source Io Owner] has reached the quota limit for quota on [Quota Path] on server [Server]. The quota limit is [Quota Limit MB] MB and the current usage is [Quota Used MB] MB ([Quota Used Percent]% of limit). An automatic one-time extension has been granted, and the quota limit has been increased to 250 MB.�The system detected that user [Source Io Owner] attempted to save [Source File Path] on [File Screen Path] on server [Server]. This file matches the [Violated File Group] file group which is not permitted on the system.DUnauthorized file matching [Violated File Group] file group detected�The system detected that user [Source Io Owner] saved [Source File Path] on [File Screen Path] on server [Server]. This file matches the [Violated File Group] file group. These files can be harmful as they may contain malicious code or viruses.7File matching [Violated File Group] file group detectedPAMicrosoft Corporation1.0.0.0"Office 2007 In-File Storage ModuleSystem Cache Storage ModuleFolder Classifier'Office 97 - 2003 In-File Storage ModuleContent ClassifierSecure Storage ModuleWindows PowerShell Classifier%Storage module for Office 2007 files.�Stores properties in Alternate Data Streams as a cache and storage mechanism for files that do not support other types of storageCClassifies all files in folders included in the scope of this rule.*Storage module for Office 97 - 2003 files.>Searches for strings and regular expression patterns in files.KStores secure properties within the security descriptor for all file types.PA2Classifies files using Windows PowerShell scripts.Folder Owner Email�The Folder Owner Email property specifies the email addresses that should be contacted when users request assistance after being denied access to the folder. We recommend that you use a distribution list instead of listing specific email addresses.Folder UsageaThe Folder Usage property specifies the purpose of the folder and the kind of files stored in it.
User Files8This folder contains files that belong to a single user.Group Files9This folder contains files that are shared between users.Application Files@This folder contains files used by applications such as Hyper-V.Backup and Archival Files@This folder contains files that have been backed up or archived.PA Access-Denied Assistance MessageThe Access-Denied Assistance Message property specifies what users see when denied access to the folder. Users denied access to folders that do not have this property assigned instead see the access-denied assistance message specified in File Server Resource Manager.PA�Searches for strings and regular expression patterns in files. The classification rule assigns the property only if all expressions that you specify are found. Strings are not case sensitive unless you choose the StringCaseSensitive or RegularExpression types.

Important: Complex regular expressions can reduce classification speed and consume large amounts of memory. See MSDN for more information about regular expressions.pThe Windows PowerShell classifier requires that the Windows PowerShell execution policy allow the script to run.UnknownOrdered ListMulti Choice ListSingle Choice ListStringMulti StringIntegerBooleanDateFileFoldercreatedmodifieddeletedGlobal
DeprecatedSecure,<Value is provided by classification method>UnknownKeep exisitng value'Aggregate existing value with new value'Overwrite existing value with new valueAll properties	All filesAllow email requestsShow device troubleshootingPut data owner on TO linePut administrator on TO lineInclude device claimsInclude user information'Generate an event log when sending mail8Access assistance requested from User: %s\%s to Path: %s5Help user find a file or folder. User: %s\%s Path: %sUnknownNot providedNonePA'Access Denied - ERROR_ACCESS_DENIED 0x5)File Not Found - ERROR_FILE_NOT_FOUND 0x2�This can occur if you don't have permission to access the file or folder, or if your computer doesn't meet security policy requirements.

Message from the administrator of the file server:
- Ask your manager if you're in the right security groups
- For troubleshooting information, go to <a href="http://support.microsoft.com">Microsoft Support</a>

If you need more help, click Request assistance.vFor general support, contact: [Provide email address]

For share permissions support, contact: [Provide email address]File/Folder PermissionsShareCentral PolicyUnable to determine$<font color="#C74824">Blocked</font>$<font color="#008800">Allowed</font> (Local)	(cleared)	(unknown)6<tr><td colspan="2">No available attributes.</td></tr>@<tr><td colspan="2">Attributes display is not enabled.</td></tr>PA�The path '%s' does not exist. This path will be ignored for now. The directory was probably deleted and will not be included in reporting or classification. Please reconfigure reporting or classification settings appropriately.�Invalid namespace root specified for reporting or classification: the path '%s' is not a valid directory (for example - it might be a file). Please reconfigure reporting or classification settings appropriately.�File Server Resource Manager was unable to access the following directory: '%s'. You must give Local System access to this directory to do further operations on it.%The volume mounted at '%s' ('%s') for namespace root '%s' is not a valid volume for reporting or classification. Make sure that you include only paths on fixed NTFS volumes in the report. This path will be ignored for now. Please reconfigure reporting or classification settings appropriately.rFile Server Resource Manager encountered an error during a volume scan of the volume mounted at '%s' ('%s'): '%#x'PAModule nameRules	File name
Property nameProperty value�The properties in the file were modified during this classification session so they will not be updated. Another attempt to update the properties will be made during the next classification session.�The file was modified during this classification session so its properties will not be updated. Another attempt to update the properties will be made during the next classification session.PABulk Classification ConsumerLoad PropertiesSave Properties)Check File State Before Saving PropertiesBegin File ProcessingEnd File ProcessingPAGet File PropertiesSet File PropertiesHRESULT = %#x (%s)}The value for property '%s' could not be determined due to an aggregation error.  The sources that led to the failure are: %siThe value for property '%s' from the property cache for the file could not be applied. HRESULT = %#x (%s)|The file resides under a protected namespace (such as %WINDIR%\System32). Its classification properties will not be updated.JNo applicable storage module was available to save the specified property.uThe value for property '%s' could not be determined. The property will not be updated in the file. HRESULT = %#x (%s)�The content type %s is not defined for the Office storage module. Please check the rule that sets the content type to make sure it uses an existing type.-Failed to create new property '%s' in parser.5Failed to set value '%s' for property '%s' in parser.2Failed to remove existing property '%s' in parser.Failed to open file %s.PA:Test notification message for File Server Resource Manager,This email address has been configured as a default for quota, file screening, and file management notifications on server %s. To update this information, in File Server Resource Manager, on the Action menu, click Configure Options, and then update the email addresses on the Email Notifications tab.�FSRM global configuration, including template definitions, file group definitions, classification properties and rules, file management and report settings that apply to the entire systemyFSRM configuration on volume %s, including its quota configuration, file screen configuration, and file screen audit logs�FSRM reports, classification and file management logs repository, including any scheduled, incident, and on-demand reports and logsTFSRM encountered a failure during pre-restore of global configuration; HRESULT = %#xUFSRM encountered a failure during post-restore of global configuration; HRESULT = %#xIFSRM encountered a failure during pre-restore of volume %s; HRESULT = %#xJFSRM encountered a failure during post-restore of volume %s; HRESULT = %#xPAVFSRM classification module configuration, captured when the module registers with FSRM[Source File Path][Source File Remote Paths][Source File Owner][Source File Owner Email][Server][Server Domain]
[Admin Email][Result List File][Error List File][Destination Directory][Task Name][File Action Date][Days Before File Action][Number Of Files Under Action][File Management Path][File Management Remote Paths][File Management System Path]PA File management task source file5Remote paths for the file management task source file&File management task source file ownerPA,File management task source file owner emailNETBIOS name of the serverServer domain name"Administrator email recipient listlPath to the file that contains all the files with action applied during an execution of file management taskgPath to the file that contains all the errors that happened during an execution of file management task(The directory where files are expired toThe file management task nameBThe date when file management task applies action to a source fileJNumber of days before file management task applies action to a source fileONumber of files with action applied during an execution of file management task*Directory path of the file management task(Remote paths of the file management task,Volume GUID path of the file management taskPA[Original File Path][Original File Path Folder]
[Admin Email][Data Owner Email]#Original file path accessed by user9Folder containing the original file path accessed by user"Administrator email recipient listData owner email recipient listPA[UNC FILE PATH][UNC PARENT PATH]
[DOMAIN NAME][USER NAME][USER EMAIL][FULL ACCESS GRANTED][MODIFY ACCESS GRANTED][READ EXEC ACCESS GRANTED][FULL LIMITERS][MODIFY LIMITERS][READ EXEC LIMITERS][ADMIN MESSAGE][USER MESSAGE]
[USER CLAIMS][DEVICE CLAIMS][UNC SHARE][READ ACCESS GRANTED][WRITE ACCESS GRANTED][READ LIMITERS][WRITE LIMITERS]QuotaQuota Management Filter DriverDatascrnFile Screening Filter DriverCbafiltCBA Cache Filter DriverPAMicrosoft CorporationMicrosoft Corporation�Synchronizes the File Classification Infrastructure taxonomy on the computer with the resource property definitions stored in Active Directory Domain Services.(Starts a scheduled file management task.Starts a scheduled report job..Starts the scheduled automatic classification.PACreateRetrieveProcessModifyDeleteOperation: %s, Object: %s5Operation: %s, Object: %s, Object Identifier (%s): %sPA$Operation: %s, Object: %s, Result:%s
Property namepropertyquotaquota template
auto-quotaquota thresholdclassification"classification property definitionclassification rulefile management job actionfile management jobfile management job condition file management job notification'file management job notification actionstorage reportPAaction access-denied assistance setting
file groupfile screenfile screen exceptionfile screen templatefolder management property folder management property valuescheduled taskFSRM settingquotasquota templatesauto-quotasquota thresholds#classification property definitionsclassification rulesPAfile management job actionsfile management jobsfile management job conditions!file management job notifications(file management job notification actionsstorage reportsactions!access-denied assistance settingsfile groupsfile screensfile screen exceptionsfile screen templatesfolder management properties!folder management property valuesscheduled tasks
FSRM settingsStartStopWaitUpdateSend
test emailReseteffective namespacesSuccessFailedPA
RMS templatesmacrosclassification property valueclassification property valuesOKzThe file was in use and could not be classified. Another attempt to classify the file will be made after the retry period.Initializing...#Creating snapshots on volume(s): %s7Analyzing directory structure for volume %s (%u of %u).*Waiting for existing job(s) to complete...)Summarizing data on volume %s (%u of %u).(Processing data on volume %s (%u of %u).%u files processed.
Finalizing...Classifying files Running file management task: %sRunning storage report: %sPASSSS@��4 � �� � ��% �A ��*0�0��W0�50��j70�?0���@�@�0�S�S�0�
S�S���S�S���S�S��S�!S� �$S�$S��(S�*S�T�,S�IS�`�PS�ZS�h�`S��S��S��S�� pAt least one failure occurred in a batch operation.

The file may only have partial classification because a failure occurred while loading or classifying the file properties.

�Classification failed on one or more volumes. Check the application event log for more information.

�Auto apply quota configuration for one or more folders failed.  Check the application event log for more information.

\File Server Resource Manager Service information: Volume '%1' appears as disconnected and it is

ignored by the service.  You may want to rescan disks.   Error: %2.

%3

|File Server Resource Manager Service information: The COM Server with CLSID %1 and name '%2' cannot be started on machine '%3'.

Most likely the CPU is under heavy load.  Error: %4.

%5

(File Server Resource Manager Service information: The COM Server with CLSID %1 and name '%2' cannot be started on machine '%3'.  Error: %4.

%5

�File Server Resource Manager Service error: The COM Server with CLSID %1 and name '%2' cannot be started on machine '%3' during Safe Mode.

The File Server Resource Manager service cannot start while in safe mode.  Error: %4.

%5

$File Server Resource Manager Service error: A critical component required by the File Server Resource Manager Service is not registered.

This might happen if an error occurred during Windows setup, or if the computer does not have the Windows Server 2008 or later version of FSRM installed.

The error returned from CoCreateInstance on class with CLSID %1 and Name '%2' on machine '%3' is %4.

%5

�File Server Resource Manager Service error: The FSRM event log source EventMessageFile '%1' found in registry key '%2' is not correct. 

This might happen if an error occurred during Windows setup.

%3

�File Server Resource Manager Service error: Unexpected error calling routine %1.  hr = %2.

%3

�File Server Resource Manager failed to initialize its WMI event provider component. Therefore, WMI events will not be sent during quota and screening notification processing.

In order to receive WMI events, check the status of the WMI service and WMI event logs, correct the WMI errors, and restart the File Server Resource Manager service.

%1

XFile Server Resource Manager failed to initialize its shadow copy writer component. Therefore, backup and restore of the File Server Resource Manager stores may not be done correctly.

In order to properly perform backup and restore of File Server Resource Manager, check the status of the COM+ Event System service and VSS and COM+ event logs, correct the errors, and restart the File Server Resource Manager service.

%1

PThe storage reports repository will not be included in the File Server Resource Manager backup because the service failed to retrieve the repository locations.

%1

�File Server Resource Manager Service error: Unexpected error.

%1

�File Server Resource Manager Service warning: %1.  Error: %2.

%3

tError occurred during file screen configuration.  File screening will not be enforced for directory '%1' on volume '%2' until the error is corrected and the volume is remounted.

%3

8FSRM Assert Failure: %1

�File Server Resource Manager Service error: Unexpected COM error %1: %2.  Error code: %3.

%4

�Communication port '%1' to the '%2' filter driver was established.

Communication port '%1' to the '%2' filter driver was disconnected.

The '%2' filter driver may need to be started.  Retrying...

pThe File Server Resource Manager detected %1 unprocessed quota or screening notifications when the service or system was stopping.  Administrators or end-users may not have received notification of quota or screening violations.  Running a quota report can help identify quotas that are in a critical state.

�The required '%1' property of the action '%2' is missing.

%3

�The required '%1' property of the action '%2' at threshold %3%% is missing.

�The required '%1' property of the action '%2' at the limit is missing.

�The '%1' property of the action '%2' is not within the legal range.

%3

�The '%1' property of the action '%2' at threshold %3%% is not within the legal range.

�The '%1' property of the action '%2' at the limit is not within the legal range.

�The properties of the action '%2' specify an illegal combination.

%3

�The properties of the action '%2' at threshold %3%% specify an illegal combination.

�The properties of the action '%2' at the limit specify an illegal combination.

�Multiple actions were found sharing the same action name: '%1'.

%1

This command was initiated by the File Server Resource Manager service.  It belongs to the action '%1' of the file screen on path '%2'.

8This command was initiated by the File Server Resource Manager service.  It belongs to the action '%1' on the %2%% threshold on the quota on path '%3'.

TThis command was initiated by the File Server Resource Manager service.  It belongs to the action '%1' on the %2%% threshold on the quota on path '%3' for user '%4'.

(This command was initiated by the File Server Resource Manager service.  It belongs to the action '%1' on the limit on the quota on path '%3'.

8This command was initiated by the File Server Resource Manager service.  It belongs to the action '%1' on the limit on the quota on '%3' for user '%4'.

,File Server Resource Manager will no longer monitor the following FSRM-initiated command-line programs because the service is shutting down: '%1'

4File Server Resource Manager killed the following FSRM-initiated command-line program because it exceeded its %1-minute run time limit setting: '%2'

�File Server Resource Manager was unable to terminate the following FSRM-initiated command-line program: '%1'

�The following FSRM-initiated command-line program exited with return code %1

TFile Server Resource Manager was unable to access the following directory: '%1'.  You must give Local System access to this directory to do further operations on it.

�File Server Resource Manager was unable to access the following file or volume: '%1'.  This file or volume might be locked by another application right now, or you might need to give Local System access to it.

�The path '%1' does not exist. This path will be ignored for now. The directory was probably deleted and will not be included in reporting or classification. Please reconfigure reporting or classification settings appropriately.

�Invalid namespace root specified for reporting or classification: the path '%1' is not a valid directory (for example - it might be a file). Please reconfigure reporting or classification settings appropriately.

TThe volume mounted at '%1' ('%2') for namespace root '%3' is not a valid volume for reporting or classification. Make sure that you include only paths on fixed NTFS volumes in the report. This path will be ignored for now. Please reconfigure reporting or classification settings appropriately.

�File Server Resource Manager failed to retrieve the mount points under the volume mounted at '%1'. Make sure the volume mounted at this location is not offline or unavailable. This path will be ignored for now.

�File Server Resource Manager failed to register all reporting and classification consumers.

�File Server Resource Manager failed to register all classification rules.

�File Server Resource Manager failed to initialize the volume scanner.

�File Server Resource Manager encountered an unexpected error while initializing modules in the classification pipeline.

�File Server Resource Manager failed to initialize all consumers in the classification pipeline.

�File Server Resource Manager encountered an unexpected error during volume scan of volumes mounted at '%1' ('%2'). To find out more information about the root cause for this error please consult the Application/System event log for other FSRM, VSS or VOLSNAP errors related with these volumes. Also, you might want to make sure that you can create shadow copies on these volumes by using the VSSADMIN command like this: VSSADMIN CREATE SHADOW /For=C:

�File Server Resource Manager was unable to create or access the shadow copy for volumes mounted at '%1' ('%2'). Possible causes include an improper Shadow Copy configuration, insufficient disk space, or extreme memory, I/O or CPU load of the system. To find out more information about the root cause for this error please consult the Application/System event log for other FSRM, VSS or VOLSNAP errors related with these volumes. Also, you might want to make sure that you can create shadow copies on these volumes by using the VSSADMIN command like this: VSSADMIN CREATE SHADOW /For=C:

�File Server Resource Manager was unable to access volumes mounted at '%1' ('%2'). Make sure that dismount or format operations do not happen while running classification or generating reports.

XClassification module '%1' has failed.

tReporting or classification consumer '%1' has failed.

PScanning statistics on volume mounted at '%1' ('%2'):%n

- File count: %3%n

- Milliseconds elapsed: %4%n

- Files per second: %5%n

- Resident stream count: %6%n

%1

%1

|Scanning statistics on pipeline running on '%1':%n

%2%n

4A fatal error has occurred in the classification pipeline. All currently running reporting, classification, and file management jobs will be aborted.

dPerformance statistics for module '%1':%n

- Total file count: %2%n

- Total time spent (s): %3%n

- Average time spent per file (ms): %4%n

- Maximum time spent on a file (ms): %5%n

- File that caused maximum time: %6%n

- Files processing for longer than 10 seconds: %7%n

- Files processing for longer than 1 minute: %8%n

- Files processing for longer than 10 minutes: %9%n

- Files processing for longer than 1 hour: %10%n

�File Server Resource Manager was unable to access a file or volume. Details:%n

%1%n

The volume may be inaccessible for I/O operations or marked read-only. In case of a cluster volume, this may be a transient failure during failover.

$The File Server Resource Manager configuration file '%1' is not found. It is required that the system or volume be restored from backup.

%2

hA File Server Resource Manager module encountered an invalid parameter or a valid parameter with an invalid value or an expected module parameter is not found. Parameter: '%1'

�File Server Resource Manager was unable to scan volume  '%1' ('%2'). 

�File Server Resource Manager failed to schedule auto apply quota rebuilding on volume '%1'.

�File Server Resource Manager encountered an error during a classification operation.%n

HRESULT = %1%n%n

Details:%n

%2

�File Server Resource Manager set a property on a file outside of automatic classification.

%1

�File Server Resource Manager cleared a property on a file outside of automatic classification.

%1

`File Server Resource Manager set properties on a file outside of automatic classification. This can occur if a file is manually classified. No user action is required.

%1

�File Server Resource Manager detected an invalid SID, %1, for the quota on directory, '%2'.

$File Server Resource Manager failed to automatically upgrade its configuration on volume %1. The volume cannot be added to the upgrade queue.

�The File Server Resource Manager Reports service is shutting down due to idle timeout.

%1

The File Server Resource Manager Reports service is shutting down due to shutdown event from the Service Control Manager.

%1

�The File Server Resource Manager configuration file or import-export file '%1' is corrupted.  If the corrupt file is a configuration file, it is required that the system or volume be restored from backup.  If the file is an import-export file, export the items again and retry the operation without editing the file contents.

%2

�File Server Resource Manager has received a configuration request from the file screen filter driver for volume '%1'.

�File Server Resource Manager has completed a configuration request from the file screen filter driver for volume '%1'.

�File Server Resource Manager failed to configure auto apply quota settings on path '%1'.

%2

�File Server Resource Manager regenerated one or more records for configuration database '%1'.  The new records contain no quota or screening notification configuration, so it is recommended that the system or volume be restored from backup.

%2

�A File Server Resource Manager Service command line action was not run because command line actions are disabled on this machine.  Use the FSRM management console to enable command line notifications on this system.

%1

A File Server Resource Manager Service command line action was not run because the last person who saved it is no longer an administrator on this machine.  Use the FSRM management console to save again the quota, screening or file management configuration.

%1

�A File Server Resource Manager Service command line action specifies an insecure path because it gives write access to '%1' on path '%2'.  Move the program to a directory that permits write access only to privileged users.

%3

�A File Server Resource Manager Service command line action could not be run.

%1

�A File Server Resource Manager Service event log action could not be run.

%1

lA File Server Resource Manager Service email action could not be run because there is no SMTP server set.  Use the FSRM management console to specify the SMTP server to use.

%1

A File Server Resource Manager Service email action could not be run because the specified TO or FROM address is invalid.  Use the FSRM management console to add valid TO and FROM e-mail addresses to the quota, screening or file management configuration.

%1

�A File Server Resource Manager Service email action could not be run.

%1

�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

pThe File Server Resource Manager configuration file '%1' is missing.  This could have been caused by inadvertent administrator action, or by incomplete backup/restore.  An empty configuration file has been created for interim use.  It is recommended that the system or volume be restored from backup.  

%2

�A File Server Resource Manager configuration file or import-export file is corrupted.  If the corrupt file is a configuration file, it is required that the system or volume be restored from backup.  If the file is an import-export file, export the items again and retry the operation without editing the file contents.

%1

�Shadow copy '%1' was deleted during storage report generation.  Volume '%2' might be configured with inadequate shadow copy storage area.  Storage reports may be temporarily unavailable for this volume.

%3

�Shadow copy creation failed for volume '%1' with error %2.  The volume might be configured with inadequate shadow copy storage area.  Storage reports may be temporarily unavailable for this volume.

%3

�File Server Resource Manager encountered an error while attempting to find the network share and DFS paths that expose the local path '%1'.  The remote paths may be temporarily unavailable to FSRM quota and screening notifications.

%2

�The File Server Resource Manager global configuration data store has been created.

�File Server Resource Manager encountered an error while initializing local-to-remote path mapping.  Mappings from local file paths to share and DFS paths will not be available until the FSRM service is restarted or the system reboots.

%1

�File Server Resource Manager encountered an error when uninitializing local-to-remote path mapping.

%1

XVolume '%1' is not supported for shadow copy.  It is possible that the volume was removed from the system.  Storage reports will not be available for this volume.

%2

�File Server Resource Manager failed to enumerate share paths or DFS paths.  Mappings from local file paths to share and DFS paths may be incomplete or temporarily unavailable.  FSRM will retry the operation at a later time.

%1

TFailed saving one of the configuration stores on volume '%1' due to a disk-full error:

If the disk is full, please clean it up (extend the volume or delete some files).

If the disk is not full, but there is a hard quota on the volume root, please delete, disable or increase this quota.

%2

�Shadow copy creation failed for volume '%1' because other shadow copies were being created.

%3

�The volume '%1' has been deleted or removed from the system.

%2

The file system on volume '%1' is potentially corrupted.  Please run the CHKDSK utility to verify and fix the file system.

%2

LError occurred during default template setup.  Template '%1', could not be installed and will not be available on the system until the system is reinstalled.

%2

PError occurred during file screen configuration.  File screening will not be enforced on volume '%1' until the error is corrected and the volume is remounted.

%2

%1

%1

dFile Server Resource Manager global configuration cannot be accessed since the cluster service is not running. Please start the cluster service and retry the operation.

%1

<The File Server Resource Manager global configuration cannot be accessed since the cluster service is not running. Please start the cluster service.

%1

hFile Server Resource Manager cannot start file screening on this system since the cluster service is not running. Screening will start once the cluster service is running.

%1

HFailed writing the file screen audit log on volume '%1' due to a disk-full error:

If the disk is full, please clean it up (extend the volume or delete some files).

If the disk is not full, but there is a hard quota on the volume root, please delete, disable or increase this quota.

%2

�File Server Resource Manager successfully created a cluster resource for the reports scheduled task '%1', but failed to bring the resource online. Please check the resource status in the cluster administration console.

%2

�File Server Resource Manager failed to take a cluster resource offline for the reports scheduled task '%1'. The report task cannot be deleted if the resource remains online. Please check the resource status in the cluster administration console.

%2

,File Server Resource Manager had a failure when invoking an COM call on an external component:%n

This might be a problem with this specific COM component that supplies this functionality.%n

You might want to follow up the error with the vendor implementing this module.%n

dFile Server Resource Manager attempted to load a disabled module.%n

Please ensure that all enabled modules in use (by FSRM classification rules and policies) are enabled.%n

tAn error occurred while File Server Resource Manager attempted to impersonate user %1 to load module %2.%n

Please check the security policies on this machine. (GetLastError = %3)%n

�An error occurred while File Server Resource Manager attempted to install a default module.%n

%1

�Rule '%1' refers to module definition '%2', which could not be found; rule will not be used for classification.

�Rule '%1' refers to a property '%2' that has no property definition; rule will not be used for classification.

�The Continuous scanner encountered an unexpected error.

%1

�File Server Resource Manager failed to find the claim list '%1' in Active Directory (ADsPath: %2). Please check that the claims list configured for this machine in Group Policy exists in Active Directory.

�File Server Resource Manager encountered a malformed claim in Active Directory Domain Services (AD DS). Please reconfigure the claim in AD DS.%n

%n

Details:%n

Domain controller: %1%n

Resource property list: %2%n

Resource property name: %3%n

�File Server Resource Manager encountered the claim %1 in Active Directory with the same name as a local property definition.  The local property definition is being marked as deprecated.

File Server Resource Manager finished syncing claims from Active Directory Domain Services with no errors.%n

%n

Details:%n

Domain controller: %1%n

Resource property list: %2%n

Properties created: %3%n

Properties modified: %4%n

Properties deleted: %5%n

XFile Server Resource Manager finished syncing claims from Active Directory and encountered errors during the sync (%1).  Please check previous event logs for details.

File Server Resource Manager failed to update property definition '%1' with data from Active Directory.  The error is: %2.

File Server Resource Manager failed to change or delete property definition '%1'.  Please check previous event logs for details.

�File Server Resource Manager failed to create the predefined property definition '%1' with the error %2.

�File Server Resource Manager could not add the Access-Denied Assistance Users group to the Remote Management Users group. Try manually adding the Access-Denied Assistance Users group to the Remote Management Users group.

�File Server Resource Manager could not remove the Access-Denied Assistance Users group from the Remote Management Users group. Try manually removing the Access-Denied Assistance Users group from the Remote Management Users group.

,File Server Resource Manager could not add '%1' group to '%2' group. Try adding this group manually to enable Access-Denied Assistance for users.

�File Server Resource Manager module '%1' took too long processing file '%2'. The module was restarted and the file skipped. The file will be processed by a future classification attempt.

�File Server Resource Manager Service added a quota.%n

%n

Quota ID: %1%n

Auto apply quota ID: %2%n

Path: %3%n

�File Server Resource Manager Service modified a quota.%n

%n

Quota ID: %1%n

Auto apply quota ID: %2%n

Path: %3%n

�File Server Resource Manager Service deleted a quota.%n

%n

Quota ID: %1%n

Auto apply quota ID: %2%n

Path: %3%n

File Server Resource Manager Service added an auto apply quota.%n

%n

Quota ID: %1%n

Auto apply quota ID: %2%n

Path: %3%n

File Server Resource Manager Service modified an auto apply quota.%n

%n

Quota ID: %1%n

Auto apply quota ID: %2%n

Path: %3%n

File Server Resource Manager Service deleted an auto apply quota.%n

%n

Quota ID: %1%n

Auto apply quota ID: %2%n

Path: %3%n

 File Server Resource Manager Service derived a quota from an auto apply quota.%n

%n

Quota ID: %1%n

Auto apply quota ID: %2%n

Path: %3%n

�File Server Resource Manager set a property on a file during automatic classification.%n

%n

File: %1%n

Property Changed: %2%n

Property Value: %3%n

Retrieved From Storage: %4%n

Rule Applied: %5%n

8File Server Resource Manager applied a file management job expiration action to a file.%n

%n

File Management Job Name: %1%n

Expiration Action: %2%n

(File Server Resource Manager applied a file management job custom action to a file.%n

%n

File Management Job Name: %1%n

Custom Action: %2%n

`File Server Resource Manager performed the following file management job notification:%n

%n

File Management Job Name: %1%n

Notification Days: %2%n

Actions Taken: %3%n

@File Server Resource Manager encountered an error while classifying a file during automatic classification.%n

%n

File: %1%n

Module: %2%n

Message: %3%n

HThe following property definition was %1:%n

%n

Name: %2%n

Type: %3%n

Global: %4%n

Secure: %5%n

Deprecated: %6%n

Applies To: %7%n

Possible Values: %8%n

�The following classification rule was %1:%n

%n

Name: %2%n

Enabled: %3%n

Valid: %4%n

Scope: %5%n

Property Assignment Method: %6%n

Property Assigned: %7%n

Value: %8%n

Re-evaluation Option: %9%n

Parameters: %10%n

<The following classifier module definition was %1:%n

%n

Name: %2%n

COM CLSID: %3%n

Properties Set: %4%n

Needs Explicit Value: %5%n

Parameters: %6%n

The following storage module definition was %1:%n

%n

Name: %2%n

COM CLSID: %3%n

Supported Extensions: %4%n

Parameters: %5%n

�The following access-denied assistance error configuration was %1:%n

%n

Error: %2%n

Enabled: %3%n

Client Display Flags: %4%n

Error Message: %5%n

Email Flags: %6%n

Additional To Emails: %7%n

Email Message: %8%n

�A request for assistance with an error was sent.%n

%n

Details:%n

Error: %1%n

Email sent to: %2%n

Email subject: %3%n

User: %4\%5%n

File path: %6%n

Parent folder: %7%n

Message from administrator: %8%n

Message from %4\%5: %9%n

0A request for assistance with an error could not be sent because the email address of the recipient is blank.%n

%n

Details:%n

Error: %1%n

Email subject: %2%n

User: %3\%4%n

File path: %5%n

Parent folder: %6%n

Message from administrator: %7%n

Message from %3\%4: %8%n

�An access-denied assistance error is configured to send email to the file server administrator, but no email address is specified in the Default Administrator Recipients box in the Options dialog box of File Server Resource Manager.%n

<File Server Resource Manager applied a file management task RMS Encryption action to a file.%n

%n

File management task name: %1%n

Custom action: %2%n

File Server Resource Manager encountered an error while contacting the RMS server. The error can be caused by any of the following issues:%n

%n

* Server unreachable: The RMS server was not reachable.%n

* Not authorized: The file server is not authorized to encrypt files by using the RMS server. Verify that the file server has Read and Execute access to the following file on the RMS server: <wwwroot>\_wmcs\certification\ServerCertification.asmx%n

* Predefined template is not valid: The template requested is not valid for encryption.%n

* Custom template is not valid: The custom template provided is not valid for encryption.

%1

File Server Resource Manager failed to create a pipeline module object. The error is: %1

See below for additional details.

%2

�This computer has case sensitive lookup enabled for file systems and the kernel, which is not supported by File Server Resource Manager.%n

To disable case sensitivity, set the "obcaseinsensitive" value to 1 in the following registry subkey, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\kernel.

�The computer has been joined to a failover cluster. The File Server Resource Manager service (SRMSVC) must be restarted to work correctly on a failover cluster.%n

To restart the service, open a Windows PowerShell command prompt as an administrator, and then type the following command: restart-service srmsvc -force

�A debugger has been attached to an FSRM process:%n

Command: '%1'%n

Module Name: '%2'

\The debugger command is invalid or a debugger process could not be attached to an FSRM process. Please make sure the command contains at least one instance of the string '[pid]', which will be replaced with the process ID.%n

If you do not want to attach a debugger process, please delete the corresponding registry entry. See below for details:%n

Command: '%1'%n

Module Name: '%2'%n

Process ID: %3%n

Registry path: '%4'

PThe requested object was not found.

�One or more of the arguments supplied to the task scheduler are not valid.

TThe specified object already exists.

LThe specified path was not found.

HThe specified user is invalid.

HThe specified path is invalid.

HThe specified limit is invalid.

HThe specified name is invalid.

XAll items in a batch operation failed.

HThe specified text is invalid.

HThe version of the configuration file you are trying to import is not supported. You cannot import configuration files with database versions earlier than 2.0.

XThe specified property is out of range.

`The specified required property is missing.

hThe specified property combination is invalid.

pDuplicate names were detected for the same object.

�The operation or the specified combination of parameters is not supported.

�A required filter driver is not installed, loaded or ready for service.

�There is insufficient disk space to perform the requested operation.

TThe specified volume is unsupported.

The File Server Resource Manager service encountered an unexpected error.

Check the application event log for more information.

HThe specified path is insecure.

@The SMTP server is invalid.

The File Server Resource Manager service could not send email due to an error.

Check the application event log for more information.

XThe specified email address is invalid.

�The file system might be corrupted.  Please run the CHKDSK utility.

�The specified command-line executable path is longer than MAX_PATH.

hThe specified file group definition is invalid.

TThe specified file screen is invalid.

XThe specified report format is invalid.

dThe specified report description is invalid.

PThe specified file name is invalid.

�A volume shadow copy could not be created or was unexpectedly deleted.

�A File Server Resource Manager XML configuration file or import-export file is corrupted.

�File Server Resource Manager global configuration cannot be accessed since the cluster service is not running.

�File Server Resource Manager global configuration cannot be accessed since it is not installed yet.

�The volume does not reside on a cluster shared disk with an associated cluster resource.

There are at least two paths which reside on different cluster shared disks which are not in the same cluster resource group.

�A report of the specified type already exists in the report job.

|The report job is already running or queued for running.

`An error occurred during report generation.

hThe task contains zero or unsupported triggers.

|A rule or policy attempted to load/use a disabled module.

�File Server Resource Manager cannot aggregate the value for the specified file property.

�The limit of the number of messages that the current pipeline context can add to the property bag has been reached.

`The object is in use and cannot be deleted.

�Cannot change the name of a property definition once it is set.

�Cannot change the type of a property definition once it is set.

�A new property definition cannot be created.  The maximum number of property definitions, {0}, has been reached.

�A classification job is currently running.  Only one classification job can be running at a time.

\Classification is not currently running.

�The file management task is already running or queued for running.

�Cannot expire a file while running a file management task.

�Cannot perform a custom action on a file while running a file management task.

xCannot send a notification for a file management task.

pFile Server Resource Manager cannot open the file.

�File Server Resource Manager failed to perform a secure link with a hosted module process.

�The property cache for the file is invalid and could not be read.

XA cache storage module already exists.

�The expiration directory cannot be within the file management scope.

�A file management task of the specified name already exists.

dThe specified file property has been deleted.

�The updating of last access times is disabled on this server.  To create a report or file management task that uses the last access time the updating of last access time must be enabled.

�The specified file property should not be assigned a value.

�An unknown module cannot be run inside the service process.

$File Server Resource Manager failed to enumerate file properties because a failure occurred while loading or classifying the file properties.

File Server Resource Manager failed to set a file property to the file because a failure occurred while saving the file properties.

�Classification properties will not be stored because a failure occurred while loading or classifying the file properties.

xClassification is not supported on the specified reparse point. File Server Resource Manager does not recognize the reparse point's identifier tag for the purposes of classification.

LThe requested property was not found. The file may only have partial classification because a failure occurred while loading or classifying the file properties.

�The File Server Resource Manager text reader was not initialized.

pThere is no IFilter registered for this extension.

8File Server Resource Manager failed to write the properties to the file because the file is either corrupt or protected by Rights Management Services.

�The IFilter for this extension is not registered correctly.

�There was an error obtaining the file's streaming interface.

XThe file name's extension is too long.

�The module will not process the specified file because it is unable to determine a compatible file format.

�File Server Resource Manager could not access the file because it is encrypted.

�File Server Resource Manager failed to persist the properties to the file.

�File Server Resource Manager failed to access the volume. It may be offline.

dThe file management action command timed out.

�The file management action completed successfully, but the exit code cannot be obtained.

�The module encountered an invalid parameter or a valid parameter with an invalid value or an expected module parameter is not found. Check the application event log for more information.

�The module initialization failed. Check the application event log for more information.

�The module session initialization failed. Check the application event log for more information.

�Classification failed on all volumes. Check the application event log for more information.

�The file management task cannot be accessed because task conditions were modified by using WMI or Windows PowerShell interfaces. To access or edit the file management task, use the WMI or Windows PowerShell interfaces.

�The file management task has reached its maximum number of conditions.

This object uses a property definition that is deprecated.  You must change it to use a non-deprecated property definition.

dThe property definition sync task timed out.

�This object uses a property definition that doesn't exist.  You must change it to use an existing property definition.

�File Server Resource Manager encountered an invalid resource claim in Active Directory.

`The classification operation was canceled.

�File Server Resource Manager encountered an invalid folder property store.

�File Server Resource Manager is rebuilding the index of Folder Usage property values.

|The specified property definition doesn't apply to files.

TThe classification request timed out.

�Classification failed on one or more files in the batch operation.

|This property is a system property and cannot be deleted.

�The file is being used by another application and cannot be accessed at this time.

xAccess-denied assistance is not enabled for this error.

�File Server Resource Manager could not create a temporary file copy.

\Access-denied assistance cannot send an email because an email address could not be found for the path specified, and sending email to the administrator is not enabled. 

�The current user has sent the maximum number of requests for access-denied assistance. 

pThe path is not included in a classification rule.

�The RMS template used to configure the file management task no longer exists.  Please select another template.

�The computer hosting the file or folder does not support setting secure properties. This can occur if the computer is running Windows Server 2008 R2, Windows 7, or earlier, or if the computer is not running Windows.

�File Server Resource Manager cannot run the file management task because no RMS protectors are installed.

�File Server Resource Manager cannot protect the file because an RMS protector for the file type is not installed.

�The specified property definition doesn't apply to folders.

tThe specified property definition type is not secure.

tThe specified property definition type is not global.

PUnexpected failure from a WMI call.

�Cannot protect a file while running a file management task.

�The property definition sync task encountered errors.

Check the application event log for more information.

tThe server does not provide access-denied assistance.

�Access-denied assistance cannot be provided for local paths.

�Access-denied assistance requires that the server be joined to a domain.

�File Server Resource Manager could not remove the read-only attribute from a file.

<A continuous file management job cannot have conditions based on the file's last accessed/modified or created times and cannot define any notifications.

�The object contains a schedule that was created by using an earlier version of File Server Resource Manager and that is incompatible with the current version of Windows Server. Edit the schedule on this computer to update it.

�This operation is not supported for paths on which Offline Files is enabled.

�Cannot write to the specified expiration directory. Confirm that the permissions of the expiration directory grant Write permission to the computer account of the server performing the file expiration task.

xThe expiration path must be 150 characters or shorter.

�The expiration directory must be on a volume formatted with the NTFS file system.

This file management job is deprecated. Please check the configuration of the file management job and verify that it is up-to-date.

�A module was restarted due to excessive processing time of a file. Check the application event log for more information.

�4VS_VERSION_INFO��
{aJ
{aJ?0StringFileInfo040904B0LCompanyNameMicrosoft Corporation�7FileDescriptionMicrosoft� File Server Resource Manager Common Libraryn'FileVersion10.0.19041.7291 (WinBuild.160101.0800)0InternalNamesrm.lib�.LegalCopyright� Microsoft Corporation. All rights reserved.@OriginalFilenamesrm.lib.muij%ProductNameMicrosoft� Windows� Operating SystemDProductVersion10.0.19041.7291DVarFileInfo$Translation	���<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html>



<head>

<title>Access Assistance Requested From User</title>

<style type="text/css">







.table-style td{

	border: 1px dotted #666;

}

.table-header-style {

	background-color: #E0E0E0;

	text-align: left;

	font-weight: normal;

}



.h1-style {

	color: #0099CC;

	font-size:medium;

	font:"Arial Black", Gadget, sans-serif;

}

body,td,th {

	font-family: Arial, Helvetica, sans-serif;

	font-size:12px;

	padding:3px 10px 3px 5px;

}



</style>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

</head>



<body>



<p id=DoNotReply><i>Please do not reply to this message as it is sent from an unmonitored account.</i></p>

<p id=GeneralInfo>A user is requesting help accessing a shared folder or file. Review the user s permissions and then take the appropriate action.</p>



<table  class="table-style" cellpadding="3" summary="This table lists the user requesting access, the resource, and the justification from the user.">

	<tr>

		<th class="table-header-style" scope="row"><ID id=UserRow>User:</ID></th>

		<td><a href="mailto:[USER EMAIL]">[DOMAIN NAME]\[USER NAME]</a></td>

	</tr>

	<tr>

		<th class="table-header-style" scope="row"><ID id=PathRow>Path:</ID></th>

		<td><a href="[UNC FILE PATH]">[UNC FILE PATH]</a></td>

	</tr>

	<tr>

		<th class="table-header-style" scope="row"><ID id=JustificationRow>Justification from user:</ID></th>

		<td>[USER MESSAGE]</td>

	</tr>

</table>

<br />

<p id=CurrentPermissions>Current permissions for user (<a href="mailto:[USER EMAIL]">[DOMAIN NAME]\[USER NAME]</a>):</p>

<table class="table-style" summary="This table lists the permissions of the user, including the effective access and what policies are limiting access.">

	<tr>

		<th class="table-header-style" scope="col"><ID id=PermHeader>Permission</ID></th>

		<th class="table-header-style" scope="col"><ID id=AccessHeader>Effective Access</ID></th>

		<th class="table-header-style" scope="col"><ID id=LimiterHeader>Access Limited By</ID></th>

	</tr>

	<tr>

		<td><ID id=FullRow>Full Control</ID></td>

		<td>[FULL ACCESS GRANTED]</td>

		<td>[FULL LIMITERS]</td>

	</tr>

	<tr>

		<td><ID id=ModifyRow>Modify</ID></td>

		<td>[MODIFY ACCESS GRANTED]</td>

		<td>[MODIFY LIMITERS]</td>

	</tr>

	<tr>

		<td><ID id=ReadExecRow>Read & Execute (or List Folder Contents)</ID></td>

		<td>[READ EXEC ACCESS GRANTED]</td>

		<td>[READ EXEC LIMITERS]</td>

	</tr>

	<tr>

		<td><ID id=ReadRow>Read</ID></td>

		<td>[READ ACCESS GRANTED]</td>

		<td>[READ LIMITERS]</td>

	</tr>

	<tr>

		<td><ID id=WriteRow>Write</ID></td>

		<td>[WRITE ACCESS GRANTED]</td>

		<td>[WRITE LIMITERS]</td>

	</tr>

</table>

<br />



<h1  id=HelpOptions class="h1-style">Help the User Obtain Access</h1>

<p id=HelpSteps>To help the user obtain access, follow these steps:</p>

<ol>

	<li id=BrowseItem>Browse to the folder <a href="[UNC PARENT PATH]">[UNC PARENT PATH]</a>, right-click the folder, and then click 

	<strong>Properties</strong>.</li>

	<li id=PermItem>On the <strong>Security</strong> tab, view the permissions for the file.</li>

	<li id=ReplyItem>Reply to the user (<a href="mailto:[USER EMAIL]">[DOMAIN NAME]\[USER NAME]</a>) with appropriate guidance. For example, the user might need to join a specific security group.</li>

</ol>

<br />



<h1 id=DenyOptions><span class="h1-style">Deny the Access Request</span></h1>

<p id=DenyText>To deny the access request, reply to the user (<a href="mailto:[USER EMAIL]">[DOMAIN NAME]\[USER NAME]</a>) informing them that they aren t allowed to access the resource.</p>

<br />



<h1><span class="h1-style"><ID id=AdditionalOptions>Additional Information</ID></span></h1>

<p>[ADMIN MESSAGE]</p>



<h1><span class="h1-style"><ID id="UserClaims">User Claim Details</ID></span></h1>

<table class="table-style" cellpadding="3" summary="This table lists the attributes of the user requesting assistance.">

  <tr>

    <th class="table-header-style" scope="col">

      <ID id="UserClaimHeader">Claim Name</ID>

    </th>

    <th class="table-header-style" scope="col">

      <ID id="UserClaimValue">Claim Value</ID>

    </th>

  </tr>

  [USER CLAIMS]

</table>



<h1><span class="h1-style"><ID id="DeviceClaims">Device Claim Details</ID></span></h1>

<table class="table-style" cellpadding="3" summary="This table lists the attributes of the machine from which the user is requesting assistance.">

<tr>

  <th class="table-header-style" scope="col">

    <ID id="DeviceClaimHeader">Claim Name</ID>

  </th>

  <th class="table-header-style" scope="col">

    <ID id="DeviceClaimValue">Claim Value</ID>

  </th>

</tr>

[DEVICE CLAIMS]

</table>



</body>



</html>

��<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html>



<head>

<title>Help User Find a File or Folder</title>

<style type="text/css">







.table-style td{

	border: 1px dotted #666;

}

.table-header-style {

	background-color: #E0E0E0;

	text-align: left;

	font-weight: normal;

}



body,td,th {

	font-family: Arial, Helvetica, sans-serif;

	font-size:12px;

	padding:3px 10px 3px 5px;

}



</style>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

</head>



<body>



<p id=DoNotReply><i>Please do not reply to this message as it is sent from an unmonitored account.</i></p>

<p id=GeneralInformation>A user is requesting help locating a file or folder that might have been 

moved or deleted. </p>



<table class="table-style" cellpadding="3" summary="This table lists the user requesting assistance, the file or folder he or she cannot locate, and the message from the user.">

	<tr>

		<th class="table-header-style" scope="row"><ID id=UserRow>User:</ID></th>

		<td><a href="mailto:[USER EMAIL]">[DOMAIN NAME]\[USER NAME]</a></td>

	</tr>

	<tr>

		<th class="table-header-style" scope="row"><ID id=PathRow>Path:</ID></th>

		<td><a href="[UNC FILE PATH]">[UNC FILE PATH]</a></td>

	</tr>

	<tr>

		<th class="table-header-style" scope="row"><ID id=JustificationRow>Message from user:</ID></th>

		<td>[USER MESSAGE]</td>

	</tr>

</table>

<p id=AdditionalInfo>If you have additional information about this file or folder, reply to the 

user (<a href="mailto:[USER EMAIL]">[DOMAIN NAME]\[USER NAME]</a>) with the new location 

or status. </p>



<p>[ADMIN MESSAGE]</p>



</body>



</html>

PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGX