.NET Framework

  1. The original value for the property '{0}' cannot be set to null because the '{1}' member on the entity type '{2}' is not ...
  2. The OriginalWorkflowDefinition provided to the map builder is invalid for implementation map creation because it does not ...
  3. The OS handle's position is not what FileStream expected. Do not use a handle simultaneously in one FileStream and in Win32 ...
  4. The outgoing message with action '{0}' contains a callback context message property. Callback context cannot be transmitted ...
  5. The output writer for code generation and the writer supplied don't match and cannot be used. This is generally caused by ...
  6. The page '{0}' cannot use the user control '{1}', because it is registered in web.config and lives in the same directory ...
  7. The page already has the 'SqlDependency="CommandNotification"' attribute specified in the OutputCache directive. On such ...
  8. The page already has the 'SqlDependency="CommandNotification"' attribute specified in the OutputCache directive. On such ...
  9. The page is performing an async postback but the ScriptManager.SupportsPartialRendering property is set to false. Ensure ...
  10. The page needs to save viewstate, but session state is disabled or readonly. Enable session state, or disable viewstate for ...
  11. The page requires session state that is no longer available. Either the session has expired, the client did not send a valid ...
  12. The parameter '{0}' is not a correctly formed parameter. All switches must begin with '/' and separate the name from the ...
  13. The parameter '{0}' is not an input-only parameter. The EntityClient provider only allows input-only parameters when the ...
  14. The parameter at index {0} requested from the InstancePersistenceAction named {1} was requested using an incorrect generic ...
  15. The parameter name '{0}' is not valid. A valid parameter name must begin with a letter and contain only letters, numbers, ...
  16. The parameter {0} in function '{1}' in schema '{2}' has an invalid parameter direction {3}. The only valid value for this ...
  17. The parameter {0} in function '{1}' in schema '{2}' has an invalid parameter direction {3}. Valid parameter directions are: ...
  18. The parameterized constructor '{0}' has a parameter named '{1}' which is the same as the default return value name. Consider ...
  19. The parameters of Function '{0}' are converted to conceptual side type '{1}', and the function with the same conceptual side ...
  20. The parent control, usually the form, that contains the data-bound controls on which the ErrorProvider can display error ...
  21. The participantCount argument is greater than the number of participants that haven't yet arrived at the barrier in this ...
  22. The PassportManager object could not be initialized. Please ensure that Microsoft Passport is correctly installed on the ...
  23. The password supplied is invalid. Passwords must conform to the password strength requirements configured for the default ...
  24. The password-question supplied is invalid. Note that the current provider configuration requires a valid password question ...
  25. The path "{0}" is not supported. When InlineScript=true, the path should be a relative path pointing to the same web application ...
  26. The path is too long after being fully qualified. Make sure the full path is less than 260 characters and the directory name ...
  27. The persistence provider implementation of InstanceStore doesn't support the command named {0}. Either choose a different ...
  28. The persistence provider implementation of InstanceStore in use is invalid. A new instance was created when an InstanceNotReadyException ...
  29. The persistence provider implementation of InstanceStore in use is invalid. An ambient transaction (System.Transactions.Transaction.Current) ...
  30. The persistence provider implementation of InstanceStore in use is invalid. It attempted to execute a potentially lock-acquiring ...
  31. The persistence provider implementation of InstanceStore in use is invalid. It attempted to execute transactional command ...
  32. The persistence provider implementation of InstanceStore in use is invalid. It called BindAcquiredLock to set the locked ...
  33. The persistence provider implementation of InstanceStore in use is invalid. It called BindAcquiredLock, BindReclaimedLock, ...
  34. The persistence provider implementation of InstanceStore in use is invalid. It called BindAcquiredLock, BindReclaimedLock, ...
  35. The persistence provider implementation of InstanceStore in use is invalid. It called BindAcquiredLock, BindReclaimedLock, ...
  36. The persistence provider implementation of InstanceStore in use is invalid. It called BindInstance to set the instance ID ...
  37. The persistence provider implementation of InstanceStore in use is invalid. It called BindInstanceOwner twice with the same ...
  38. The persistence provider implementation of InstanceStore in use is invalid. It called BindOwner to set the owner of an InstanceHandle ...
  39. The persistence provider implementation of InstanceStore in use is invalid. It called the method {0} on InstancePersistenceContext, ...
  40. The persistence provider implementation of InstanceStore in use is invalid. It completed processing a TryCommand request ...
  41. The persistence provider implementation of InstanceStore in use is invalid. It failed to bind the InstanceHandle to an instance ...
  42. The persistence provider implementation of InstanceStore in use is invalid. It reported acquiring and committing the same ...
  43. The persistence provider implementation of InstanceStore in use is invalid. It reported associating a key to an instance ...
  44. The persistence provider implementation of InstanceStore in use is invalid. It reported completing a key which was already ...
  45. The persistence provider implementation of InstanceStore in use is invalid. It reported completing an instance with active ...
  46. The persistence provider implementation of InstanceStore in use is invalid. It reported completing or modifying a key which ...
  47. The persistence provider implementation of InstanceStore in use is invalid. It reported disassociating a key which was associated ...
  48. The persistence provider implementation of InstanceStore in use is invalid. It reported disassociating a key which was not ...
  49. The persistence provider implementation of InstanceStore in use is invalid. It reported loading an instance with an invalid ...
  50. The persistence provider implementation of InstanceStore in use is invalid. It reported loading an instance with InstanceState.Completed ...
  51. The persistence provider implementation of InstanceStore in use is invalid. It reported loading an instance with InstanceState.Uninitialized ...
  52. The persistence provider implementation of InstanceStore in use is invalid. It reported loading an InstanceValue with InstanceValueOptions.WriteOnly ...
  53. The persistence provider implementation of InstanceStore in use is invalid. It reported performing an operation which requires ...
  54. The persistence provider implementation of InstanceStore in use is invalid. It reported performing an operation which requires ...
  55. The persistence provider implementation of InstanceStore in use is invalid. It reported performing an operation which requires ...
  56. The persistence provider implementation of InstanceStore in use is invalid. It reported performing an operation which requires ...
  57. The persistence provider implementation of InstanceStore in use is invalid. It reported performing an operation which requires ...
  58. The persistence provider implementation of InstanceStore in use is invalid. It returned false from TryCommand (or EndTryCommand) ...
  59. The persistence provider implementation of InstanceStore in use is invalid. Its handler for cancel threw an exception. The ...
  60. The persistence provider implementation of InstanceStore in use is invalid. Its implementation of OnFreeInstanceHandle threw ...
  61. The persistence provider implementation of InstanceStore in use is invalid. The {0} method can only be called during the ...
  62. The persistence provider implementation of InstanceStore is invalid. It attempted to execute multiple nested commands concurrently. ...
  63. The persistence provider implementation of InstanceStore successfully canceled the command. An orphaned lock was reclaimed ...
  64. The persistence provider was unable to reclaim the lock within the timeout provided. This may indicate a deadlock in the ...
  65. The persistence value named {0} is being provided as an initial metadata value, so it must have a valid InstanceValue other ...
  66. The personal card that is used for authentication of the managed card cannot be found. If you have a backup file containing ...
  67. The physical path of the application to be compiled. If -p is missing, the IIS metabase is used to locate the app. This switch ...
  68. The picture file format for this file is an unknown or invalid file type. Select a different picture file. Supported picture ...
  69. The pipe connection was aborted because an asynchronous read from the pipe did not complete within the allotted timeout of ...
  70. The pipe connection was aborted because an asynchronous write to the pipe did not complete within the allotted timeout of ...
  71. The platform mapping "{0}" in the platform mapping list "{1}" is malformed. Please only pass in a semicolon-delimited list ...
  72. The PNRP service is not installed on this machine. Please refer to the documentation with your system for details on how ...
  73. The policy being imported for contract '{0}:{1}' contains multiple HTTP authentication scheme assertions. Since at most one ...
  74. The policy expression was not fully imported because it exceeded the maximum allowable complexity. The import stopped at ...
  75. The policy to import a process cannot import a binding for contract ({0},{1}). The protection requirements for the binding ...