UI Translation

SQL Server 2012

  1. The Merge Agent was unable to synchronize the row due to one or more unanticipated errors in the batch of changes. When troubleshooting, ...
  2. The Merge Agent was unable to update information about the last synchronization at the Subscriber. Ensure that the subscription ...
  3. The merge process cleaned up %1!d! row(s) in MSmerge_genhistory, %2!d! row(s) in MSmerge_contents, and %3!d! row(s) in MSmerge_tombstone. ...
  4. The merge process could not access row data at the '%1'. When troubleshooting, restart the synchronization with verbose history ...
  5. The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the ...
  6. The merge process could not delete retry information at the Publisher on tempdb. This may be due to too much activity on ...
  7. The merge process could not enumerate changes at the '%1'. When troubleshooting, restart the synchronization with verbose ...
  8. The merge process could not enumerate deletions at the '%1'. Troubleshoot by restarting the synchronization with verbose ...
  9. The merge process could not initialize the subscription. Ensure that the subscription registration exists at the publisher, ...
  10. The merge process could not perform retention-based metadata cleanup in database '%1'. If this failure continues, try increasing ...
  11. The merge process could not query the last generation received from the Publisher. If this failure persists, reinitialize ...
  12. The merge process could not register an alternate synchronization partner. Troubleshoot by restarting the synchronization ...
  13. The merge process could not remove the registration for an alternate synchronization partner. When troubleshooting, restart ...
  14. The merge process could not replicate one or more INSERT statements to the '%1'. A stored procedure failed to execute. Troubleshoot ...
  15. The merge process could not replicate one or more UPDATE statements to the '%1' because a stored procedure failed to execute. ...
  16. The merge process could not retrieve column information for table '%1.%2'. Verify that you have sufficient privileges on ...
  17. The merge process could not retrieve generation information at the '%1'. If this failure persists, reinitialize the subscription. ...
  18. The merge process could not retrieve schema information from the Publisher. When troubleshooting, use SQL Profiler or restart ...
  19. The merge process could not retrieve the last generation received from the Publisher. If this failure persists, reinitialize ...
  20. The merge process could not store conflict information for article '%1'. Check the publication properties to determine where ...
  21. The merge process could not store delete conflict information for an article. Check the publication properties to determine ...
  22. The merge process could not update the last generation received from the Publisher. If this failure persists, reinitialize ...
  23. The merge process could not update the last sent generation sent to the Publisher. If this failure persists, reinitialize ...
  24. The merge process detected a mismatch while evaluating the subscriber partition validation expression. The problem can be ...
  25. The merge process failed because it detected a mismatch between the replication metadata of the two replicas, such that some ...
  26. The merge process failed to enumerate changes in articles with parameterized row filters. If this failure continues, increase ...
  27. The merge process failed to execute a query because the query timed out. If this failure continues, increase the query timeout ...
  28. The merge process failed to get correct information about the Interactive Resolver component from the registry. Verify that ...
  29. The merge process failed when obtaining a new identity range for the subscriber, or failed to determine if the subscriber ...
  30. The merge process timed out while making a connection. Increase the login timeout for this process (-LoginTimeOut). When ...
  31. The merge process was unable to access metadata at the '%1' that was needed to retry an operation. When troubleshooting, ...
  32. The merge process was unable to access row metadata at the '%1'. When troubleshooting, restart the synchronization with verbose ...
  33. The merge process was unable to change generation history at the '%1'. When troubleshooting, restart the synchronization ...
  34. The merge process was unable to create a new generation at the '%1'. Troubleshoot by restarting the synchronization with ...
  35. The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may ...
  36. The merge process was unable to perform data validation on article '%1'. Check for SQL Server errors in the Windows application ...
  37. The merge process was unable to verify the existence of a generation at the '%1'. If this failure persists, reinitialize ...
  38. The MERGE statement attempted to UPDATE or DELETE the same row more than once. This happens when a target row matches more ...
  39. The message cannot be sent because the message type '%1!s!' is marked SENT BY INTITIATOR in the contract, however this service ...
  40. The message cannot be sent because the message type '%1!s!' is marked SENT BY TARGET in the contract, however this service ...
  41. The message cannot be sent because the service queue '%1!s!' associated with the dialog is currently disabled and retention ...
  42. The message could not be delivered because it could not be classified. Enable broker message classification trace to see ...
  43. The message received was sent by a Target service, but the message type '%1!s!' is marked SENT BY INITIATOR in the contract. ...
  44. The message received was sent by the initiator of the conversation, but the message type '%1!s!' is marked SENT BY TARGET ...
  45. The message string being posted by the managed error infrastructure contains a bad format specification. This is an internal ...
  46. The message with default language Id of destination is not present in destination and hence attempting to transfer the same ...
  47. The message {0}:{1} on conversation {2}:{3} from service {4} and broker instance {5} to service {6} and broker instance {7} ...
  48. The metadata could not be determined because every code path results in an error; see previous errors for some of these. ...
  49. The metadata could not be determined because remote metadata discovery failed for statement '%1!s!' in procedure '%2!s!'. ...
  50. The metadata could not be determined because statement '%1!s!' contains dynamic SQL. Consider using the WITH RESULT SETS ...
  51. The metadata could not be determined because statement '%1!s!' in procedure '%2!s!' contains dynamic SQL. Consider using ...
  52. The metadata could not be determined because statement '%1!s!' in procedure '%2!s!' does not support metadata discovery. ...
  53. The metadata could not be determined because statement '%1!s!' in procedure '%2!s!' invokes a CLR procedure. Consider using ...
  54. The metadata could not be determined because statement '%1!s!' in procedure '%2!s!' invokes an extended stored procedure. ...
  55. The metadata could not be determined because statement '%1!s!' in procedure '%2!s!' uses an undeclared parameter in a context ...
  56. The metadata could not be determined because statement '%1!s!' invokes a CLR procedure. Consider using the WITH RESULT SETS ...
  57. The metadata could not be determined because statement '%1!s!' uses an undeclared parameter in a context that affects its ...
  58. The metadata could not be determined because the statement '%1!s!' in procedure '%2!s!' is not compatible with the statement ...
  59. The metadata could not be determined because the statement '%1!s!' in procedure '%2!s!' is not compatible with the statement ...
  60. The metadata could not be determined because the statement '%1!s!' in the main batch is not compatible with the statement ...
  61. The metadata discovery operation {0} returned invalid content. Verify that the connection string and permissions are correct. ...
  62. The metadata element reference starting with '{0}' cannot be resolved due to too many levels of indirection. The last metadata ...
  63. The metadata file name "%1!s!" is invalid. Verify that the file exists and that the SQL Server service account has access ...
  64. The metadata for the statically linked %{typename/}, with the name of '%{name/}', cannot be verified against the source object. ...
  65. The metadata of the following output columns does not match the metadata of the external columns with which the output columns ...
  66. The method "{0}" in class "{1}" marked as a server-level trigger cannot be auto deployed because server-level trigger deployment ...
  67. The method "{0}" in class "{1}" marked as a table-valued function must define a table definition in the SqlFunction attribute. ...
  68. The method '%1!s!' in class '%2!s!' in assembly '%3!s!' has some invalid parameter declaration for parameter number %4!s!. ...
  69. The method was called on the wrong buffer. Buffers that are not used for component output do not support this operation. ...
  70. The method {0} on type {1} in extension with Id {2} could not be converted to a TestCondition delegate for use in the condition ...
  71. The method {0} on type {1} in extension with Id {2} could not be converted to a TestCondition delegate for use in the condition ...
  72. The method {0} used as a CreateCustomModifiers raised an exception when it was called. The modifiers from the source could ...
  73. The Microsoft .NET Framework 2.0 or 4.0 must be installed on your computer before you can install ProductShortName]. Please ...
  74. The Microsoft .NET Framework 3.5 or 4.0 must be installed on your computer before you can install ProductShortName]. Please ...
  75. The Microsoft .NET Framework 3.5 SP1 must be installed on your computer before you can install ProductShortName]. Microsoft ...
Deutsch (Deutschland)
German (Germany) Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean Português
Portuguese Русский
Russian English
English (United States)