The File Replication Service cannot enable replication on the comptuer %1 until a backup/restore application completes. A backup/restore application has set a registry key that prevents the File Replication Service from starting until the registry key is deleted or the system is rebooted. The backup/restore application may still be running. Check with your local administrator before proceeding further. The computer can be rebooted by clicking on Start, Shutdown, and selecting Restart. WARNING - DELETING THE REGISTRY KEY IS NOT RECOMMENDED! Applications may fail in unexpected ways. The registry key can be deleted by running regedt32. Click on Start, Run, and type regedt32. Click on the window entitled HKEY_LOCAL_MACHINE. Double click on SYSTEM, CurrentControlSet, Services, NtFrs, Parameters, Backup/Restore, "Stop NtFrs from Starting". On the toolbar, click on Edit and select Delete. Be careful! Deleting a key other than "Stop NtFrs From Starting" can have unexpected sideeffects.
The file or folder you are opening contains Web content that may be unsafe. The Web content has either been modified or is ...
The file recovery operation has completed with errors. One or more files may not have been recovered correctly. Log of files ...
The File Replication Service (FRS) is set to replicate one or more folders on this server. The replication of these folders ...
The file replication service cannot communicate with the file replication service on the domain controller. The event log ...
The File Replication Service cannot enable replication on the comptuer %1 until a backup/restore application completes. A ...
The File Replication Service cannot find the DNS name for the computer %1 because the "%2" attribute could not be read from ...
The file replication service cannot populate the system volume because of an internal error. The event log may have more ...
The file replication service cannot populate the system volume because of an internal timeout. The event log may have more ...
The File Replication Service cannot replicate %1 because it overlaps the File Replication Service's logging pathname %2. ...