.NET Framework

  1. The service does not expose IProjectionProvider interface which is required when projection is requested. Request could not ...
  2. The service does not expose IProjectionProvider interface which is required when top level results are paged. Request could ...
  3. The service endpoint failed to listen on the URI '{0}' because access was denied. Verify that the current user is granted ...
  4. The service endpoint failed to listen on the URI '{0}' because access was denied. Verify that the current user is granted ...
  5. The service endpoint failed to listen on the URI '{0}' because the shared memory section was not found. Verify that the '{1}' ...
  6. The service instance was released on the completion of the transaction '{0}' because the ReleaseServiceInstanceOnTransactionComplete ...
  7. The service operation '{0}' that belongs to the contract with the '{1}' name and the '{2}' namespace does not allow impersonation. ...
  8. The service type provided could not be loaded as a service because it does not have a default (parameter-less) constructor. ...
  9. The Service with name '{0}' could not be constructed because the application does not have permission to construct the type: ...
  10. The service {0} is required but could not be found. If you have removed this service ensure that you provide a replacement. ...
  11. The ServiceCredentials cannot be added to the binding parameters because the binding parameters already contains a SecurityCredentialsManager ...
  12. The ServiceDebugBehavior Help Page is enabled at a relative address and cannot be created because there is no base address. ...
  13. The ServiceEndpoint with name '{0}' could not be exported to WSDL because the Binding property is null. To fix this, set ...
  14. The ServiceHost close operation timed out after {0}. This could be because a client failed to close a sessionful channel ...
  15. The ServiceHost must be configured with either a serviceType or a serviceInstance. Both of these values are currently null. ...
  16. The ServiceMetadataExtension instance could not be added to the ServiceHost instance because it has already been added to ...
  17. The ServiceMetadataExtension instance could not be removed from the ServiceHost instance because it has already been added ...
  18. The ServiceMetadataExtension instance could not be removed from the ServiceHost instance because it has not been added to ...
  19. The session requirements of the contracts are inconsistent. All COM contracts in a service must have the same session requirement. ...
  20. The Session value '{0}' is invalid. Please specify 'CurrentSession','ServiceSession' or a valid non-negative Windows Session ...
  21. The settings managed through the Debugging and Tracing feature of the Application tab exist within the , , and sections of ...
  22. The Settings property has invalid value. Set the Settings property to either an empty string or "Assembly references and ...
  23. The settings that are managed through the Application Settings feature of the Application tab exist in the section of the ...
  24. The settings that are managed through the SMTP Settings feature of the Application tab exist within the section of the Web.config ...
  25. The SetTransactionComplete method was called in the operation '{0}' on contract '{1}' when TransactionAutoComplete was set ...
  26. The SetTransactionComplete method was wrongly called more than once in the operation '{0}' on contract '{1}'. The SetTransactionComplete ...
  27. The setup must update files or services that cannot be updated while the system is running. If you choose to continue, a ...
  28. The setup was unable to automatically close all requested applications. Please ensure that the applications holding files ...
  29. The shutdown indicator could not be written to the pipe. The application on the other end of the pipe may not be listening ...
  30. The shutdown indicator was not received from the pipe. The application on the other end of the pipe may not have sent it. ...
  31. The signature of the MethodBuilder can no longer be modified because an operation on the MethodBuilder caused the methodDef ...
  32. The signing token {0} has no keys. The security token is used in a context that requires it to perform cryptographic operations, ...
  33. The simple identifier '{0}' must contain basic Latin characters only. To use UNICODE characters, use an escaped identifier. ...
  34. The Site membership condition is true for all assemblies that come from the site name below. Assemblies that meet this membership ...
  35. The site name is the portion of the URL starting after the protocol and before the path. Site names do not include port numbers. ...
  36. The size must be greater than or equal to 0. If 0 is specified, the view extends from the specified offset to the end of ...
  37. The Skip operator is not supported for sequences containing sequences (with the exception of IGrouping under SQL Server 2005). ...
  38. The Skip Verification membership condition is true for all assemblies that request the right to skip verification. Assemblies ...
  39. The SOAP 1.1 encoding style is not supported for operations that use SOAP 1.2. Use the URI '{0}' to refer to the SOAP 1.2 ...
  40. The SOAP action specified on the message, '{0}', does not match the action specified in the content-type of the HttpRequestMessageProperty, ...
  41. The SOAP action specified on the message, '{0}', does not match the action specified on the HttpRequestMessageProperty, '{1}'. ...
  42. The socket connection was aborted because an asynchronous send to the socket did not complete within the allotted timeout ...
  43. The socket connection was aborted by your local machine. This could be caused by a channel Abort(), or a transmission error ...
  44. The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded ...
  45. The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded ...
  46. The socket transfer timed out after {0}. You have exceeded the timeout set on your binding. The time allotted to this operation ...
  47. The socket transfer timed out after {0}. You have exceeded the timeout set on your binding. The time allotted to this operation ...
  48. The socket was aborted because an asynchronous receive from the socket did not complete within the allotted timeout of {0}. ...
  49. The sort order and ordinal must either both be specified, or neither should be specified (SortOrder.Unspecified and -1). ...
  50. The SortDescriptions added are not valid. The probable solutions are to set the CanUserSort on the Column to false, or to ...
  51. The source '{0}' is not registered in log '{1}'. (It is registered in log '{2}'.) " The Source and Log properties must be ...
  52. The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please ...
  53. The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please ...
  54. The source installation package for the product 2 is out of sync with the client package. Try the installation again using ...
  55. The source query for this EntityCollection or EntityReference cannot be returned when the related object is in either an ...
  56. The source was not found, but some or all event logs could not be searched. To create the source, you need permission to ...
  57. The specified Activity definition contains multiple languages of expression activities that require compilation (languages ...
  58. The specified addressing scheme is invalid for this binding. The NetMsmqBinding scheme must be net.msmq. The MsmqIntegrationBinding ...
  59. The specified bookmark scope cannot be initialized with the identifier '{0}' because a bookmark scope already exists with ...
  60. The specified connection string could not be used to create an EntityConnectionStringBuilder due to the following error: ...
  61. The specified ContractDescription could not be exported to WSDL because the Type property of the MessagePartDescription with ...
  62. The specified DbCrossJoinExpression inputs contain expression bindings with a duplicate variable name, '{2}'. The first occurrence ...
  63. The specified destination buffer is not large enough to hold the specified number of bytes starting at the specified offset. ...
  64. The specified destination path is a mapped drive or UNC path. Installing to mapped drives or UNC paths is not supported. ...
  65. The specified DiscoveryMessageSequence cannot be compared with this message sequence as it represents a different sequence ...
  66. The specified display mode is currently disabled on this page. Make sure personalization is enabled for the current user. ...
  67. The specified display mode is not supported on this page. Make sure personalization is enabled and the corresponding zones ...
  68. The specified element expressions cannot be contained by the same collection because no common element type can be inferred ...
  69. The specified entity cannot be deleted from the ObjectSet because the entity is a member of the EntitySet '{0}.{1}' instead ...
  70. The specified entity cannot be detached from the ObjectSet because the entity is a member of the EntitySet '{0}.{1}' instead ...
  71. The specified format name does not support the requested operation. For example, a direct queue format name cannot be deleted. ...
  72. The specified LINQ expression of type '{0}' cannot be translated into a valid provider-specific LINQ to Entities store expression ...
  73. The specified member '{0}' on the type '{1}' cannot be translated into a valid provider-specific LINQ to Entities store expression ...
  74. The specified metadata path is not valid. A valid path must be either an existing directory, an existing file with extension ...
  75. The specified method '{0}' on the type '{1}' cannot be translated into a LINQ to Entities store expression because its return ...