.NET Framework

  1. The pre-application start initialization method {0} on type {1} threw an exception with the following error message: {2}. ...
  2. The prefix 'xml' is bound to the namespace name 'http://www.w3.org/XML/1998/namespace'. Other prefixes must not be bound ...
  3. The prefix 'xmlns' is bound to the namespace name 'http://www.w3.org/2000/xmlns/'. It must not be declared. Other prefixes ...
  4. The primary signature is not signed with a derived key. The binding's primary token parameter '{0}' requires key derivation. ...
  5. The primary signature is not signed with a key derived from the encrypted key. The binding's token parameter '{0}' requires ...
  6. The private implementation of this activity has changed (by adding, removing or rearranging implementation children, delegates, ...
  7. The process account used to run ASP.NET must have read access to the IIS metabase (e.g. IIS://servername/W3SVC). For information ...
  8. The process does not have permission to listen on IP endpoint {0}. Make sure that you are not trying to use this endpoint ...
  9. The process identity for the web server account must have a local user profile. See the readme document for details on how ...
  10. The Profile defines the "wire signature" of an operation in a wsdl:binding to be the fully qualified name of the child element ...
  11. The Profile property '{0}' allows anonymous users to store data. This requires that the AnonymousIdentification feature be ...
  12. The profiler currently in use has requested to be detached from the process. The CLR has disabled communication with the ...
  13. The project currently contains references to more than one version of |1, a direct reference to version |4 and an indirect ...
  14. The project XML file "{0}" cannot be unloaded because at least one project "{1}" is still loaded which references that project ...
  15. The properties of the message are mismatched. The message cannot be sent. The BodyType message property cannot be specified ...
  16. The property '{0}' could not be reported as changing. This occurred because EntityComplexMemberChanging was called with a ...
  17. The property '{0}' differs only in case from an existing property, and is not compatible with the current language option. ...
  18. The property '{0}' does not have a valid entity mapping on the complex type. For more information, see the Entity Framework ...
  19. The property '{0}' does not have a valid entity mapping on the entity object. For more information, see the Entity Framework ...
  20. The property '{0}' has been related to '{1}', which is a read only property and cannot be set. Remove the relationship between ...
  21. The property '{0}' in EntityType '{1}' is not valid. All properties that are part of the EntityKey must be of enumeration ...
  22. The property '{0}' in EntityType '{1}' is not valid. EntityKey properties that are of type '{2}' are currently not supported. ...
  23. The property '{0}' in EntityType '{1}' is not valid. Type '{2}' of the property maps to '{3}' and EntityKey properties that ...
  24. The property '{0}' is not a key member of the EntityType. Only key members can be mapped as part of the EndProperty mapping. ...
  25. The property '{0}' is not supported when building a ChannelFactory. The property value must be null when calling BuildChannelFactory. ...
  26. The property '{0}' of type '{1}' in the assembly '{2}' cannot be used as a scalar property because it does not have both ...
  27. The property '{0}' on type '{1}' cannot be serialized because it is decorated with declarative security permission attributes. ...
  28. The property '{0}' on type '{1}' has the return type '{2}', which is not a recognized EntityType or enumeration of instances ...
  29. The property '{0}' on type '{1}' is attributed with EdmComplexPropertyAttribute but returns the type '{2}', which is not ...
  30. The property '{0}' on type '{1}' is attributed with EdmScalarPropertyAttribute but returns the type '{2}', which is not a ...
  31. The property '{0}' on type '{1}' is not a valid property. Make sure that the type of the property is a public type and a ...
  32. The property '{0}' on type '{1}' is not a valid property. Properties whose types are collection of primitives or complex ...
  33. The property '{0}' provided at the end of the PropertyName property of the EntityPropertyMappingAttribute on a resource type ...
  34. The property '{0}' referred in the request URI is a open property and refers to a collection of resources. Open properties ...
  35. The property '{0}' specified in source path for EntityPropertyMappingAttribute is of non-primitive type while it is provided ...
  36. The property '{0}' specified in source path for EntityPropertyMappingAttribute is of primitive type while it is not provided ...
  37. The property '{1}' on type '{0}' threw an exception so the value stored in the property will be removed. The exception was: ...
  38. The property for the relationship '{0}' contains a Role '{1}' has a type '{2}' that is not valid for a relationship End. ...
  39. The property name '{0}' (an XName) for a value provided to DurableInstanceManager.AddInstanceOwnerValues conflicts with the ...
  40. The property name '{0}' provided on an InsertParameters, UpdateParameters, or DeleteParameters collection does not match ...
  41. The property name specified in the IgnoreProperties attribute cannot be null or empty. Please specify a valid property name. ...
  42. The property name'{0}' specified in the ETagAttribute on type '{1}' is not a valid property name. Please specify a valid ...
  43. The property path '{0}' specified for EntityPropertyMappingAttribute does not correspond to any property in type '{1}' or ...
  44. The property path '{0}' specified for EntityPropertyMappingAttribute on member '{1}' does not correspond to any property ...
  45. The property path '{0}' specified for the EntityPropertyMappingAttribute does not correspond to any property in type '{1}' ...
  46. The property value corresponding to Published property in SyndicationItemProperty could not be converted to type DateTimeOffset. ...
  47. The property value corresponding to Updated property in SyndicationItemProperty could not be converted to type DateTimeOffset. ...
  48. The property's value was not set because the provider did not support the '{0}' property, or the consumer attempted to get ...
  49. The PropertyName property value '{0}' on more than one EntityPropertyMappingAttribute on resource type '{1}' is provided ...
  50. The protocol '{0}' specified in the protocol binding for the application '{1}' does not match the one that the Listener Adapter ...
  51. The protocol binding '{0}' does not conform to the syntax for '{1}'. The following is an example of valid '{1}' protocol ...
  52. The provided activity ID was in an invalid format. It must be a dot separated list of integer values such as '1.12.3' with ...
  53. The provided activity was not part of this workflow definition when its metadata was being processed. The problematic activity ...
  54. The provided EntitySet name must be qualified by the EntityContainer name, such as 'EntityContainerName.EntitySetName', or ...
  55. The provided ID '{0}' could not be found in the workflow. Check the workflow for validation errors which could be generating ...
  56. The provided implementation map does not match the activity's definition. Please ensure that the version of the activity ...
  57. The provided list of key-value pairs contains an incorrect number of entries. There are {1} key fields defined on type '{0}', ...
  58. The provided value '{0}' is not a valid value for channel idle timeout. The value should be a valid TimeSpan or 'infinite'. ...
  59. The provided value '{0}' is not a valid value for channel lease timeout. The value should be a valid TimeSpan or 'infinite'. ...
  60. The provided value '{0}' is not a valid value for max idle channels per endpoint. The value should be a valid positive integer. ...
  61. The provider connection point '{0}' on '{1}' and the consumer connection point '{2}' on '{3}' do not use the same connection ...
  62. The provider could not determine the {0} value. For example, the row was just created, the default for the {0} column was ...
  63. The Provider tab manages configuration settings that are stored in the Web.config file for your application. Specifically, ...
  64. The Publisher membership condition is true if an assembly is digitally signed with a certificate that matches the one below. ...
  65. The query view specified for the EntitySet '{0}' contains a reference to member '{1}' of kind '{2}'. Only columns may be ...
  66. The query view specified for the EntitySet '{0}' includes a call to the Function '{1}'. Only storage Functions may be referenced ...
  67. The query view specified for the EntitySet '{0}' includes a scan of the '{1}' EntitySet. Only storage EntitySets may be referenced ...
  68. The query view specified for the EntitySet '{0}' initializes an instance of type '{1}'. Only types assignable to the element ...
  69. The queue could not be opened because the ReceiveContext feature is not supported on subqueues. Specify a different queue ...
  70. The QuotePrefix and QuoteSuffix properties cannot be changed once an Insert, Update, or Delete command has been generated. ...
  71. The read from the pipe did not complete within the allotted timeout of {0}. The time allotted to this operation may have ...
  72. The Receive activity configured with request/reply operation '{0}' failed to initialize a RequestReplyCorrelation handle. ...
  73. The Receive activity is configured with a request/reply Operation '{0}', however, there is no SendReply paired with it. Please ...
  74. The receive context, {0}, is in an unsupported state '{1}'. This indicates an internal error in the implementation of that ...
  75. The receive context, {0}, is in the {1} state. Receive contexts cannot be used for sending delayed acks unless they are in ...