Error codes
Last updated February 29th, 2024
Every error that occurs in the Knox Service Plugin has an associated error code. The following sections cover what each error means and the optimal solution to resolve it.
A typical error message looks like this in the app:
For errors that require additional support, please submit a support ticket. Some errors require additional information from the device log before they can be resolved. To learn how to retrieve a device log, see Get device logs in the Knox Platform for Enterprise documentation.
Knox Service Plugin issue
Fatal errors
| Error code |
Error message |
Cause |
Resolution |
| 11000 |
An unknown error occurred. |
Unknown error |
Please contact support and provide a device log. |
| 11001 |
The Android version you're using doesn't support Knox Service Plugin. |
Unsupported Android version |
To use Knox Service Plugin, upgrade your device to Android 8.0 or higher. |
| 11002 |
The Android version you're using doesn't support Knox Service Plugin. |
Unsupported Android version |
To use Knox Service Plugin within a Work Profile, upgrade your device to Android 9.0 or higher. |
| 11003 |
Couldn't find a Device Owner or Profile Owner. |
Device owner or Profile owner missing |
Please re-enroll your device in DO or PO mode. |
| 11004 |
Device administration permission required |
The Knox Service Plugin app doesn't have Device Administration permission enabled. |
Install or push the Knox Service Plugin app to the device again, and ensure the device user accepts the Device Administration agreement. |
| 11005 |
A Knox delegation failure occurred. |
Knox delegation failure |
Please contact support. |
Schema errors
| Error code |
Error message |
Cause |
Resolution |
| 12001 |
One or more mandatory fields haven't been completed for policies you've selected to configure. |
Required fields missing |
Check in your UEM console that you've entered all fields correctly and that none are left blank. |
| 12002 |
Your device uses an older version of Knox Service Plugin. |
Newer version of KSP app required |
Update your Knox Service Plugin app. After the update, the app will try to apply the Knox policy changes. |
| 12003 |
Unsupported keys have been specified in the input data. |
Unsupported keys in input data |
Check in your UEM console that you've entered all fields correctly. |
| 12006 |
No policies were received. |
No policies received |
Check in your UEM console that you've entered all fields correctly. |
License errors
| Error code |
Error message |
Cause |
Resolution |
| 13001 |
Your license is invalid. |
Problem with KPE license |
Check that you have a valid Knox Platform for Enterprise license. |
| 13002 |
Your Knox Platform for Enterprise license has expired. |
Problem with KPE license |
Renew your Knox Platform for Enterprise license or generate a new one. |
| 13003 |
You've reached the maximum number of license assignments. |
Problem with KPE license |
If you need more license assignments, contact the Knox Reseller or your Samsung account representative. You don't need to obtain another Knox Platform for Enterprise license. |
| 13004 |
Your Knox Platform for Enterprise license is terminated. |
Problem with KPE license |
Please generate a new Knox Platform for Enterprise license. |
| 13005 |
Your license couldn't be activated because of a network error. |
Problem with KPE license |
Ensure your device is connected to the network, and try activating your license again. |
| 13006 |
Your Knox license couldn't be activated because the time and date on your device don't match the current time and date. |
Problem with KPE license |
Set the correct time and date on your device, and try activating your license again. |
| 13007 |
This license cannot be used with your application. |
Problem with KPE license |
You will need to associate your app with a Knox Platform for Enterprise Premium (commercial) license in the Knox Developer Portal. |
| 13008 |
An unknown license error occurred. |
Problem with KPE license |
Verify that your Knox Platform for Enterprise license is valid, and try again. |
| 13009 |
One or more policies couldn't be applied because of insufficient permissions. |
KPE Premium license required |
Please obtain a Knox Platform for Enterprise Premium license and try applying the policies again. |
| 13010 |
One or more policies that you're trying to apply require a Knox Platform for Enterprise Premium license. |
KPE Premium license required |
Provide a valid Knox Platform for Enterprise Premium license key and try applying the policies again. |
| 13011 |
This policy requires a Knox Platform for Enterprise Premium license with Dual DAR add-on. |
Dual DAR license required |
Contact Samsung for more information and to upgrade your license with the Dual DAR add-on. |
Unknown
| Error code |
Error message |
Cause |
Resolution |
| 21000 |
An unknown error occurred while trying to apply this policy. |
Unknown KPE or Android error |
Please try applying the policy again. |
Exception
| Error code |
Error message |
Cause |
Resolution |
| 22000 |
A device exception occurred while trying to apply this policy. |
Device exception occurred |
Please try applying the policy again. |
Unexpected return value
| Error code |
Error message |
Cause |
Resolution |
| 23000 |
KPE error occurred while trying to apply this policy. |
KPE error |
Please try applying the policy again. |
| 23001 |
UCM error occurred while configuring UCM Plugin. |
Problem with UCM device lock |
Please try applying the policy again. |
Install fail
| Error code |
Error message |
Cause |
Resolution |
| 24000 |
An installation problem is preventing this policy from being applied. |
Problem with installation |
Please try applying the policy again. |
| 24001 |
UCM error occurred while installing UCM applet. |
UCM ese applet install fail |
Please try applying the policy again. |
Creation fail
| Error code |
Error message |
Cause |
Resolution |
| 25000 |
Couldn't configure the policy |
Problem with policy configuration creation |
Check if anything is missing from the advanced polices. |
| 25001 |
Couldn't configure the APN (Access Point Name). |
Problem with APN policy configuration |
Check if anything is missing from the APN configuration. For details, see Device controls. |
| 25002 |
Couldn't configure the VPN (Virtual Private Network). |
Problem with VPN policy configuration |
Check if anything is missing from the VPN configuration. For details, see VPN policies. |
| 25003 |
UCM error occurred because the data is incorrectly configured. |
UCM incorrect data configuration |
Please try applying the policy again. |
Update fail
| Error code |
Error message |
Cause |
Resolution |
| 26000 |
Couldn't update the policy settings. |
Problem with policy configuration update |
Check if anything is missing from the policy configuration. |
| 26001 |
Couldn't update the APN (Access Point Name) settings. |
Problem with APN configuration update |
Check if anything is missing from the APN configuration. |
| 26002 |
Couldn't update the VPN (Virtual Private Network) settings. |
Problem with VPN configuration update |
Check if anything is missing from the VPN configuration. |
Invalid policy configuration
| Error code |
Error message |
Cause |
Resolution |
| 31000 |
This policy couldn't be applied because one or more required input fields is empty. |
Required input field empty |
Check in your UEM console that you've entered all fields correctly. |
| 31001 |
This policy couldn't be applied because one or more input fields contained invalid data. |
Invalid input field |
Check in your UEM console that you've entered all fields correctly. |
Data or path error
| Error code |
Error message |
Cause |
Resolution |
| 32000 |
This policy couldn't be applied because a specified file path is not valid. |
Invalid file path |
Check in your UEM console that you've entered all fields correctly. |
Type mismatch
| Error code |
Error message |
Cause |
Resolution |
| 33000 |
This policy couldn't be applied because of a data type mismatch in one or more input fields. |
Data type mismatch |
Check in your UEM console that you've entered all fields correctly. |
| Error code |
Error message |
Cause |
Resolution |
| 34000 |
You've exceeded the maximum number of policy configurations. |
Exceeded maximum policy configurations |
Modify your policy configuration and try again. |
| 34001 |
This policy couldn't be applied because your password length is invalid. |
Invalid password length |
Please try applying the policy again with a valid password. |
| 34002 |
This policy couldn't be applied because the shutdown timer length is less than 600 seconds. |
Invalid shutdown timer length |
Please try applying the policy again with a valid timer length. |
Policy combination issue
Policy enabled but no data
| Error code |
Error message |
Cause |
Resolution |
| 41000 |
One or more policy configurations are missing some required input data. |
Required profile configuration missing |
Check in your UEM console that you've entered all fields correctly and that none are left blank. For details, see Advanced policies. |
Policy conflict
| Error code |
Error message |
Cause |
Resolution |
| 42000 |
Some policies couldn't be applied because of a policy conflict. |
Policy conflict |
Adjust the policy settings by referring to the error message details. |
Policy combination or precondition problem
| Error code |
Error message |
Cause |
Resolution |
| 43000 |
Some policies couldn't be applied because the preconditions were not met. |
Another policy is required to apply this policy |
Adjust the policy settings by referring to the error message details. |
Device environment issue
Package not installed
| Error code |
Error message |
Cause |
Resolution |
| 51000 |
This policy couldn't be applied because the required app package is not installed. |
App package not installed |
Install the appropriate app and try applying the policy again. |
Certificate not installed
| Error code |
Error message |
Cause |
Resolution |
| 52000 |
This policy couldn't be applied because the required certificate is not installed. |
Certificate not installed |
Install the appropriate certificate and try applying the policy again. |
Network issue
| Error code |
Error message |
Cause |
Resolution |
| 53000 |
This policy couldn't be applied because of a network issue. |
Network connection issue |
Ensure your device is connected to the network and try applying the policy again. |
User interaction needed
| Error code |
Error message |
Cause |
Resolution |
| 54000 |
This policy requires interaction from the device user. |
User interaction with device required |
Interaction from the device user is required to apply this policy. |
| 54003 |
Couldn't activate a token for DualDAR. |
Token activation required from device user |
The device user needs to manually activate the DualDAR password token in the device settings (Settings > Lock screen > Screen lock type > Confirm lock). |