Request - Error in query syntax.
!An internal error '{0}' occurred.
'{0}' is an invalid instance annotation name. An instance annotation name must contain a period that is not at the start or end of the name.
&
Syntax error at position {0} in '{1}'.
0An error occurred while parsing part of the URI.
4Bad Request: there was an error in the query syntax.
5An error occurred while processing the OData message.
A node of type '{0}' was read from the JSON reader when trying to read the start of a collection with a collection wrapper object. A 'StartObject' node was expected.
A node of type '{0}' was read from the JSON reader when trying to read the start of a feed. A 'StartObject' or 'StartArray' node was expected.
A node of type '{0}' was read from the JSON reader when trying to read the start of an entity reference link. In JSON Light, entity reference links must be objects.
A node of type '{0}' was read from the JSON reader when trying to read the start of an entity reference link. In OData, entity reference links must be objects.
A node of type '{0}' was read from the JSON reader when trying to read the start of an entry. A 'StartObject' node was expected.
A node of type '{0}' was read from the JSON reader when trying to read the start of the content of a feed
however, a node of type 'StartArray' was expected.
A property with name '{0}' was found in the error object when reading a top-level error. In OData, a top-level error object must have exactly one property with name 'error'.
A property with name '{0}' was found in the error value of a top-level error. In OData, a top-level error value can only have properties with name 'code', 'message', or 'innererror', or custom instance annotations.
A property with name '{0}' was found in the error value of a top-level error. In OData, a top-level error value can only have properties with name 'code', 'message', or 'innererror'.
A property with name '{0}' was found in the message value of a top-level error. In OData, the message value of a top-level error value can only have properties with name 'lang' or 'value'.
AThe function overloads matching '{0}' are invalid. This is most likely an error in the IEdmModel.
An OData instance annotation '{0}' was found in an error payload
however, error payloads do not support OData instance annotations.
An OData property annotation '{0}' was found in an error payload
however, error payloads do not support OData property annotations.
An ODataCollectionStart with a 'null' name was passed to the ATOM collection writer. In ATOM, an ODataCollectionStart cannot have a 'null' name.
An ODataCollectionStart with an empty name was passed to the collection writer. An ODataCollectionStart cannot have an empty name.
An error occurred when parsing the HTTP header '{0}'. The header value '{1}' is incorrect at position '{2}' because '{3}' is not a recognized separator. The supported separators are ',', '
', and '='.
An error occurred when parsing the HTTP header '{0}'. The header value '{1}' is incorrect at position '{2}' because '{3}' is not a valid separator after a quoted-string.
An error occurred when parsing the HTTP header '{0}'. The header value '{1}' is incorrect at position '{2}' because a token is expected but a quoted-string is found instead.
An error occurred when parsing the HTTP header '{0}'. The header value '{1}' is incorrect at position '{2}' because a token or a quoted-string is expected at this position but were not found.
An error occurred when parsing the HTTP header '{0}'. The header value '{1}' is incorrect at position '{2}' because it terminates with the escape character '{3}'. In a quoted-string, the escape characters must always be followed by a character.
An error occurred when parsing the HTTP header '{0}'. The header value '{1}' is incorrect at position '{2}' because the character '{3}' is not allowed in a quoted-string. For more information, see RFC 2616, Sections 3.6 and 2.2.
An error occurred when parsing the HTTP header '{0}'. The header value '{1}' is incorrect at position '{2}' because the closing quote character was not found for the quoted-string.
An error occurred when parsing the HTTP header '{0}'. The header value '{1}' is incorrect at position '{2}' because the escape character '{3}' is not inside a quoted-string.
An error occurred when parsing the HTTP header '{0}'. The header value '{1}' is incorrect at position '{2}' because the header value should not end with the separator '{3}'.
An invalid quality value was detected in the header string '{0}'
quality values must start with '0' or '1' but not with '{1}'.
DAn error occurred when converting the character '{0}' to an integer.
FInner or start path segments must be navigation properties in .
FThe Entity Set of the operation '{0}' is not specified. This is most likely an error in the IEdmModel.
GWriteEnd can only be called after WriteStart and after the previously created sub-writer has completed.
IA top-level error cannot be read from request payloads. Top-level errors are only supported in responses.
IComplex types can not be marked as 'Open'. Error occurred for type '{0}'.
KParameter names must be unique. There is most likely an error in the model.
MWriting an in-stream error is not supported when writing a parameter payload.
Multiple '{0}' properties were found in an error or inner error object. In OData, an error or inner error must have at most one '{0}' property.
Multiple '{{http://schemas.microsoft.com/ado/2007/08/dataservices/metadata}}:{0}' elements were found in a top-level error value. In OData, the value of a top-level error value can have no more than one '{{http://schemas.microsoft.com/ado/2007/08/dataservices/metadata}}:{0}' element
Multiple '{{http://schemas.microsoft.com/ado/2007/08/dataservices/metadata}}:{0}' elements were found in an inner error value. In OData, the value of an inner error value can have at most one '{{http://schemas.microsoft.com/ado/2007/08/dataservices/metadata}}:{0}' element.
NAn error was read from the payload. See the 'Error' property for more details.
NWhen trying to read the start of a collection, the expected collection property with name '{0}' was not found.
One or more property annotations for property '{0}' were found in an error payload without the property to annotate. Error payloads must not contain property annotations for properties that are not in the payload.
QParsing JSON Light payloads without a model is only supported for error payloads.
RCannot transition from state '{0}' to state '{1}'. Nothing can be written once the writer entered the error state.
TError processing request stream. In batch mode, a resource can be cross-referenced only for bind/unbind operations.
The '{0}' header value '{1}' is invalid. When this is the start of the change set, the value must be '{2}'
otherwise it must be '{3}'.
The WriteError and WriteErrorAsync methods on ODataMessageWriter cannot be called when a batch is being written by using ODataBatchWriter. In OData, writing an in-stream error for a batch payload is not supported.
The WriteError method or the WriteErrorAsync method on ODataMessageWriter cannot be called after the WriteValue method or the WriteValueAsync method is called. In OData, writing an in-stream error for raw values is not supported.
The WriteError method or the WriteErrorAsync method on the ODataMessageWriter has already been called to write an error payload. Only a single error payload can be written with each ODataMessageWriter instance.
The element with name '{0}' in namespace '{1}' is not a valid root element for an error. The root element of an error must be 'error' and must belong to the 'http://schemas.microsoft.com/ado/2007/08/dataservices/metadata' namespace.
The element with name '{0}' in namespace '{1}' is not a valid start element for an entity reference link. The start element of an entity reference link must be 'uri' and it must belong to the 'http://schemas.microsoft.com/ado/2007/08/dataservices' namespace.
The element with name '{0}' in namespace '{1}' is not a valid start element for entity reference links. The start element of entity reference links must be 'links' and it must belong to the 'http://schemas.microsoft.com/ado/2007/08/dataservices' namespace.
The relative URI '{0}' cannot be escaped because it starts with '{1}' and a base URI is not available. Relative URIs without a base URI cannot start with '/', '' or '..'.
The request line '{0}' is invalid. The request line at the start of each operation must be of the format 'HttpMethod RequestUrl HttpVersion'.
The response line '{0}' is invalid. The response line at the start of each operation must be of the format 'HttpVersion StatusCode StatusCodeString'.
UThe target Entity Set of Navigation Property '{0}' could not be found. This is most likely an error in the IEdmModel.
Unable to resolve function overloads to a single function. There was more than one function in the model with name '{0}' and parameter names '{1}'.
VUnable to find property '{2}' on the instance type '{1}' of the structured type '{0}'.
WWriteStart can only be called once, and it must be called before writing anything else.
When trying to read the start of a collection without a collection wrapper object, a node of type '{0}' was read from the JSON reader
however, a 'StartArray' node was expected.
WriteValue and CreateCollectionWriter can only be called after WriteStart and before WriteEnd
they cannot be called until the previously created sub-writer is completed.
XAn error cannot be written to a request payload. Errors are only supported in responses.