Windows Server 2008
- The file '[2]' cannot be installed because the file cannot be found in cabinet file '[3]'. This could indicate a network ...
- The file 2][3 is being held in use{ by the following process: Name: 4], Id: 5], Window Title: '[6]'}. Close that application ...
- The file can't be saved to %1 because there is not enough space. Free up space and try again, or try saving to another location. ...
- The file cannot be added to the library because it is a protected DVR-MS file. This content cannot be played back by Windows ...
- The file cannot be added to the library because it is smaller than the "Skip files smaller than" setting. To add the file, ...
- The file cannot be created or updated because the disk is full. Remove some files from the disk, or move the Briefcase to ...
- The file could be corrupted, and it should be verified before trying again. If the problem persists, contact your system ...
- The file could not be opened for reading. Check that the file exists and you have permissions to open the file for reading ...
- The file could not be sent because the connection could not be established. Check to make sure the Bluetooth radio is plugged ...
- The file exclusion filter list. This is a comma-separated list of filter strings to be applied to files under the local path ...
- The file extension for the filename you entered is missing or is not equal to ".SIF". This will make the unattend setup information ...
- The file is already in use. Close other programs that might be using the file, or stop playing the file, and then try again.%0 ...
- The file may contain scripts or try to access information in your library. Are you sure you want to download and open the ...
- The file name "%s" is not a valid name for a phone book download. A phone book file that will be updated using phone book ...
- The file name %1!s!' is not valid because the file name and extension cannot be the same. Please enter a different file name. ...
- The file name you are creating is too long. Try again using a shorter file name or create the file in a folder that has a ...
- The file name you have specified does not have an extension. Some operating systems might not be able to use this file. If ...
- The file name you have specified does not have an extension. This might pose a security risk for your users. Some operating ...
- The file name you typed is incorrect. The file name cannot have more than eight characters and should not include a file ...
- The file name(s) would be too long for the destination folder. You can shorten the file name and try again, or try a location ...
- The file or device that you are trying to use requires a component of Windows Media Player to be upgraded. Click Upgrade ...
- The file or drive you are trying to scan does not exist on this computer. Choose another file or drive, and then scan your ...
- 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 reference number. On NTFS volumes, each file is assigned an identifier that is unique on the volume; the identifier ...
- 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 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 working directory %2. ...
- The File Replication Service cannot replicate %1 because it overlaps the staging directory %2 of the replicating directory ...
- The File Replication Service cannot replicate %1 because the pathname of the customer designated staging directory: %2 is ...
- The File Replication Service cannot replicate %1 because the pathname of the replicated directory is not the fully qualified ...
- The File Replication Service cannot replicate %1 with the computer %2 because the computer's SID cannot be determined from ...
- The file replication service cannot satisfy the request because authenticated RPC is not available on the domain controller. ...
- The file replication service cannot satisfy the request because authenticated RPC is not available. The event log may have ...
- The file replication service cannot satisfy the request because the user has insufficient privileges on the domain controller. ...
- The file replication service cannot satisfy the request because the user has insufficient privileges. The event log may have ...
- The File Replication Service cannot start replica set %1 on computer %2 for directory %3 because the type of volume %4 is ...
- The file replication service cannot stop replicating the system volume because of an internal error. The event log may have ...
- The File Replication Service could not grant an unknown user access to the API "%1". Access checks can be disabled for "%1" ...
- The File Replication Service could not grant an unknown user access to the API "%1". Access checks can be disabled for "%1" ...
- The File Replication Service could not prepare the root directory %1 for replication. This is likely due to a problem creating ...
- The File Replication Service detected an invalid parameter value in the registry. %1. The expected registry key name is "%2". ...
- The File Replication Service detected an invalid parameter value in the registry. %1. The expected registry key name is "%2". ...
- The File Replication Service did not grant the user "%3" access to the API "%1". Permissions for "%1" can be changed by running ...
- The File Replication Service did not grant the user "%3" access to the API "%1". Permissions for "%1" can be changed by running ...
- The File Replication Service failed a consistency check (%3) in "%1" at line %2. The File Replication Service will restart ...
- The File Replication Service has detected a duplicate connection object between this computer "%6" and a computer named "%1". ...
- The File Replication Service has detected a duplicate connection object between this computer "%6" and a computer named "%1". ...
- The File Replication Service has detected a duplicate connection object between this computer "%7" and a computer named "%1". ...
- The File Replication Service has detected a duplicate connection object between this computer "%7" and a computer named "%1". ...
- The File Replication Service has detected an enabled disk write cache on the drive containing the directory %2 on the computer ...
- The File Replication Service has detected that one or more volumes on this computer have the same Volume Serial Number. File ...
- The File Replication Service has detected that the replica root path has changed from "%2" to "%3". If this is an intentional ...
- The File Replication Service has detected that the replica set "%1" is in JRNL_WRAP_ERROR. Replica set name is : "%1" Replica ...
- The File Replication Service has detected that the replica set "%1" is in JRNL_WRAP_ERROR. Replica set name is : "%1" Replica ...
- The File Replication Service has detected that the staging path for the replica set %1 has changed. Current staging path ...
- The File Replication Service has detected that the volume holding the FRS debug logs is running out of disk space. This will ...
- The File Replication Service has detected that the volume hosting the path %1 is low on disk space. Files may not replicate ...
- The File Replication Service has detected what appears to be an attempt to change the root path for the following replica ...
- The File Replication Service has detected what appears to be an attempt to change the root path for the following replica ...
- The File Replication Service has skipped one or more files and/or directories during primary load of the following replica ...
- The File Replication Service is deleting this computer from the replica set "%1" as an attempt to recover from the error ...
- The File Replication Service is having trouble enabling replication from %1 to %2 for %3 using the DNS name %4. FRS will ...
- The File Replication Service is having trouble enabling replication from %1 to %2 for %3 using the DNS name %4. FRS will ...
- The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on ...
- The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on ...
- The File Replication Service is no longer preventing the computer %1 from becoming a domain controller. The system volume ...
- The File Replication Service is stopping on computer %1 because there is no free space on the volume containing %2. The available ...
- The File Replication Service is stopping on the computer %1 because a universally unique ID (UUID) cannot be created. The ...
- The File Replication Service is unable to add this computer to the following replica set: "%1" This could be caused by a ...
- The File Replication Service is unable to open (or create) the pre-install directory under the customer designated replica ...
- The File Replication Service is unable to open the customer designated staging directory for replica set %1. The path used ...