FSRM was unable to create or access the shadow copy for the volumes mounted at {0} (volume names {1}). 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 informations 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:
FSRM global configuration, including template definitions, file group definitions, classification properties and rules, file ...
FSRM performed the following file management job notification: File Management Job Name: %1 Nofitication Days: %2 Actions ...
FSRM reports, classification and file management logs repository, including any scheduled, incident, and on-demand reports ...
FSRM set a property on a file during automatic classification. File: %1 Property Changed: %2 Property Value: %3 Retrieved ...
FSRM was unable to create or access the shadow copy for the volumes mounted at {0} (volume names {1}). Possible causes include ...
FTP does not encrypt or encode passwords or data before sending them to the server. To protect the security of your passwords ...
FTP Extensibility enables support for FTP extensibility features such as custom providers, ASP.NET users or IIS Manager users. ...
FTP Server could not create a client worker thread for user at host %1. The connection to this user is terminated. The data ...
FTP Server enables the transfer of files between a client and server by using the FTP protocol. Users can establish an FTP ...