XML QERR Packet

GDS uses a standardised error packet in order to simplify handling of errors on both clients and servers.

Fields in QERR

All fields are optional, unless explicitly noted.

Output Field Datatype Description

f3 number Standard error defining a broad category of error. This field SHOULD always be provided to clients. type failures.

4 Feature disabled

8 Invalid call. Did not like arguments etc.

32 Unknown resource. The requested item is not known. This might be a pinboard, bucket, table, server or other entity.

64 Security failure, at the widest meaning possible, not just password
128 Application specific error, refer to F4. The field F4 can be returned by clients, even if this F3 field is not set to 128.

256 Execute failure. The server encountered some severe error while processing the request. The client request is probably ok, but the server just cannot process it now.

f4 number An application specific error code providing more in-depth information about the error being returned. Generally present, although this depends on where the error is generated.

f20 string A string description of the f3 value. A short message designed for technical users. This field will NOT convey additional error information.

f22 string An application specific string description of the error code in F4. This error string is potentially displayable to users and will be returned in the current language of the device, or Accept-Language for Web.

Meetu4 Error Codes (F4)

These error codes relate to Meetu4, need codes for RetailMAX.

Value Description

124 Manually generated error when login credentials include "|debugtime".

130 User required for new logins.

131 Device UserGuid does not match provided value.

132 Unable to process at this time. The server is encountering some kind of condition that means it is unable to reliably respond at this time. Pause and try again shortly (in this context, pause means at least a few seconds)

133 No user record. The device has successfully logged in, however the server cannot locate the user record. This should not happen in normal operation.

134 No retailer record. The device has successfully logged in, however the server cannot locate the retailer record. This can occur if a shopper attempts to access retailer only buckets

135 A required predicate for this bucket has not been supplied

136 The bid amount was not sufficent for the message. It has not been accepted.

137 Bad arguments. Either a parameter was missing or out of bounds

138 Account name in use

139 Account name not accepted. A variation of 138 where we do not wish to confirm that this is already an account or not.

140 Wrong password

141 New password not accepted

142 Unable to email

143 Account Locked

144 Unspecified error whilst trying to delete device

Examples

A security failure

<QERR>
 <F3>64</F3> 
</QERR>

Locked account

<QERR>
 <F3>64</F3> 
 <F4>143</F4> 
 <F22>Account gesperrt</F22>
</QERR>

Value	Description
124	Manually generated error when login credentials include "\|debugtime".
130	User required for new logins.
131	Device UserGuid does not match provided value.
132	Unable to process at this time. The server is encountering some kind of condition that means it is unable to reliably respond at this time. Pause and try again shortly (in this context, pause means at least a few seconds)
133	No user record. The device has successfully logged in, however the server cannot locate the user record. This should not happen in normal operation.
134	No retailer record. The device has successfully logged in, however the server cannot locate the retailer record. This can occur if a shopper attempts to access retailer only buckets
135	A required predicate for this bucket has not been supplied
136	The bid amount was not sufficent for the message. It has not been accepted.
137	Bad arguments. Either a parameter was missing or out of bounds
138	Account name in use
139	Account name not accepted. A variation of 138 where we do not wish to confirm that this is already an account or not.
140	Wrong password
141	New password not accepted
142	Unable to email
143	Account Locked
144	Unspecified error whilst trying to delete device