Windows 7

  1. The member {0} could not be contacted to get current schedule status. The error returned was "{1}" Do you still want to attempt ...
  2. The member {0} has one or more primary memberships. If this member is deleted then you must manually configure new primary ...
  3. The member {0} is the last valid on demand replication source for one or more downstream members. Deleting this member would ...
  4. The membership {0} cannot be enabled. This membership is marked to replicate on demand, but failed to pass one or more validations: ...
  5. The membership {0} cannot be modified to use shared staging. Shared staging is not supported on memberships that are part ...
  6. The membership {0} cannot replicate on demand since there are no valid upstream neighbors in the connection topology, that ...
  7. The memory block page for the virtualization infrastructure driver cannot be mapped because the page map limit has been reached. ...
  8. The memory mapped I/O for this page range no longer exists. Restarting the virtual machine may fix the problem. If the problem ...
  9. The memory page at physical address %1 has encountered multiple corrected hardware error events. As a result it will no longer ...
  10. The Memory performance object consists of counters that describe the behavior of physical and virtual memory on the computer. ...
  11. The menu command you select can be applied to any of the items in the details pane. When you run the task, you must select ...
  12. The message at which the cursor is currently pointing was removed from the queue by another process or by another call to ...
  13. The message cannot be delivered due to a configuration error. The MTA has been disabled yet the recipient requires the MTA ...
  14. The message could not be moved to deadletter queue %1. Deadletter queues should not require privacy of messages. The message ...
  15. The message could not be moved to deadletter queue %1. The deadletter queue is authenticated and the authenticity of the ...
  16. The message could not be moved to deadletter queue %1. The deadletter queue needs to be transactional. The message will be ...
  17. The message could not be moved to deadletter queue %3. Check that queue exists and users have permissions to send. The message ...
  18. The message could not be sent because its size exceeded the server's limit. You can use the option, located in Tools | Accounts ...
  19. The message could not be sent. The authentication setting might not be correct for your outgoing e-mail SMTP server. For ...
  20. The message has been sent, but the connected workstation has not received it. The workstation is running an unsupported version ...
  21. The message is currently being processed under a transaction. Till the transaction outcome is determined, the message cannot ...
  22. The message might have been one that required no action, such as a quick status notification. Windows will notify you if ...
  23. The message queue for the virtualization infrastructure driver has been closed. Restarting the virtual machine may fix the ...
  24. The message queue for the virtualization infrastructure driver is full and cannot accept new messages. Restarting the virtual ...
  25. The Message Queuing directory service failed to update the directory service flag in Active Directory Domain Services at ...
  26. The Message Queuing directory service failed to update the directory service flag in Active Directory Domain Services during ...
  27. The Message Queuing directory service is not running as a local system. To get the directory service functionality, you need ...
  28. The Message Queuing DLL or the entry point in that DLL for the specified procedure cannot be found. You can turn on tracing ...
  29. The Message Queuing resource failed to come online. The Message Queuing resource depends on the network name resource with ...
  30. The Message Queuing Security page cannot be displayed. Message Queuing may not be properly installed. Please reinstall Message ...
  31. The Message Queuing serivce performance counter data are not available. The performance counter module failed to initialize. ...
  32. The Message Queuing server cannot determine if the local domain controller is trusted for delegation. This may indicate a ...
  33. The Message Queuing service cannot communicate with other computers, because the RPC interface cannot use the TCP/IP protocol. ...
  34. The Message Queuing service cannot communicate with other computers, because the select API for socket failed. Error %1: ...
  35. The Message Queuing service cannot join the '%1' Windows NT 4.0 domain. The Active Directory Domain Services Integration ...
  36. The Message Queuing service cannot start because a queue is in an inconsistent state. For more information, see Microsoft ...
  37. The Message Queuing service cannot start. A connection with the Distributed Transaction Coordinator cannot be established. ...
  38. The Message Queuing service cannot start. The Active Directory Domain Services interface cannot be initialized. Error %1: ...
  39. The Message Queuing service cannot start. The checkpoint files cannot be recovered. To start the Message Queuing service ...
  40. The Message Queuing service cannot start. The internal private queue '%3' cannot be initialized. If the problem persists, ...
  41. The Message Queuing service cannot start. The log file cannot be recovered. To start the Message Queuing service without ...
  42. The Message Queuing service cannot start. The registry value '\HKLM\SOFTWARE\Microsoft\MSMQ\Parameters\%3' cannot be retrieved ...
  43. The Message Queuing service cannot start. The registry value '\HKLM\SOFTWARE\Microsoft\MSMQ\Parameters\%3' cannot be written ...
  44. The Message Queuing service has to be restarted for the changes to take effect. Do you want to restart the Message Queuing ...
  45. The Message Queuing service is not online with Active Directory Domain Services, since the service properties cannot be retrieved ...
  46. The Message Queuing service is not online with Active Directory Domain Services. The MSMQ Configuration object (msmq) ID ...
  47. The Message Queuing service on the computer hosting the queue may be offline, or a connection with Active Directory Domain ...
  48. The Message Queuing service on this computer is now represented by a new MSMQ-Configuration object. As a result, all transactional ...
  49. The Message Queuing service rejects incoming messages when it is unable to check whether the sender is allowed access to ...
  50. The Message Queuing service resource cannot bind to the cluster IP address. This prevents the Message Queuing resource from ...
  51. The Message Queuing service was unable to obtain the properties of the msmq (MSMQ Configuration) object from Active Directory ...
  52. The Message Queuing service will not join the %1 domain. An MSMQ Configuration (msmq) object exists in the new domain with ...
  53. The Message Queuing Triggers Configuration page cannot be displayed. Message Queuing Triggers may not be properly installed. ...
  54. The message sender has requested a receipt to indicate that you have read this message. Would you like to send a receipt? ...
  55. The message sender has requested a response to indicate that you have read this message. Would you like to send a receipt? ...
  56. The message will be sent as a regular e-mail message using only the default character set. Any text not in the default character ...
  57. The message will be sent as a Unicode message. All character set information will be retained. However, if the recipient's ...
  58. The message(s) cannot be copied because not all of the bodies have been downloaded. To perform the copy, first uncheck Work ...
  59. The message(s) cannot be moved because not all of the bodies have been downloaded. To perform the move, first uncheck Work ...
  60. The MessageOriented property indicates whether the protocol is message-oriented. A message-oriented protocol uses packets ...
  61. The Messages Received Delta performance counter shows the number of new cluster messages received on the network since the ...
  62. The Messages Sent Delta performance counter shows the number of new cluster messages sent over the network since the last ...
  63. The Messages Sent Delta performance counter shows the number of new cluster MRR messages sent over the network since the ...
  64. The metadata cleanup for the requested server should happen on an Active Directory Domain Controller (AD DC) in the same ...
  65. The Metadata IO Delta performance counter shows the number of new metadata operations that were performed against the volume ...
  66. The metadata of element %1 is too large. The maximum allowed size is 2048 bytes. Reduce the size of the metadata of element ...
  67. The metadata of element %1 would cause the total published metadata to be more than 32k, which is the maximum allowable size ...
  68. The metadata store cannot be opened because it has been updated by synchronization components that are newer than those installed ...
  69. The Metadata Store does not support nested transactions (a new transaction was attempted while another was still active). ...
  70. The Metadata Store does not support querying for multiple columns which have not been specified by a CUSTOM_FIELDS_INDEX. ...
  71. The Metadata Store InitializeReplicaMetadata method only supports columns of maximum length 4000 and binary columns of maximum ...
  72. The Metadata Store InitializeReplicaMetadata method requires an empty array to be passed as a null value with a count of ...
  73. The Metadata Store InitializeReplicaMetadata method requires CUSTOM_FIELDS_INDEX to have at least one custom field name. ...
  74. The Metadata Store InitializeReplicaMetadata method requires the replica ID to be large than 2 bytes and smaller than the ...
  75. The Metadata Store method does not allow change unit versions on a tombstoned item or an item that already has a change version ...