Windows Server 2008

  1. The File Replication Service is unable to replicate from a partner computer because the event time associated with the file ...
  2. The File Replication Service is unable to replicate with its partner computer because the difference in clock times is outside ...
  3. The File Replication Service is unable to replicate with its partner computer because the difference in clock times is outside ...
  4. The File Replication Service may be preventing the computer %1 from becoming a domain controller while the system volume ...
  5. The File Replication Service may be preventing the computer %1 from becoming a domain controller while the system volume ...
  6. The File Replication Service may be preventing the computer %1 from becoming a domain controller while the system volume ...
  7. The File Replication Service moved the preexisting files in %1 to %2. The File Replication Service may delete the files in ...
  8. The File Replication Service on computer %1 is stopping because the database %2 is corrupted. The database can be recovered ...
  9. The File Replication Service on computer %1 is stopping because the database %2 is corrupted. The database can be recovered ...
  10. The File Replication Service on the computer %1 cannot communicate with the File Replication Service on the computer %2. ...
  11. The file replication service on the domain controller cannot communicate with the file replication service on this computer. ...
  12. The File Replication Service paused because the size of a file exceeds the staging space limit. Replication will resume only ...
  13. The File Replication Service paused because the size of a file exceeds the staging space limit. Replication will resume only ...
  14. The File Replication Service paused because the staging area is full. Replication will resume if staging space becomes available ...
  15. The File Replication Service paused because the staging area is full. Staging files are used to replicate created, deleted ...
  16. The File Replication Service successfully added the connections shown below to the replica set: "%1" %2 %3 %4 %5 %6 %7 %8 ...
  17. The File Replication Service successfully added this computer to the following replica set: "%1" Information related to this ...
  18. The File Replication Service was unable to create the directory "%1" to store debug log files. If this directory does not ...
  19. The File Replication Service will not check access to the API "%1". Access checks can be enabled for "%1" by running regedit. ...
  20. The File Replication Service will not check access to the API "%1". Access checks can be enabled for "%1" by running regedt32. ...
  21. The File Server Resource Manager configuration file '%1' is missing. This could have been caused by inadvertent administrator ...
  22. The File Server Resource Manager configuration file '%1' is out of sync or missing records. This could have been caused by ...
  23. The File Server Resource Manager configuration file or import-export file '%1' is corrupted. If the corrupt file is a configuration ...
  24. The File Server Resource Manager detected %1 unprocessed quota or screening notifications when the service or system was ...
  25. The File Server Resource Manager global configuration cannot be accessed since the cluster service is not running. Please ...
  26. The File Server Resource Manager server is managed remotely using the File Server Resource Manager snap-in or the dirquota.exe, ...
  27. The File Server Resource Manager service could not send email due to an error. Check the application event log for more information. ...
  28. The File Server Resource Manager service encountered an unexpected error. Check the application event log for more information. ...
  29. The File Server Resource Manager service failed to analyze the mount points under the volume mounted at {0}. Please reconfigure ...
  30. The File Server Resource Manager service failed to analyze the namespaces for volume mounted at {0}. Please reconfigure the ...
  31. The File Server Resource Manager service, or Storage Reports Manager service is either not running or was restarted. Closing ...
  32. The file system for one or more partitions on the disk for resource '%1' may be corrupt. Run the Validate a Configuration ...
  33. The file system on volume '%1' is potentially corrupted. Please run the CHKDSK utility to verify and fix the file system. ...
  34. The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the device %1 with label ...
  35. The file that was specified as a target is a directory and the caller specified that it could be anything but a directory. ...
  36. The file that you are trying to use requires a software component on your computer to be upgraded. We recommend that you ...
  37. The file transfer could not be completed because the connection was lost. Make sure your Bluetooth radio is plugged in and ...
  38. The file transfer failed because the receiving Bluetooth computer or device did not respond. If you sent the file to another ...
  39. The file type is not recognized and cannot be played. Either the correct codec (a file that compresses/decompresses audio ...
  40. The file unidrvui.dll is currently in use by one or more applications. Windows must be restarted to complete the print driver ...
  41. The file version entered contains one or more parts that are greater than the maximum value of a WORD (16-bit number). Should ...
  42. The file with extension %1 cannot be faxed because faxing requires the file to be rendered to TIF. This file cannot be rendered ...
  43. The file you are attempting to import is not valid. Please check that entity keys are unique and not already registered in ...
  44. The file you are attempting to import is not valid. Please check that the file exists, and that it is a valid UDDI resources ...
  45. The file you are attempting to play has an extension (.%s) that does not match the file format. Playing the file may result ...
  46. The file you are downloading cannot be opened by the default program. It is either corrupted or it has an incorrect file ...
  47. The file you entered is not a unattend setup information file (SIF) or the SIF is not portable to other images. Only SIFs ...
  48. The file you selected doesn't match the original file closely enough to be used as a replacement. Either try a different ...
  49. The file {0} is not digitally signed. The script will not execute on the system. Please see "get-help about_signing" for ...
  50. The FileName input parameter is a string representing the fully qualified name of the copy of the file (or directory). Example: ...
  51. The FileName input parameter is a string representing the fully qualified name of the copy of the file (or directory). Example: ...
  52. The FileName input parameter is a string representing the new name for the logical file (or directory). The FileName input ...
  53. The filename you entered could not be found. Please make sure that: - You entered a valid file name. - The directory exists. ...
  54. The filename you entered could not be opened. Please make sure that: - You entered a valid file name. - The directory exists. ...
  55. The files and settings are being copied to the disc or other storage type you chose. When this is complete, go to your new ...
  56. The files are too long to fit on the DVD. Remove some files from the disc or reduce the length of one or more video files, ...
  57. The files cannot be added to the Briefcase because it is on a read-only disk or share. Make the Briefcase writable, then ...
  58. The files cannot be added to the Briefcase because the disk is full. Remove some files from the disk, or move the Briefcase ...
  59. The files cannot be added to the Briefcase because the disk is inaccessible. Verify that the disk is accessible, then click ...
  60. The files cannot be added to the Briefcase because the source cannot be opened. Verify that the files are accessible, then ...
  61. The files could not be imported because they were compiled for a different processor type than the components already installed ...
  62. The files do not fit to the boot-block configuration file %1. Change the BASE and ORG definitions or the order of the files. ...
  63. The files or folders encrypted using the previous smart card can only be accessed by using that card or by an administrator ...
  64. The files you are restoring have security permissions for a user account which could not be found on this computer. The missing ...
  65. The FileSystemFlagsEx property indicates the file system flags associated with the Win32 CD-ROM drive. This parameter can ...
  66. The FillAttribute property specifies the initial text and background colors if a new console window is created in a console ...
  67. The filter contains a property (%1) that is of an unsupported type. Filtering is not supported on properties with the following ...
  68. The filter daemon process MSFTEFD exited unexpectedly because of document %1. Batch Id: %2 Locale Id: %3 Property Id: %4 ...
  69. The filter daemon process MSFTEFD timed out for an unknown reason. This may indicate a bug in a filter, wordbreaker, or protocol ...
  70. The filter dialect (the type associated with the filter) was not supported for this resource. Change the filter dialect or ...
  71. The filter host process cannot be started. The system is most likely low on resources, or the filter host process binary ...
  72. The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been ...
  73. The Filter Manager had an internal error from which it cannot recover, therefore the operation has been failed. This is usually ...
  74. The Filter Manager had an internal error from which it cannot recover, therefore the operation has been failed. This is usually ...
  75. The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is getting loaded ...