SQL Server 2016

  1. Failed to obtain %1!s! access to the cached information in the replica controller (Windows Fabric replica ID 2!s!, partition ...
  2. Failed to obtain %1!s! access to the list of replica controller objects (SQL OS error %2!s!). The operation may have been ...
  3. Failed to obtain a Windows Server Failover Clustering (WSFC) object enumeration handle for objects of type %1!s! (Error code ...
  4. Failed to obtain cluster information. Either the specified instance of SQL Server is not running on a Windows Server Failover ...
  5. Failed to obtain cryptographic key pair associated with the specified certificate with error 1!8.8X! "%2!s!". Verify that ...
  6. Failed to obtain ICLRAppDomainResourceMonitor interface from CLR. The error code from CLR was: 1!s!. As a result, resource ...
  7. Failed to obtain local computer name (Error code %1!s!). The supplied buffer may be too small, or there is a system error. ...
  8. Failed to obtain the cluster quorum resource (Error code %1!s!). The WSFC service may not be running or may not be accessible ...
  9. Failed to obtain the local Windows Server Failover Clustering (WSFC) handle (Error code %1!s!). The WSFC service may not ...
  10. Failed to obtain the local Windows Server Failover Clustering (WSFC) node handle (Error code %1!s!). The WSFC service may ...
  11. Failed to obtain the local Windows Server Failover Clustering (WSFC) node ID (Error code %1!s!). The WSFC service may not ...
  12. Failed to obtain the name of local Windows Server Failover Cluster (Error code %1!s!). The WSFC service may not be running ...
  13. Failed to obtain the Windows Server Failover Clustering (WSFC) group handle for cluster group with name or ID '%1!s!' (Error ...
  14. Failed to obtain the Windows Server Failover Clustering (WSFC) node handle (Error code %1!s!) for node '%2!s!'. The WSFC ...
  15. Failed to obtain the Windows Server Failover Clustering (WSFC) node state for the local WSFC node (Error code %1!s!). The ...
  16. Failed to obtain the Windows Server Failover Clustering (WSFC) resource enumeration handle (Error code %1!s!). The WSFC service ...
  17. Failed to obtain the Windows Server Failover Clustering (WSFC) resource handle for cluster resource with name or ID '%1!s!' ...
  18. Failed to obtain the WSFC node enumeration handle. The error code is %1!s!. The WSFC service may not be running or may be ...
  19. Failed to obtain the WSFC resource dependency expression for cluster resource with name or ID '%1!s!' The error code is %2!s!. ...
  20. Failed to obtain the WSFC resource state for cluster resource with name or ID '%1!s!'. The WSFC resource state API returned ...
  21. Failed to obtain XML source from XML DOM object with error 1!8.8X! "%2!s!". This occurs when IXMLDOMDocument::get_xml fails. ...
  22. Failed to open a cluster network interface object: '%1!s!'. The WSFC cluster control API returned error code %2!s!. The WSFC ...
  23. Failed to open a cluster network object: '%1!s!'. The WSFC cluster control API returned error code %2!s!. The WSFC service ...
  24. Failed to open connection. You might have specified an unsupported authentication method in the connection string for the ...
  25. Failed to open embedded file '{0}' containing the access control entries for registry keys and directories to apply in order ...
  26. Failed to open package file "%1!s!" due to error 2!8.8X! "%3!s!". This occurs when loading a package and the file cannot ...
  27. Failed to open package file. This occurs when loading a package and the file cannot be opened or loaded correctly into the ...
  28. Failed to open registry key 'HKEY_LOCAL_MACHINE\{1}' on machine '{0}'. Examine if this key exists and has read permissions. ...
  29. Failed to open registry key '{0}' in order to apply permissions on registry key '{1}'. The registry key '{0}' does not exist. ...
  30. Failed to open the Windows Server Failover Clustering (WSFC) resource registry key '%1!s!' (Error code %2!s!). The WSFC service ...
  31. Failed to open the Windows Server Failover Clustering registry subkey '%1!s!' (Error code %2!s!). The parent key is %3!s!the ...
  32. Failed to open Windows Server Failover Clustering (WSFC) registry root key (Error code %1!s!). The WSFC service may not be ...
  33. Failed to parse directory section of the database backup; this error is likely caused by a backup truncation. Directory offset=%ld{dirOffset/}, ...
  34. Failed to parse the Web Services Description Language (WSDL). Cannot find the Binding that corresponds to the SOAP port. ...
  35. Failed to perform a versioned copy of sqlscriptdowngrade.dll from Binn to Binn\Cache folder. VerInstallFile API failed with ...
  36. Failed to perform database operation '%1!s!' on database '%2!s!' (ID %3!s!) in availability group '%4!s!'. The database might ...
  37. Failed to persist configuration data of availability group '%1!s!' in the Windows Server Failover Clustering (WSFC) cluster. ...
  38. Failed to populate the ForEachEnumeratorInfos collection with native ForEachEnumerators with the following error code: %1!s!. ...
  39. Failed to process the registry key value '%1!s!' (Windows error code: %2!s!), which holds the name of the remote Windows ...
  40. Failed to queue cleanup packets for orphaned rowsets in database "%1!s!". Some disk space may be wasted. Cleanup will be ...
  41. Failed to read registry value '{2}'. Examine if registry key 'HKEY_LOCAL_MACHINE\{1}' exists on machine '{0}' and has read ...
  42. Failed to read the message body while marshaling a message. This message is a symptom of another problem. Check the SQL Server ...
  43. Failed to read the TXF_REPLICATION_RECORD_WRITE structure. Last error returned '%1!s!'. If the problem persists, contact ...
  44. Failed to receive Windows Server Failover Clustering (WSFC) change notifications (Error code %1!s!). The WSFC service may ...
  45. Failed to register additional Windows Server Failover Clustering (WSFC) change notifications with notification filter %1!s! ...
  46. Failed to register client (ID %1!s!) with asynchronous operations administrator. A client with this ID has already been registered. ...
  47. Failed to register Power BI client application. You may not have permissions to register an app with Azure Active Directory. ...
  48. Failed to remove a FILESTREAM file. The database is a primary database in an availability group. Wait for the FILESTREAM ...
  49. Failed to remove a node from the possible owner list of a Windows Server Failover Clustering (WSFC) resource (Error code ...
  50. Failed to remove a system variable. This error occurs when removing a variable that is a required variable. Required variables ...
  51. Failed to remove the availability group replica '%1!s!' from availability group '%2!s!'. The availability group does not ...
  52. Failed to remove the resource dependency in which resource '%1!s!' is depending on resource '%2!s!' in the WSFC cluster. ...
  53. Failed to rename customized logging level '%1!s!' with '%2!s!'. You do not have sufficient permissions to rename customized ...
  54. Failed to resolve groups to SIDs for SQL Server Browser and SQL Server Database Engine service groups. Make sure the service ...
  55. Failed to resolve the path '{0}' to an object of type '{1}'. Either set your location to the proper context, or use the -Path ...
  56. Failed to resolve the path {0}' to an object of type '{1}'. Either set your location to the proper context, or use the -Path ...
  57. Failed to restore master database. Shutting down SQL Server. Check the error logs, and rebuild the master database. For more ...
  58. Failed to resume data movement in database '{2}', which resides on the availability replica '{0}' in the availability group ...
  59. Failed to retrieve account for service '{0}'. SQL Server Setup expects the service exists and the account is a valid user. ...
  60. Failed to retrieve column properties by executing SELECT statement with schema only option from the database. The problem ...
  61. Failed to retrieve data for this request because the federation member, {0}, has been repartitioned or deleted or is not ...
  62. Failed to retrieve internal property '{0}' in order to apply permissions on the registry and/or directories for configuration ...
  63. Failed to retrieve matrix information from '{0}'. Check if it corresponds to a server\instance of a valid brick in a matrix. ...
  64. Failed to retrieve service desription from Windows Fabric for partition '%1!s!' (Windows Fabric error 2!s!). If this condition ...
  65. Failed to retrieve the mdw version compatibility information from the configuration store. Please contact your system administrator. ...
  66. Failed to retrieve the oldest active log sequence number (LSN) from a commit record. Stop and restart SQL Server and the ...
  67. Failed to retrieve the Paxos tag from the Windows Server Failover Clustering (WSFC) registry hive. The WSFC registry hive ...
  68. Failed to retrieve the provider invariant name from %1!s!, it is currently not supported by ADO NET Destination component ...
  69. Failed to retrieve the Windows Server Failover Clustering (WSFC) registry value corresponding to name '%1!s!' (Error code ...
  70. Failed to retrieve value from the .ini file. The ConfiguredValueType section is either empty, or does not exist: "%1!s!". ...
  71. Failed to run resource governor classifier user-defined function '%1!s!'. Last error %2!s!, state %3!s!. See previous errors ...
  72. 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 ...
  73. Failed to schedule or execute database operation '%1!s!' on database '%2!s!' (Database ID: %3!s!) in availability group '%4!s!' ...
  74. Failed to send any kind of notification to the fail-safe operator ('%1') for alert '%2'. Check the SQLServerAgent registry ...
  75. Failed to send request for file '%1!s!' to the '%2!s!' primary database for the local secondary database. Resuming the database ...