.NET Framework

  1. There is already a listener on IP endpoint {0}. Make sure that you are not trying to use this endpoint multiple times in ...
  2. There is already a listener on IP endpoint {0}. This could happen if there is another application already listening on this ...
  3. There is already a pending discovery operation associated with a MessageId '{0}'. Please specify a different value of MessageId ...
  4. There is already a read in progress for the pipe. Wait for the first operation to complete before attempting to read again. ...
  5. There is already a write in progress for the pipe. Wait for the first operation to complete before attempting to write again. ...
  6. There is already configuration information for some of these assemblies. Are you sure you want to overwrite the existing ...
  7. There is already configuration information for {0}. Are you sure you want to overwrite the existing configuration information? ...
  8. There is already one outstanding '{0}' call for this WebSocket instance. ReceiveAsync and SendAsync can be called simultaneously, ...
  9. There is an incomplete parameter in this path segment: '{0}'. Check that each '{' character has a matching '}' character. ...
  10. There is more than one XmlnsCompatibleWithAttribute in assembly '{0}' for OldNamespace '{1}'. Remove the extra attribute(s). ...
  11. There is no build provider registered for the extension '{0}'. You can register one in the section in machine.config or web.config. ...
  12. There is no compatible TransportManager found for URI '{0}'. This may be because that you have used an absolute address which ...
  13. There is no compatible TransportManager found for URI '{0}'. This may be because that you have used an absolute address which ...
  14. There is no compatible TransportManager found for URI '{0}'. This may be because you have used an absolute address that points ...
  15. There is no compatible TransportManager found for URI '{0}'. This may be because you have used an absolute address that points ...
  16. There is no context attached to incoming message for the service and the current operation is not marked with "CanCreateInstance ...
  17. There is no context attached to the incoming message for the service and the current operation is not marked with "CanCreateInstance ...
  18. There is no correlation handle available to initialize the QueryCorrelationInitializer. This is because there is no explicit ...
  19. There is no correlation handle available to initialize the QueryCorrelationInitializer. This is because there is no explicit ...
  20. There is no defined ordering between fields in multiple declarations of partial class or struct '%1!ls!'. To specify an ordering, ...
  21. There is no disk in drive 2]. Please insert one and click Retry, or click Cancel to go back to the previously selected volume. ...
  22. There is no disk in drive 2]. Please insert one and click Retry, or click Cancel to return to the browse dialog and select ...
  23. There is no host attached to this service. Call AttachHost to provide a valid host that can provide a request to process. ...
  24. There is no metadata information available for the proxy type for '{0}'. This exception can be caused when a proxy type for ...
  25. There is no operation listening for {0} , but there is an operation listening for {1} , so you are being redirected there. ...
  26. There is no pending asynchronous write on this stream. Ensure that there is pending write on the stream or verify that the ...
  27. There is no printer installed on your system. Make sure you have at least one printer installed in the "Printers and Faxes" ...
  28. There is no printer installed on your system. Make sure you have at least one printer installed in the "Printers and Faxes" ...
  29. There is no public default constructor for '{0}'. This might be referenced by a '{0}' tag, or it might be the default type ...
  30. There is no SecurityContextSecurityToken with context-id={0} (generation-id={1}) registered with SecurityContextSecurityTokenAuthenticator. ...
  31. There is no SecurityContextSecurityToken with context-id={0} (no key generation-id) registered with SecurityContextSecurityTokenAuthenticator. ...
  32. There is not enough disk space on the volume '[2]' to continue the install with recovery enabled. 3 KB are required, but ...
  33. There is not enough disk space on your drive for the new files to be uncompressed and installed. Please run this application ...
  34. There is not enough information to call IEnumerable.GetEnumerator on a Windows Runtime object, please cast the object to ...
  35. There is not enough information to cast a Windows Runtime object to IEnumerable, please cast the object to IEnumerable first. ...
  36. There is not enough space available on the selected installation disk. Free some disk space or select a different installation ...
  37. There was a conflict between two files from the redist folder files going to the same target path "{0}" between the "{1}" ...
  38. There was a conflict between two redist files going to the same target path "{0}" within the "{1}" SDK. Choosing "{2}" over ...
  39. There was a conflict between two references with the same file name between the "{0}" and "{1}" SDKs. Choosing "{2}" over ...
  40. There was a conflict between two references with the same file name resolved within the "{0}" SDK. Choosing "{1}" over "{2}" ...
  41. There was a failure initializing profiling API attach infrastructure. This process will not allow a profiler to attach. HRESULT: ...
  42. There was a mismatch between the number of supplied arguments and the number of expected arguments. Specifically, the argument ...
  43. There was a problem accessing file information. This may be caused by missing file(s) or folder(s), unauthorized file(s) ...
  44. There was a problem loading the XSD documents provided: a reference to a schema element with name '{0}' and namespace '{1}' ...
  45. There was a problem loading the XSD documents provided: a reference to a schema type with name '{0}' and namespace '{1}' ...
  46. There was a problem reading the MetadataSet argument: a MetadataSection instance with identifier '{0}' and dialect '{1}' ...
  47. There was a problem unregistering the '{0}' culture. The file may be in use or you may not have the appropriate permission. ...
  48. There was a validation error on a schema generated during export: Source: {0} Line: {1} Column: {2} Validation Error: {3} ...
  49. There was a validation error on a schema generated during export: Source: {0} Line: {1} Column: {2} Validation Error: {3} ...
  50. There was an error creating a temporary file that is needed to complete this installation.{ Folder: 3]. System error code: ...
  51. There was an error creating the security key identifier clause from the security token XML. Please see the inner exception ...
  52. There was an error deserializing the security key identifier clause XML. Please see the inner exception for more details. ...
  53. There was an error during asynchronous processing. Unique state object is required for multiple asynchronous simultaneous ...
  54. There was an error executing the query. Please check the syntax of the command and if present, the types and values of the ...
  55. There was an error loading app.config. Since the document being loaded uses Dynamic Properties, the config file must be valid. ...
  56. There was an error opening the queue. Ensure that MSMQ is installed and running, the queue exists and has proper authorization ...
  57. There was an error processing type '{0}'. Type member '{1}' declared in '{2}' is missing required '{3}' property. If one ...
  58. There was an error reading the file located at {0}. Please make sure that a valid wave file exists at the specified location. ...
  59. There was an error while trying to deserialize parameter {0}:{1}. The InnerException message was '{2}'. Please see InnerException ...
  60. There was an error while trying to serialize parameter {0}:{1}. The InnerException message was '{2}'. Please see InnerException ...
  61. There was an internal failure in the profiling API detach infrastructure. The profiler will not be able to be detached. Error ...
  62. There was an unknown error processing the expression "{0}". Processing the expression text did not cause an exception but ...
  63. There was no channel actively listening at '{0}'. This is often caused by an incorrect address URI. Ensure that the address ...
  64. There was no channel actively listening at '{0}'. This might be because the service is closed due to application recycling. ...
  65. There was no endpoint listening at {0} that could accept the message. This is often caused by an incorrect address or SOAP ...
  66. There were character conversion errors while saving the project file '%1'. Save the project file in Unicode or UTF-8 format ...
  67. These fields are only effective when the "Use Application Manifest for Trust Information" option is selected in the Application ...
  68. These settings will not appear valid for the current user. Please re-run the wizard as a user to incorporate these changes ...
  69. This '{0}' object cannot be used to generate configuration because it was created with the constructor that takes a '{1}' ...
  70. This action could not be completed because multiple device filters that share the same name exist in this project's Web.config ...
  71. This action could not be completed because there are multiple styles defined in this style sheet that share the same name. ...
  72. This action will reset DataPager fields and properties and you will lose customizations you have made to DataPager. Would ...
  73. This action will reset ListView keys, properties, and templates and you will lose customizations you have made to ListView. ...
  74. This activity cannot be invoked because it was not opened by an overload of Invoke which takes an IDictionary of string and ...
  75. This activity does not correctly handle updates when it's inside an activity implementation. It attempted to save original ...