Troubleshooting Knox E-FOTA
The Knox E-FOTA API uses the conventional HTTP response code to indicate the success or failure of a request. A `2XX` response code indicates success, a `4XX` response code indicates an error given the inputs of the request, and a `5XX` response code indicates a failure with the Knox E-FOTA platform.
Authentication errors will contain a JSON response body with some information about the error. 401 errors occur when the OAuth token sent in the request header is no longer valid or is inaccurate.
Here's an example authentication error response:
HTTP/1.1 401 UNAUTHORIZED
Content-Type: application/json
{ "error": "invalid_request", "error_description": "Validation error" }
All other errors will contain an XML response body containing one of the error codes listed below. Here's an example bad request to the licenseinfo
endpoint:
HTTP/1.1 400 BAD REQUEST
Content-Type: application/xml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <error> <code>FUD_3018</code> <message></message> <resource>com.samsung.efota.mdm.biz.v2.MdmInitBizImpl</resource> </error>
Parameter errors
Processing errors
Error code | Cause of Error | HTTP Status Code | Troubleshoot |
FUD_3001 | The deliveryEndDate parameter is set before the deliveryStartDate . |
400 Bad Request |
Enter a date parameter for |
FUD_3002 | The deliveryEndDate parameter is set less than 3 days and more than 7 days after deliveryStartDate . |
400 Bad Request |
Enter a valid |
FUD_3003 | The dailyEndHour is set to the same parameters as dailyStartHour . |
400 Bad Request |
Enter a valid parameter, there must be a time gap between 0 (midnight) to 24 (after midnight) and be within 12 hours after For example, if |
FUD_3004 | The dailyEndHour is set to occure more than 12 hours after the dailyStartHour . |
400 Bad Request |
Enter a valid parameter, the parameter set must be within 12 hours after For example, if |
FUD_3005 | The deliveryStartDate and dailyStartHour parameter is set before the current date and time. |
400 Bad Request |
Enter a valid parameter, the parameter set must occur after the current date and time. For example, if the current date is (GMT)20171101 and the current time is (GMT)10HH, then the |
FUD_3011 | The following combination of IDs aren't registered: MDM, customer, and group. | 400 Bad Request |
The combination of MDM, customer, and group IDs must be registered into the Knox E-FOTA server in order to proceed. Verify that the parameters entered for |
FUD_3012 | The following combination of IDs aren't registered: MDM and customer. | 400 Bad Request |
The combination of MDM and customer IDs must be registered into the Knox E-FOTA server in order to proceed. Verify that the parameters entered for |
FUD_3013 | An anonymous request was sent to the Server-Init service, or an invalid groupId was detected. |
400 Bad Request |
Verify that |
FUD_3014 | The following parameter combinations are invalid: deviceModelName , carrierCode (Knox E-FOTA v1), or salesCode (Knox E-FOTA v2). The model name or carrier code is not registered or mismatched. |
400 Bad Request |
Verify that |
FUD_3015 | The values entered for targetFirmwareVersion is invalid. |
400 Bad Request |
Verify that the values for |
FUD_3016 | The license entered doesn't match the license registered with MDM and customer ID. | 400 Bad Request |
Enter a license that matches the one received from the SLM server. Note that the license must match the one registered with MDM and customer ID. |
FUD_3017 | The license entered has expired. | 400 Bad Request |
Verify that you've entered the correct license. Check that the license remains valid and has not expired. |
FUD_3018 | The values entered for mdmId and customerId doesn't match the one issued. |
400 Bad Request |
Check that the MDM ID and customer ID entered are the ones issued by SLM at the time the license was purchased. |
FUD_3019 | The following combination of IDs: MDM, customer ID and group ID is already registered to Knox E-FOTA with another license. | 400 Bad Request |
While |
FUD_3020 | The license entered has been cancelled. | 400 Bad Request |
Verify that you've entered the correct license. Check that the license remains valid and has not expired. |
FUD_3021 | The license entered has been terminated. | 400 Bad Request |
Verify that you've entered the correct license. Check that the license remains valid and has not expired. |
FUD_3022 | The license entered is invalid. | 400 Bad Request |
Verify that you've entered the correct license. Check that the license remains valid and has not expired. |
FUD_3023 | The requested model name and carrier code has already been registered. | 400 Bad Request | Verify that the model name and carrier code hasn't already been registered. |
FUD_3024 | The firmware ID entered doesn't exist. | 400 Bad Request | Verify that you've entered the correct firmware ID. Check that the ID remains valid . |
FUD_3026 | The firmware ID entered has already been processed. | 400 Bad Request | Verify that you've entered the correct firmware ID. Check that the ID remains valid. |
FUD_3027 | The requested model is invalid and isn't found in the allowed model group. | 400 Bad Request | Verify that the model you've entered is correct. Check that the strings entered for the requested model is valid: "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789-_" |
FUD_3028 | The firmware requested doesn't exist. | 400 Bad Request |
The requested firmware doesn't exist in the E-FOTA system. Verify that the firmware name entered is valid. Check that the strings entered for firmware name is valid: "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789-/._" |
FUD_3029 | The value entered for the currentFirmwareVersion parameter is invalid. |
400 Bad Request |
The firmware version entered is invalid for the given model and sales code. Check that "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789-/._" |
FUD_3030 | The following parameter combinations are invalid: deviceModelName , carrierCode (Knox E-FOTA v1) , or salesCode (Knox E-FOTA v2). |
400 Bad Request | Verify that model, carrier code (Knox E-FOTA v1), or sales code (Knox E-FOTA v2) are valid and entered properly. If the model or sales code wasn't registered in the Knox E-FOTA server, or if the values entered don't match, then your request will generate an error message. |
FUD_3031 | The serial number entered doesn't match the one registered in the license. | 400 Bad Request | Enter a serial number that matches the one registered in the license. Note that the license must match the one registered with MDM and customer ID. |
FUD_3032 | The new license entered has expired. | 400 Bad Request | Verify that you've entered the correct license. Check that the license remains valid and has not expired. |
FUD_3033 | The following combination of IDs: MDM, customer ID and group ID had not been issued. | 30 | While mdmId and customerId can be the same, ensure that the values entered for groupId and corpId are different to indicate a different license is being used. |
FUD_3034 | The new license entered has been cancelled. | 400 Bad Request | Verify that you've entered the correct license. Check that the license remains valid and has not expired. |
FUD_3035 | The new license entered has been terminated. | 400 Bad Request | Verify that you've entered the correct license. Check that the license remains valid and has not expired. |
FUD_3036 | The new license entered is invalid. | 400 Bad Request | Verify that you've entered the correct license. Check that the license remains valid and has not expired. |
FUD_3037 | There is an insufficient amount of new licenses available. | 400 Bad Request | The number of new licenses must match the number of old licenses already assigned to devices registered by their corp ID. Check the quantity of new licenses available. |
FUD_3038 | The mandatory parameter forceUpdateId is missing or the format entered is invalid. |
400 Bad Request | The mandatory parameter forceUpdateId needs to be entered. You obtain this parameter after pushing a forceUpdate . Note that the force update ID is valid for 3 months after the force update. |
FUD_3039 | The license type of the new license doesn't match the previous license. | 400 Bad Request | The new license type must be the same as the previous license type. |
Service errors
Error code | Cause of Error | HTTP Status Code | Troubleshoot |
FUD_9001 | Database connection error. | 500 Internal Service Error |
An error occurred while attempting to connect to the database. Try again later. If the issue persists, log into your Samsung account to send a ticket through Samsung BTSP with the following information: IMEI, Model name, carrier code and a description of the issue for further assistance. |
FUD_9003 | Internal server error. | 500 Internal Service Error |
An internal server error occurred. Log into your Samsung account to send a ticket through Samsung BTSP with the following information: IMEI, Model name, carrier code and a description of the issue for further assistance. |