SQL Server 2008 R2
- Failed to locate DataType property in the XML node "{0}". The package file may be corrupt. The offending ForEachPropertyMapping ...
- Failed to locate DTSID property in the parent XML node of node "{0}". The package file may be corrupt. The offending ForEachPropertyMapping ...
- Failed to locate MappedProperty node in the XML node "{0}". The package file may be corrupt. The offending ForEachPropertyMapping ...
- Failed to locate PACKAGEPATH attribute in the XML node "{0}". The package file may be corrupt. The offending ForEachPropertyMapping ...
- Failed to locate PROPERTY attribute in the XML node "{0}". The package file may be corrupt. The offending ForEachPropertyMapping ...
- Failed to locate ValueIndex property in the XML node "{0}". The package file may be corrupt. The offending ForEachPropertyMapping ...
- Failed to lock the current log record at log sequence number (LSN) {%1!s!:%2!s!:%3!s!}. Contact Customer Support Services. ...
- Failed to obtain cryptographic key pair associated with the specified certificate with error 1!8.8X! "%2!s!". Verify that ...
- Failed to obtain XML source from XML DOM object with error 1!8.8X! "%2!s!". This occurs when IXMLDOMDocument::get_xml fails. ...
- Failed to open embedded file '{0}' containing the access control entries for registry keys and directories to apply in order ...
- 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 ...
- Failed to open package file. This happens when loading a package and the file cannot be opened or loaded correctly into an ...
- Failed to open registry key 'HKEY_LOCAL_MACHINE\{0}'. Examine if this key exists and has read permissions. SQL Server Setup ...
- Failed to open registry key 'HKEY_LOCAL_MACHINE\{1}' on the cluster node '{0}'. Examine if this key exists and has read permissions. ...
- Failed to open registry key '{0}' in order to apply permissions on registry key '{1}'. The registry key '{0}' does not exist. ...
- Failed to parse the Web Services Description Language (WSDL). Cannot find the Binding that corresponds to the SOAP port. ...
- Failed to populate the ForEachEnumeratorInfos collection with native ForEachEnumerators with the following error code: %1!s!. ...
- Failed to queue cleanup packets for orphaned rowsets in database "%1!s!". Some disk space may be wasted. Cleanup will be ...
- Failed to read registry value '{1}'. Examine if registry key 'HKEY_LOCAL_MACHINE\{0}' exists and has read permissions. SQL ...
- Failed to read registry value '{2}'. Examine if registry key 'HKEY_LOCAL_MACHINE\{1}' exists on the cluster node '{0}' and ...
- Failed to read the message body while marshaling a message. This message is a symptom of another problem. Check the SQL Server ...
- Failed to read the TXF_REPLICATION_RECORD_WRITE structure. Last error returned '%1!s!'. If the problem persists, contact ...
- Failed to remove a system variable. This error occurs when removing a variable that is a required variable. Required variables ...
- Failed to resolve groups to SIDs for SQL Server Browser and SQL Server Database Engine service groups. Make sure the service ...
- Failed to restore master database. Shutting down SQL Server. Check the error logs, and rebuild the master database. For more ...
- Failed to retrieve account for service '{0}'. SQL Server Setup expects the service exists and the account is a valid user. ...
- Failed to retrieve column properties by executing SELECT statement with schema only option from the database. The problem ...
- Failed to retrieve internal property '{0}' in order to apply permissions on the registry and/or directories for configuration ...
- Failed to retrieve the mdw version compatibility information from the configuration store. Please contact your system administrator. ...
- Failed to retrieve the oldest active log sequence number (LSN) from a commit record. Stop and restart SQL Server and the ...
- Failed to retrieve the provider invariant name from %1!s!, it is currently not supported by ADO NET Destination component ...
- Failed to retrieve value from the .ini file. The ConfiguredValueType section is either empty, or does not exist: "%1!s!". ...
- Failed to run resource governor classifier user-defined function. See previous errors in SQL Server error log from session ...
- 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 ...
- Failed to send any kind of notification to the fail-safe operator ('%1') for alert '%2'. Check the SQLServerAgent registry ...
- Failed to simulate heap for Table '%s' specified in input configuration. Simulating heaps for tables requires SQL Server ...
- Failed to truncate AppendOnlyStorageUnit 1!s!. Will retry next time. This is an informational message only. No user action ...
- Failed to update SQL Server Network Interfaces registry settings to enable local connectivity using MDAC or WDAC. Instance ...
- Failed to update the dedicated administrator connection (DAC) port number in the registry. Clients may not be able to discover ...
- Failing over database mirroring will swap the roles of the mirror and principal databases. The mirror database will become ...
- Failure to read Metadata information from a Table-Valued Parameter Rowset. Failure occurred while attempting to obtain Ordinals ...
- Failure to read Metadata information from a Table-Valued Parameter Rowset. The call to "%1" method on the TVP Rowset object ...
- Failure while loading back a swapped bufer. It may mean the system is in a low memory state and the buffer cannot get its ...
- FASTFIRSTROW hint will be removed in the next version of SQL Server. Avoid using this feature in new development work, and ...
- FCB::SetSize dbid %1!s! fileid %2!s! oldSize %3!s! newSize %4!s!. To prevent this informational message from appearing in ...
- FC[reate {SQL | DTS};ParentFolderPath;NewFolderName Operation. Create a folder on SSIS or SQL Server. The ParentFolderPath ...
- FDe[lete {SQL | DTS};ParentFolderPath;FolderName Operation. Delete a folder on SSIS or SQL Server. The ParentFolderPath is ...
- FDi[rectory {SQL | DTS}[;FolderPath[;S Operation. List the contents (folders and packages) in a folder on SSIS or SQL Server. ...
- FE[xists {SQL | DTS};FolderPath Operation. Check if a folder exists on SSIS or SQL Server. FolderPath is the path and name ...
- Field with name {0}, but different type already exists in the {1}'s field collection. Field type is {2}, but data type is ...
- File "%1!s!" cannot be opened for reading. Error may occur when there are no privileges or the file is not found. Exact cause ...
- File "%1!s!" cannot be restored over the existing "%2!s!". Reissue the RESTORE statement using WITH REPLACE to overwrite ...
- File "{0}" already exists. Do you want to reuse this file as the configuration file or overwrite the file with new configuration ...
- 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. ...
- 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 ...
- 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. ...
- 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 ...
- File '%1' already exists. If this error occurs, locate this file in the Web synchronization directory, delete the file, and ...
- File '%{fileName/}' specified in Restore command is AS encrypted backup file that was created by earlier prerelease of SQL ...
- 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 ...
- File ID %1!s! of database ID %2!s! cannot be shrunk to the expected size. The high concurrent workload is leading to too ...
- File not found: {0}. To perform this action SQL Server Configuration Manager component needs to be installed on local machine. ...
- File {0} exists in destination SQL Server and since overwrite option is not set for database ignoring transfer of database ...
- File {0} not found. SQL Server Setup expects that this file exists and that setup has read permissions on it. SQL Server ...
- File {0} not found. SQL Server Setup expects that this file exists and that setup has read permissions on it. SQL Server ...
- File {0} was not found. The file might be missing in sources or misspelled in config.xml (note: file name in config.xml is ...
- File {0} was not found. The file might be missing in sources or misspelled in config.xml, or case sensitivity may not be ...
- Filegroup '%1!s!' already exists in this database. Specify a different name or remove the conflicting filegroup if it is ...
- Filegroup '%1!s!' has no files assigned to it. Tables, indexes, and large object columns cannot be created on this filegroup. ...
- Filemark on device '%1!s!' is not aligned. Re-issue the Restore statement with the same blocksize used to create the backupset: ...
- Files are copied from the backup folder to a destination folder by a SQL Server Agent job running on the secondary server ...
- FILESTREAM columns cannot be published in a publication by using a synchronization method of either 'database snapshot' or ...
- FILESTREAM feature configuration might be inconsistent. Use the sp_filestream_configure stored procedure to reset the configuration. ...
- FILESTREAM feature could not be initialized. The Windows Administrator must enable FILESTREAM on the instance using Configuration ...
- FILESTREAM feature has been disabled. Restart the instance of SQL Server for the settings to fully take effect. If you have ...