SQL Server 2008

  1. Failed to open embedded file '{0}' containing the access control entries for registry keys and directories to apply in order ...
  2. Failed to open package file "%1!s!" due to error 2!8.8X! "%3!s!". This happens when loading a package and the file cannot ...
  3. Failed to open package file. This happens when loading a package and the file cannot be opened or loaded correctly into an ...
  4. Failed to open registry key '{0}' in order to apply permissions on registry key '{1}'. The registry key '{0}' does not exist. ...
  5. Failed to populate the ForEachEnumeratorInfos collection with native ForEachEnumerators with the following error code: %1!s!. ...
  6. Failed to queue cleanup packets for orphaned rowsets in database "%1!s!". Some disk space may be wasted. Cleanup will be ...
  7. Failed to read the message body while marshaling a message. This message is a symptom of another problem. Check the SQL Server ...
  8. Failed to read the TXF_REPLICATION_RECORD_WRITE structure. Last error returned '%1!s!'. If the problem persists, contact ...
  9. Failed to remove a system variable. This error occurs when removing a variable that is a required variable. Required variables ...
  10. Failed to resolve groups to SIDs for SQL Server Browser and SQL Server Database Engine service groups. Make sure the service ...
  11. Failed to restore master database. Shutting down SQL Server. Check the error logs, and rebuild the master database. For more ...
  12. Failed to retrieve column properties by executing SELECT statement with schema only option from the database. The problem ...
  13. Failed to retrieve internal property '{0}' in order to apply permissions on the registry and/or directories for configuration ...
  14. Failed to retrieve the mdw version compatibility information from the configuration store. Please contact your system administrator. ...
  15. Failed to retrieve the oldest active log sequence number (LSN) from a commit record. Stop and restart SQL Server and the ...
  16. Failed to retrieve the provider invariant name from %1!s!, it is currently not supported by ADO NET Destination component ...
  17. Failed to retrieve value from the .ini file. The ConfiguredValueType section is either empty, or does not exist: "%1!s!". ...
  18. Failed to run resource governor classifier user-defined function. See previous errors in SQL Server error log from session ...
  19. Failed to scan to the delete log record of an update base on log sequence number (LSN) {%1!s!:%2!s!:%3!s!}. Contact Customer ...
  20. Failed to send any kind of notification to the fail-safe operator ('%1') for alert '%2'. Check the SQLServerAgent registry ...
  21. Failed to simulate heap for Table '%s' specified in input configuration. Simulating heaps for tables requires SQL Server ...
  22. Failed to truncate AppendOnlyStorageUnit 1!s!. Will retry next time. This is an informational message only. No user action ...
  23. Failed to update SQL Server Network Interfaces registry settings to enable local connectivity using MDAC or WDAC. Instance ...
  24. Failed to update the dedicated administrator connection (DAC) port number in the registry. Clients may not be able to discover ...
  25. Failing over database mirroring will swap the roles of the mirror and principal databases. The mirror database will become ...
  26. Failure to read Metadata information from a Table-Valued Parameter Rowset. Failure occurred while attempting to obtain Ordinals ...
  27. Failure to read Metadata information from a Table-Valued Parameter Rowset. The call to "%1" method on the TVP Rowset object ...
  28. Failure while loading back a swapped bufer. It may mean the system is in a low memory state and the buffer cannot get its ...
  29. FASTFIRSTROW hint will be removed in the next version of SQL Server. Avoid using this feature in new development work, and ...
  30. FCB::SetSize dbid %1!s! fileid %2!s! oldSize %3!s! newSize %4!s!. To prevent this informational message from appearing in ...
  31. FC[reate {SQL | DTS};ParentFolderPath;NewFolderName Operation. Create a folder on SSIS or SQL Server. The ParentFolderPath ...
  32. FDe[lete {SQL | DTS};ParentFolderPath;FolderName Operation. Delete a folder on SSIS or SQL Server. The ParentFolderPath is ...
  33. FDi[rectory {SQL | DTS}[;FolderPath[;S Operation. List the contents (folders and packages) in a folder on SSIS or SQL Server. ...
  34. FE[xists {SQL | DTS};FolderPath Operation. Check if a folder exists on SSIS or SQL Server. FolderPath is the path and name ...
  35. File "%1!s!" cannot be opened for reading. Error may occur when there are no privileges or the file is not found. Exact cause ...
  36. File "%1!s!" cannot be restored over the existing "%2!s!". Reissue the RESTORE statement using WITH REPLACE to overwrite ...
  37. File "{0}" already exists. Do you want to reuse this file as the configuration file or overwrite the file with new configuration ...
  38. File '%1!s!' appears to have been truncated by the operating system. Expected size is %2!s! KB but actual size is %3!s! KB. ...
  39. File '%1!s!' has been rolled forward to LSN %2!s!. This log terminates at LSN %3!s!, which is too early to apply the WITH ...
  40. File '%1!s!' is claimed by '%2!s!'(%3!s!) and '%4!s!'(%5!s!). The WITH MOVE clause can be used to relocate one or more files. ...
  41. File '%1!s!' is not a valid undo file for database '%2!s! (database ID %3!s!). Verify the file path, and specify the correct ...
  42. File '%1' already exists. If this error occurs, locate this file in the Web synchronization directory, delete the file, and ...
  43. File '%{fileName/}' specified in Restore command is AS encrypted backup file that was created by earlier prerelease of SQL ...
  44. File ID %1!s! of database ID %2!s! cannot be shrunk as the target shrink size (%3!s! KB) is greater than the actual file ...
  45. File ID %1!s! of database ID %2!s! cannot be shrunk to the expected size. The high concurrent workload is leading to too ...
  46. File not found: {0}. To perform this action SQL Server Configuration Manager component needs to be installed on local machine. ...
  47. File {0} exists in destination SQL Server and since overwrite option is not set for database ignoring transfer of database ...
  48. File {0} was not found. The file might be missing in sources or misspelled in config.xml (note: file name in config.xml is ...
  49. File {0} was not found. The file might be missing in sources or misspelled in config.xml, or case sensitivity may not be ...
  50. Filegroup '%1!s!' already exists in this database. Specify a different name or remove the conflicting filegroup if it is ...
  51. Filegroup '%1!s!' has no files assigned to it. Tables, indexes, and large object columns cannot be created on this filegroup. ...
  52. Filemark on device '%1!s!' is not aligned. Re-issue the Restore statement with the same blocksize used to create the backupset: ...
  53. Files are copied from the backup folder to a destination folder by a SQL Server Agent job running on the secondary server ...
  54. FILESTREAM columns cannot be published in a publication by using a synchronization method of either 'database snapshot' or ...
  55. FILESTREAM feature configuration might be inconsistent. Use the sp_filestream_configure stored procedure to reset the configuration. ...
  56. FILESTREAM feature could not be initialized. The Windows Administrator must enable FILESTREAM on the instance using Configuration ...
  57. FILESTREAM feature has been disabled. Restart the instance of SQL Server for the settings to fully take effect. If you have ...
  58. FILESTREAM feature has been disabled. Restart the SQL Server instance in order for the settings to fully take effect. NOTE: ...
  59. FILESTREAM file named with GUID '%1!s!' that belongs to FILESTREAM data file ID 2!s! does not exist or cannot be opened. ...
  60. FILESTREAM is not supported on this instance of SQL Server. FILESTREAM is not supported on versions of SQL Server earlier ...
  61. FILESTREAM must be enabled on the primary node of a failover cluster before it can be enabled on a secondary node. Enable ...
  62. FILESTREAM_ON cannot be specified when a table has no FILESTREAM columns. Remove the FILESTREAM_ON clause from the statement, ...
  63. FILE_ID will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to ...
  64. Filter '%1!s!' already exists in publication '%2!s!'. Specify a unique name for the @filtername parameter of sp_addmergefilter. ...
  65. Filter processes using the number of pages in the procedure cache allocated to a given process. Enter a positive value to ...
  66. Filter queries by date. If you specify a beginning date only, all queries requested on or after this date are considered. ...
  67. Filtered %1!s! '%2!s!' cannot be created on table '%3!s!' because the column '%4!s!' in the filter expression is a computed ...
  68. Filtered %1!s! '%2!s!' cannot be created on table '%3!s!' because the column '%4!s!' in the filter expression is compared ...
  69. Filtered %1!s! '%2!s!' cannot be created on table '%3!s!' because the column '%4!s!' in the filter expression is compared ...
  70. Filtered %1!s! '%2!s!' cannot be created on table '%3!s!' because the column '%4!s!' in the filter expression is of a CLR ...
  71. Filtered %1!s! '%2!s!' cannot be created on table '%3!s!' because the filter expression contains a comparison with a literal ...
  72. Filtered index '%1!s!' cannot be created on object '%2!s!' because it is not a user table. Filtered indexes are only supported ...
  73. Filtered statistics '%1!s!' cannot be created on object '%2!s!' because it is not a user table. Filtered statistics are only ...
  74. Find case studies, benchmarking data, news and reviews, trial software downloads, and other information to help you decide ...
  75. Finnish-Swedish, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server ...