2.2.3.1 UPnPError
DTAG error messages MUST be expressed in XML using a SOAP 1.1 UPnP profile, as specified in [UPNPARCH1.1] section 3.1. For this expression, the <UPnPError> element can be defined as follows and included as part of the <detail> element of the SOAP fault message, as specified in section 2.2.2.1.
-
<xs:element name="UPnPError"> <xs:complexType> <xs:sequence> <xs: element name="ErrorCode" type="xs:integer"/> <xs: element name="ErrorDescription" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element>
The following table lists the possible values of the <ErrorCode> and <ErrorDescription> elements. If an action results in multiple errors, the most specific error MUST be returned.
|
ErrorCode |
ErrorDescription |
Explanation |
|---|---|---|
|
401 |
Invalid Action |
See the description of Control in [UPNPARCH1.1] section 3. |
|
402 |
Invalid Args |
Parameters are missing, extra, or are invalid for this action. See the description of Control in [UPNPARCH1.1] section 3. |
|
403 |
Out of Sync |
See the description of Control in [UPNPARCH1.1] section 3. |
|
501 |
Action Failed |
The service was not able to process this action, or the action is not allowed in the current state. See the description of Control in [UPNPARCH1.1] section 3. |
|
801 |
Invalid Endpoint |
The parameter, <HostID>, has an invalid format or is inconsistent with previous usage. |
|
802 |
Invalid Certificate |
The parameter, <HostCertificate>, has an invalid format or does not reference the <HostID>. |
|
803 |
Invalid Nonce |
The authentication process failed. |