SQL Server 2012

  1. Error '%1!s!' occurred during full-text index population for table or indexed view '%2!s!' (table or indexed view ID '%3!s!', ...
  2. Error 1!8.8X!. Failed to create an instance of empty child package. The Distributed Component Object Model (DCOM) configuration ...
  3. Error 1!8.8X!. Failed to get an XML document from the Document Object Model. The package data or your DOM installation might ...
  4. Error 1!8.8X!. Failed to load the package "%2!s!" from SQL Server "%3!s!". Make sure that the package exists on the instance ...
  5. Error 1!8.8X!. Failed to set properties on the XML Document Object Model object. Your DOM installation might be corrupted. ...
  6. Error 1!8.8X!. Unable to access the package file, "%2!s!". Make sure that the file exists and that you have permission to ...
  7. Error 1!s! (NT status code) was encountered when SQL Server attempts to change the logging mode of Transaction File System ...
  8. Error 1!s! (NT status code) was encountered when SQL Server attempts to retrieve '%2!s!' from the Transaction File System ...
  9. Error accessing the Availability Groups manager. The local Availability Groups manager has not been initialized. Wait until ...
  10. Error and truncation dispositions were not reviewed. Make sure this component is configured to redirect rows to error outputs, ...
  11. Error applying patch to file 2]. It has probably been updated by other means, and can no longer be modified by this patch. ...
  12. Error assigning namespace to the variable. The namespace "System" is reserved for system use. This error happens when a component ...
  13. Error caused by conflicting property settings. Both the AllowAppend property and the ForceTruncate property are set to TRUE. ...
  14. Error caused by conflicting property settings. The "%1!s!" has both the AllowAppend property and the ForceTruncate property ...
  15. Error during Backup/Restore: ABFDumper functionality is not supported for the backup files created by AS2005 server. File ...
  16. Error during Backup/Restore: the backup file '%{fileName/}' stored inside backup storage is damaged: CRC validation failed. ...
  17. Error during Backup/Restore: the backup file '%{fileName/}' stored inside backup storage is damaged: EOF validation failed. ...
  18. Error during deserialization of column '%{strColumnName/}': column segment map must be deserialized and instantiated before ...
  19. Error during instantiation '%{InstObjClass/}' object of name '%{strObjectName/}': expected parent object's class is '%{ExpectedParentObjClass/}', ...
  20. Error during instantiation '%{InstObjClass/}' object: object name can not be empty for serializable data objects. Possible ...
  21. Error during processing of {0}' report parameter. The {1} property of the report parameter {0}' references the value of field ...
  22. Error during Restore/Synchronization: the backup metadata is damaged, so the operation cannot locate or process the '%{node/}' ...
  23. Error during Restore/Synchronization: the backup store directory entry is damaged, so the operation cannot locate or process ...
  24. Error during Restore/Synchronization: the backup store directory is damaged, so the operation cannot locate or process the ...
  25. Error during Restore/Synchronization: the backup store header is damaged, so the operation cannot locate or process the '%{node/}' ...
  26. Error during Restore/Synchronize: The backup metadata is damaged, so the operation cannot locate or process node %{node/}. ...
  27. Error during string decryption. The operating system returned error %1!u!. Please take corrective action based on the operating ...
  28. Error during string encryption. The operating system returned error %1!u!. Please take corrective action based on the operating ...
  29. Error during synchronization: Cannot synchronize objects on instances with different file storage mode settings, such as ...
  30. Error during synchronization: Client is trying to access the '%{file/}' file that is not included in the synchronization ...
  31. Error during synchronization: The Synchronize command failed while synchronizing empty file list (first stage is missing). ...
  32. Error during Synchronize: the synchronization LOG metadata is damaged, can't locate and/or process node %{node/}, file %{file/}. ...
  33. Error evaluating article synchronization object after column drop. The filter clause for article '%1!s!' must not reference ...
  34. Error getting or setting an array value. The type "%1!s!" is not allowed. This occurs when loading an array into a variable. ...
  35. Error happened when calling back to server, this may be caused by server out of memory or previous error in callback function. ...
  36. Error happened while loading table data. Possible cause is: corrupt variant store data file for one of the table columns. ...
  37. Error happened while loading table metadata, node '%{nodename/}'. Possible causes are: incorrect xsi:type specified in this ...
  38. Error happened while loading table metadata. Possible causes are: missing or improperly specified property in the XMObject ...
  39. Error happened while loading table metadata. Possible causes are: unknown class name '%{strClassName/}' is specified for ...
  40. Error happens while trying to read the Aotm Service Document. Please make sure that the given URL is valid and it points ...
  41. Error in mapping SQL Server performance object/counter indexes to object/counter names. SQL Server performance counters are ...
  42. Error in parsing the Paxos tag from the Windows Server Failover Clustering (WSFC) registry hive. The WSFC registry hive might ...
  43. Error in retrieving extended recovery forks from the primary replica. The extended-recovery-fork stack changed while being ...
  44. Error in the specified data source file. The file does not have the right format or cannot be validated. If this report uses ...
  45. Error initializing HTTP session with proxy "%1!s!". This error can occur when an invalid proxy was specified. HTTP connection ...
  46. Error loading from XML. No further detailed error information can be specified for this problem because no Events object ...
  47. Error number %1!s! in the THROW statement is outside the valid range. Specify an error number in the valid range of 50000 ...
  48. Error number, %1!s!, occurred in the procedure, '%2!s!', at line number, %3!s!. The error message was: '%4!s!' The error ...
  49. Error occured while loading extensions from assembly '{0}'. The extension information must be corrected before it can be ...
  50. Error occurred because the output file already exists and the WriteOption is set to Create Once. Set the WriteOption property ...
  51. Error occurred while deleting an old file or creating a file with same name. Check the controller and client error log for ...
  52. Error occurred while loading product mapping from resource '{0}'. The product information needs to be corrected before it ...
  53. Error occurred while loading the provider mapping from assembly '{0}'. The provider information must be corrected before ...
  54. Error parsing '{0}'. Make sure string constants are enclosed in single quotes and facet properties are prefixed with '@' ...
  55. Error parsing '{0}'. Policy expressions require the first argument of DATEADD and DATEPART functions to be in single quotes. ...
  56. Error processing client certificate. This error can occur when the client certificate provided was not found in the Personal ...
  57. Error processing XML data type method '%1!s!'. The following SET options required by XML data type methods are not set: '%2!s!'. ...
  58. Error saving report. Verify that the path exists, the file name contains only valid characters, and you have the right permissions. ...
  59. Error severity levels greater than %1!s! can only be specified by members of the sysadmin role, using the WITH LOG option. ...
  60. Error using a read-only variable "%1!s!" in an assignment expression. The expression result cannot be assigned to the variable ...
  61. Error using same name for different custom events. The custom event "%1!s!" was defined differently by different children ...
  62. Error while enabling Windows feature : {0}, Error Code : {1} , Please try enabling Windows feature : {0} from Windows management ...
  63. Error while enabling Windows feature : {0}, Please try enabling Windows feature : {0} from Windows management tools and then ...
  64. Error while trying to create a DbParameter. This provider may not be fully supported with the Execute SQL Task. Exception: ...
  65. Error while trying to enable integration with Data Quality Services. Please verify you have appropriate permissions to access ...
  66. Error: %1!s!, Severity: %2!s!, State: %3!s!. (Params:%4!s!). The error is printed in terse mode because there was error during ...
  67. Error: All Full-text populations in progress, for catalog '%1!s!' ('%2!s!') in database '%3!s!' ('%4!s!') were terminated ...
  68. Error: Failed to initialize full-text %1!s! population for table or indexed view '%2!s!', database '%3!s!' (table or indexed ...
  69. Error: Failed to parse input XML. Could not parse Database type specified.In USC make sure that the database names in the ...
  70. Error: Failed to parse input XML. Could not parse Server type specified.In USC make sure that -S option matches the server ...
  71. Error: Failed to reinitialize full-text %1!s! population after a temporary failure for table or indexed view '%2!s!', database ...
  72. Error: Failed to resume full-text %1!s! population for table or indexed view '%2!s!' in database '%3!s!' (table or indexed ...
  73. Error: Full-text %1!s! population for table or indexed view '%2!s!' (table or indexed view ID '%3!s!', database ID '%4!s!') ...
  74. ERROR: The Execute Package Utility requires Management Tools - Basic or Business Intelligence Studio to be installed by the ...
  75. ERROR: The Package Installation Wizard requires Integration Services or Management Tools - Basic to be installed by the SQL ...