SQL Server 2012

  1. Failed to connect because the federation distribution value is invalid. To connect to the federation member, provide the ...
  2. Failed to connect by using the specified user name and password. Verify that the user name and password are valid, and that ...
  3. Failed to connect to analysis services server database using the '{0}' connection manager. Check that the connection manager ...
  4. Failed to connect to DQS server the connection manager '{0}' as a result of the following value: A connection could not be ...
  5. Failed to connect to DQS using the connection manager '{0}' as a result of the following value: A connection could not be ...
  6. Failed to connect to the SQL Server Analysis Services database using the connection manager "{0}". Verify that the connection ...
  7. Failed to convert a type in the configuration "%1!s!" for the package path "%2!s!". This happens when a configuration value ...
  8. Failed to convert the package connection mananager '{0}' to a project connection manager because '{0}' is not a valid stream ...
  9. Failed to create a new folder '{0}'. The caller does not have the required permission. Verify if you have enough access permissions ...
  10. Failed to create a new folder '{0}'. The directory specified by path is read-only. A new directory can only be created on ...
  11. Failed to create a new folder '{0}'. The specified path contains a colon character (:) that is not part of a drive label ...
  12. Failed to create a new folder '{0}'. The specified path contains one or more invalid characters like ASCII/Unicode characters ...
  13. Failed to create a new folder '{0}'. The specified path exceeds the system-defined maximum length. Paths must be less than ...
  14. Failed to create a new table '{1}' in database '{0}'. Check whether the table already exists, and have the database administrator ...
  15. Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter %1!s! and notification ...
  16. Failed to create an IDataAdapter object. This provider may not be fully supported with the Execute SQL Task. Error message ...
  17. Failed to create availability group '%1!s!', because a Windows Server Failover Cluster (WSFC) group with the specified name ...
  18. Failed to create availability group '%1!s!', because a Windows Server Failover Cluster (WSFC) group with the specified name ...
  19. Failed to create availability group '%1!s!'. The operation encountered SQL Server error %2!s! and has been rolled back. Check ...
  20. Failed to create availability group '%1!s!'. The operation encountered SQL Server error %2!s!. An attempt to roll back the ...
  21. Failed to create certificate context (error: %1!s!). This occurs in CPackage::put_CertificateObject or CPackage::LoadFromXML ...
  22. Failed to create the availability group. A SQL Server instance name could not be validated because the dynamic link library ...
  23. Failed to create the availability group. A SQL Server instance name could not be validated because the dynamic link library ...
  24. Failed to create the Windows Server Failover Clustering (WSFC) group with name '%1!s!' (Error code %2!s!). The WSFC service ...
  25. Failed to create the Windows Server Failover Clustering (WSFC) group with name '%1!s!'. The WSFC group with the specified ...
  26. Failed to create the Windows Server Failover Clustering (WSFC) registry subkey '%1!s!' (Error code %2!s!). The parent key ...
  27. Failed to create the Windows Server Failover Clustering (WSFC) resource with name '%1!s!' and type '%2!s!' (Error code %3!s!). ...
  28. Failed to create the Windows Server Failover Clustering (WSFC) resource with name '%1!s!' and type '%2!s!'. The resource ...
  29. Failed to create the Windows Server Failover Clustering (WSFC) resource with name '%1!s!'. The WSFC resource with the specified ...
  30. Failed to create, join or add replica to availability group '%1!s!', because node '%2!s!' is a possible owner for both replica ...
  31. Failed to decrypt a package that is encrypted with a user key. You may not be the user who encrypted this package, or you ...
  32. Failed to decrypt a project that is encrypted with a user key. You may not be the user who encrypted this project, or you ...
  33. Failed to decrypt a project that is encrypted with a user key. You may not be the user who encrypted this project, or you ...
  34. Failed to decrypt an encrypted XML node because the password was not specified or not correct. Package load will attempt ...
  35. Failed to decrypt an encrypted XML node because the password was not specified or not correct. Project load will attempt ...
  36. Failed to decrypt an encrypted XML node. Verify that the project was created by the same user. Project load will attempt ...
  37. Failed to decrypt protected connection string for server "%1!s!" with error 2!8.8X! "%3!s!". You may not be authorized to ...
  38. Failed to decrypt protected XML node "%1!s!" with error 2!8.8X! "%3!s!". You may not be authorized to access this information. ...
  39. Failed to decrypt sensitive data in a project with a password. The password was not specified, or is not correct. If the ...
  40. Failed to decrypt sensitive data in project with a user key. You may not be the user who encrypted this project, or you are ...
  41. Failed to decrypt sensitive data. Possibly the encryption key does not match or is inaccessible because of improper service ...
  42. Failed to decrypt sensitive data. Possibly the encryption key does not match or is inaccessible because of improper service ...
  43. Failed to decrypt the project. The symmetric key that was used to encrypt it may have been deleted. Delete the project and ...
  44. Failed to delete a resource in the WSFC cluster because the resource '%1!s!' is not offline. Delete the resource using the ...
  45. Failed to delete registry key '{0}' because the registry key has subkeys. The registry key has must not have any subkeys ...
  46. Failed to delete registry key '{0}' because the registry key has subkeys. The registry key must not have any subkeys in order ...
  47. Failed to delete rows from the systranschemas table. HRESULT = ' 1!s!'. The rows will be deleted the next time replication ...
  48. Failed to delete SQL Server instance name to Windows Server Failover Clustering node name map entry for the local availability ...
  49. Failed to delete the Windows Server Failover Clustering (WSFC) registry subkey '%1!s!' (Error code %2!s!). The parent key ...
  50. Failed to delete the Windows Server Failover Clustering (WSFC) registry value corresponding to name '%1!s!' (Error code %2!s!). ...
  51. Failed to delete the Windows Server Failover Clustering (WSFC) registry value corresponding to name '%1!s!', because a registry ...
  52. Failed to delete the WSFC cluster resource '%1!s!'. The error code is %2!s!. The WSFC service may not be running or may be ...
  53. Failed to designate the local availability replica of availability group '%1!s!' as the primary replica. The operation encountered ...
  54. Failed to destroy the Windows Server Failover Clustering group corresponding to availability group '%1!s!'. The operation ...
  55. Failed to determine if the Windows Server Failover Clustering (WSFC) service is in Force Quorum state. The prerequisite QFE ...
  56. Failed to determine the fully qualified domain name of the computer while composing the Service Principal Name (SPN). This ...
  57. Failed to determine the fully qualified domain name of the computer while initializing SSL support. This might indicate a ...
  58. Failed to drop a Windows Server Failover Clustering (WSFC) group with name or ID '%1!s!' (Error code %2!s!). The WSFC service ...
  59. Failed to encrypt or decrypt sensitive data in the '%{strRef/}' database because the encryption key is unavailable. One possible ...
  60. Failed to encrypt sensitive data. Possibly the encryption key is inaccessible because of improper service account change. ...
  61. Failed to encrypt sensitive data. Possibly the encryption key is inaccessible because of improper service account change. ...
  62. Failed to encrypt the project named '%1!s!'. The symmetric key may have been deleted. Delete the project and deploy it again. ...
  63. Failed to enque task to start CLR during SQL server startup. Error code: %1!s!. CLR will be started in an on-demand fashion. ...
  64. Failed to enqueue a task to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will ...
  65. Failed to enumerate the Windows Server Failover Clustering (WSFC) registry key (Error code %1!s!). The WSFC service may not ...
  66. Failed to enumerate the Windows Server Failover Clustering (WSFC) resources (Error code %1!s!). The WSFC service may not ...
  67. Failed to enumerate Windows Server Failover Clustering (WSFC) objects (Error code %1!s!). The WSFC service may not be running ...
  68. Failed to enumerate Windows Server Failover Clustering (WSFC) registry value (Error code %1!s!). The WSFC service may not ...
  69. Failed to establish connection with report server. Verify the server URL is correct or review ULS logs for more information. ...
  70. Failed to evaluate the filter procedure or computed column. Cannot find the column offset information for column ID %1!s!, ...
  71. Failed to execute IS server package because of error 1!8.8X!. Server: %2!s!, Package path: %3!s!, Environment reference Id: ...
  72. Failed to execute MDX. You can *$*invoke error message box*$* for more information. *$*Click here*$* to hide this message. ...
  73. Failed to execute the HREPL.%1!s! request to Oracle Publisher '%2!s!'. Verify that the Oracle package code exists on the ...
  74. Failed to find a DWORD property (property name '%1!s!') of the Windows Server Failover Clustering (WSFC) (Error code %2!s!). ...
  75. Failed to find a DWORD property (property name '%1!s!') of the Windows Server Failover Clustering (WSFC) resource with ID ...