HYPR Error Codes Troubleshooting Table

July 15, 2020 17:35

Overview

The table below will help Admins determine the root cause for each error returned to the user in the iOS, Android, macOS, or Windows Apps.

Error Code: The error code presented to the user.
Cause: The root cause of the problem.
Recommended Resolution: Action required to resolve the issue.

Root Cause Tracing

Prefix	Error Cause
	iOS	Android	Server	Mac OS	Windows
	10	11	12	14	15

(Windows) WorkforceAccess v6.2.0+

Error Code	Cause	Recommended Resolution
1520001	1. There appears to be an active registration in progress. 2. A previous attempt at Registration may not be completely timed out.	The user should try to register again in 3 minutes. Reboot the computer and try again if not resolved. Analyze HYPROneService logs if the problem is still happening.
1520002	1. Setup appears to have timed out. 2. Either the server or domain controller has not responded	Check that you are connected to the internet, then try to register again. Ensure that user follows all registration steps on mobile app, and windows app.
1520003	This error indicates that the request has timed out. This may be the result of a registration taking longer than the allowed duration, or the failure to receive a response from the server or domain controller during a step in the pairing process.	1. Check that the user is on a secure network (office or VPN) and try again. This will ensure the user is ready to begin pairing. 2. If the issue persists - Try to register again but proceed quickly through the pairing process. This will ensure that end user speed is not the cause of the issue. 3. If the issue persists - Guide the user to reboot workstation and reinstall mobile app before trying again.
1520004	This error indicates that the workstation client may not be configured properly. This is typically not a production issue and may be experienced during sandbox or deployment testing by internal or pilot users. This can be caused by either of an incorrect relying party application ID, an incorrect server or other parameters set by an administrator during installation.	1. Check that the user is on a secure network (office or VPN). This will ensure the user is ready to begin pairing. 2. If the issue persists - Try to register again but proceed quickly through the pairing process. This will ensure that end user speed is not the cause of the issue. 3. Provide the admin with troubleshooting information as requested and wait for feedback. As an admin, if the issue appears to be the workstation settings, verify that parameters such as the RP App, RP URL, Pinning value and other fields are set in accordance with your deployment.
1520005	This error indicates a failure to unpair a registered device. This may occur for several reasons including a delay on the server.	1. Wait 2 minutes and then proceed to unpair once again. This may allow enough time for pending requests to complete. 2. If the issue persists - open the workstation client, and open the mobile app. Longpress on the workstation you would like to unpair and proceed to additional detail on the mobile app to delete the connected device.
1520006	This error indicates the user is trying to pair a mobile app with their workstation and the workstation is not on authorized network. Not being on an approved network does not allow pairing process to generate a certificate with the domain. This issue may also be experienced in scenarios where proxies are involved in routing connections and may indicate an administrative issue.	1. Check that the user is on a secure network (office or VPN) try again. This will ensure the user is ready to begin pairing. 2. If the issue persists - Try to register again but proceed quickly through the pairing process. This will ensure that end user speed is not the cause of the issue. 3. If the issue persists - Guide the user to reboot workstation before trying again.
1530001	This error indicates the user has entered in an incorrect 'user presence' check when prompted for their workstation password. During the pairing process, an enterprise may require the user to type in their current password one final time to validate that they are the professional who has logged into the workstation. When this is incorrectly entered, such as in the case where a rogue or malicious user tries to register on a colleague's unlocked workstation, the pairing process will not complete.	1. Check that the user is on a secure network (office or VPN) try again. This will ensure the user is ready to begin pairing. 2. If the issue persists - Try to register again but proceed quickly through the pairing process. This will ensure that end user speed is not the cause of the issue. 3. If the issue persists - Guide the user to reboot workstation before trying again.
1530002	This error indicates the user has entered in an incorrect PIN for a security key during pairing or logging in. As compared to Mobile App users, Security Key users are required to enter a PIN to accomplish multi-factor authentication. When the user experiences this error, they will need administrator support to unlock their security key.	1. If you have a management PIN or a backup PIN method provided by your administrator, try this PIN at your next attempted login session. 2. If you do not have a secondary method to use your security key, reach out to your support team for further assistance.
1540001	This error indicates the pairing process has been canceled. Typically this is a user driven action however there is a possibility the user did not mean to select this option.	1. Wait 2 minutes and then proceed to unpair once again. This may allow enough time for pending requests to complete. 2. If the issue persists - identify at what step in pairing did the action cancel and inform your support team.
1550001	This error indicates that the workstation client may not be configured properly. This is typically not a production issue and may be experienced during sandbox or deployment testing by internal or pilot users. This can be caused by an invalid certificate template name during enrollment or that the certificate template does not exist.	1. Check that the user is on a secure network (office or VPN) try again. This will ensure the user is ready to begin pairing. 2. If the issue persists - guide the user to reboot the workstation before trying again. 3. If the issue persists - an admin may check the registry editor to see the configured certificate template and should ensure the name matches the configuration in AD Certificate Authority configuration.
1550002	This error indicates that the workstation user may not be configured properly. This is typically not a production issue and may be experienced during sandbox or deployment testing by internal or pilot users. This can be caused by user permissions which may not be authorized to enroll a certificate for the certificate template type.	1. Check that the user is on a secure network (office or VPN) try again. This will ensure the user is ready to begin pairing. 2. If the issue persists - guide the user to reboot the workstation before trying again. 3. If the issue persists - an admin may select the "User" template in AD and add user to "Group or user names" list under Security in template. Click on "Enroll" permissions and try again.
1550003	This error indicates that the workstation user may not be configured properly. This is typically not a production issue and may be experienced during sandbox or deployment testing by internal or pilot users. This can be caused by Active Directory Certificate Service not working properly.	1. Check that the user is on a secure network (office or VPN) try again. This will ensure the user is ready to begin pairing. 2. If the issue persists - guide the user to reboot the workstation before trying again. 3. If the issue persists - an admin may analyze HYPROneService log for more information and ensure that certificate for this user can be issued from the Certificate Authority.
1550005	This error indicates that the workstation user may not be configured properly. This is typically not a production issue and may be experienced during sandbox or deployment testing by internal or pilot users. This can be caused by the value of the public key pinning having been set to an invalid entry.	1. An admin may validate that the correct value is set for a user or whether a new value needs to be set. In the event that a new value in set, it is recommended to restart the HYPR service or reboot the machine following the change prior to trying to pair again. Once ready to pair, Check that the user is on a secure network (office or VPN) try again. This will ensure the user is ready to begin pairing. 2. If the issue persists - an admin may analyze HYPROneService log for more information and ensure that certificate for this user can be issued from the Certificate Authority.
1550006	This error indicates that the workstation user may not be configured properly. This is typically not a production issue and may be experienced during sandbox or deployment testing by internal or pilot users. This can be caused by the registry values having been set to an invalid entry or having experienced an issue during installation or upgrade.	1. An admin may validate that the correct values reside in the user's registry editor is set for a user or whether a new value needs to be set. In the event that a new value in set, it is recommended to restart the HYPR service or reboot the machine following the change prior to trying to pair again. Once ready to pair, Check that the user is on a secure network (office or VPN) try again. This will ensure the user is ready to begin pairing. 2. If the issue persists - an admin may analyze HYPROneService log for more information and ensure that certificate for this user can be issued from the Certificate Authority.
1550007	This error indicates an unknown event which is uncommon. Generally a user may retry the pairing or authentication and proceed successfully but may need further troubleshooting in the case where this issue is caused by a current or change in the enterprise environment. This is typically not a production issue and may be experienced during sandbox or deployment testing by internal or pilot users.	1. Check that the user is on a secure network (office or VPN) before pairing. This will ensure the user is ready to begin pairing. 2. If the issue persists - an admin may analyze HYPROneService log for more information and ensure that certificate for this user can be issued from the Certificate Authority.
1550008	This error indicates that the workstation client does not detect an internet connection.	1. Check that the user is on a secure network (office or VPN) before pairing. This will ensure the user is ready to begin pairing. 2. Validate that the user can open a webpage that is not cached and will successfully load on their workstation. Then have the user try to pair with HYPR. 3. If the issue persists - restart the HYPR service from services.msc and try to pair again. 4. If the issue persists - an admin may analyze HYPROneService log for more information and ensure that certificate for this user can be issued from the Certificate Authority.
1550009	This error indicates that the workstation user may not be configured properly. This is typically not a production issue and may be experienced during sandbox or deployment testing by internal or pilot users. This can be caused by the control center settings being in conflict with the type of end user seeking to pair and use the product.	An admin may need to validate on the control center that Domain Joined users is enabled. If it is not enabled, it is likely that a domain user is attempting to enroll and that functionality is not supported when the toggle is disabled. Once this is updated, the end user should be able to seamlessly pair with success.
1550010	The user is trying to enroll a security key using a local user account.	At this time, only domain joined user accounts are supported for certificate based Security Key login. Local user account enrollment for Security Keys are not currently supported without the use of a mobile app.
1570001	This error indicates that the workstation client does not detect an internet connection.	1. Check that the user is on a secure network (office or VPN) before pairing. This will ensure the user is ready to begin pairing. 2. Validate that the user can open a webpage that is not cached and will successfully load on their workstation. Then have the user try to pair with HYPR. 3. If the issue persists - restart the HYPR service from services.msc and try to pair again. 4. If the issue persists - an admin may analyze HYPROneService log for more information and escalate as needed.
1570002	This error indicates that the workstation client experienced an issue with the network.	1. Check that the user is on a secure network (office or VPN) before pairing. This will ensure the user is ready to begin pairing. 2. Validate that the user can open a webpage that is not cached and will successfully load on their workstation. Then have the user try to pair with HYPR. 3. If the issue persists - restart the HYPR service from services.msc and try to pair again. 4. If the issue persists - an admin may analyze HYPROneService log for more information and escalate as needed.
1570003	This error indicates that the workstation client experienced an unrecoverable error.	1. Restart the HYPR service from services.msc and try to pair again. If the user cannot restart the HYPR service, ask the user to reboot their workstation. 2. If the issue persists - an admin may analyze HYPROneService log for more information and escalate as needed.

(MacOS) WorkforceAccess v6.2.0+

Error Code	Cause	Recommended Resolution
1410001	This error indicates that the workstation client experienced a general error.	When encountering this error, you will often be presented information for troubleshooting inline with the error. Generally retrying the pairing process will resolve itself. If this does not work, ask the user to reboot their workstation.
1420001	This error indicates that the workstation client experienced a network error and a new attempt has been started.	1. Wait 2 minutes and then proceed to pair once again. This may allow enough time for pending requests to complete. 2. If the issue persists - reboot the computer and try to pair. This may ensure the computer did not reach an error state.
1420002	This error indicates that the workstation client experienced a network error during new device pairing.	1. Wait 2 minutes and then proceed to pair once again. This may allow enough time for any pending request or network instability to resolve. 2. If the issue persists - reboot the computer and try to pair. This may ensure the computer did not reach an error state.
1420003	This error indicates that the request has timed out. This may be the result of a registration taking longer than the allowed duration, or the failure to receive a response from the server during a step in the pairing process.	1. Wait 2 minutes and then proceed to pair once again. This may allow enough time for pending requests to complete. 2. If the issue persists - reboot the computer and try to pair. This may ensure the computer did not reach an error state.
1420004	This error indicates that device pairing failed. This may happen for a number of reasons with the most common cause due to instability in the network connection at a critical step in the process.	1. Wait 2 minutes and then proceed to pair once again. This may allow enough time for pending requests to complete. 2. If the issue persists - reboot the computer and try to pair. This may ensure the computer did not reach an error state.
1420005	This error indicates that device unpairing failed. This may happen for a number of reasons with the most common cause due to instability in the network connection at a critical step in the process.	1. Wait 2 minutes and then proceed to unpair once again. This may allow enough time for pending requests to complete. 2. If the issue persists - reboot the computer and try to unpair. This may ensure the computer did not reach an error state.
1430001	This error indicates that the user was unable to authenticate during the pairing process. Users are asked to enter in their password one last time during pairing to ensure that the person pairing is the individual who logged into the workstation.	1. Wait 2 minutes and then proceed to pair once again. During the authentication step, enter your credential slowly and carefully. 2. If the issue persists - reboot the computer and try to pair. This may ensure the computer did not reach an error state.
1430002	This error indicates that device unpairing failed. This may happen for a number of reasons with the most common cause due to instability in the network connection at a critical step in the process.	1. Wait 2 minutes and then proceed to unpair once again. This may allow enough time for pending requests to complete. 2. If the issue persists - reboot the computer and try to unpair. This may ensure the computer did not reach an error state.
1440001	This error indicates that the user canceled the pairing process when asked to confirm their authorization with their current password.	Wait 2 minutes and then proceed to pair once again. This may allow enough time for pending requests to complete. During the step where a prompt appears, do not dismiss it. Enter your credential to complete pairing.
1450001	This error indicates that the workstation client experienced an error while unlocking the user.	Wait 2 minutes and then proceed to authenticate again. If this does not resolve the issue, try a reboot and see if the issue persists.
1470001	This error indicates that the workstation client experienced an issue with the network.	1. Make sure that Server URL is reachable from the web browser on the same computer. You can try to login to your Control Center 2. If the issue persists - an admin may analyze HYPROneService log for more information and escalate as needed.
1470002	This error indicates that the workstation client experienced an unrecoverable error.	If the issue persists - an admin may analyze HYPROneService log for more information and escalate as needed.

(Server) HYPR Server v6.2.0+

Please note that these errors could be displayed in the mobile application as well. It indicates that the root cause of the problem is the server related error.

Error Code	Cause	Recommended Resolution
1201001	Usually the result of the server under load/contention. The authorization request has been interrupted for the ClientRegistrationComplete request.	1. Check the logs for any indications of server failures. 2. The user can retry after a minute.
1201003	This error indicates that the push provider is not configured for this application.	Configure a Push Provider in the Control Center.
1202002	The user does not have any registered devices for the rpAppId:	The user should register a device under the requested application.
1202001	This error indicates a generic server issue.	The administrator should check the server logs for indicators of an unhandled error. If the issue persists, contact HYPR support.
1201010	This error indicates that an invalid image was uploaded.	The max file size is 256kb. Please try again with a smaller image.
1201011	The session is not valid for this request because it has timed out. Took too long to complete action. The timeout is set in nginx. Check settings and verify action is complete within that time.	Try again. Contact HYPR support if the issue persists.
1202003	The request provided invalid data.	Try again. Contact HYPR support if the issue persists.
1202004	The provided access token is invalid.	Check the access token supplied in the API request. Re-issue a new access token if needed.
1201012	The current machine does not exist in the user's session.	Wait one minute for the session to expire, and then try again.
1201013	The request is invalid for the user's session.	Wait one minute for the session to expire, and then try again.
1201014	The user's session cannot be found.	Wait one minute for the session to expire, and then try again.
1202005	This error indicates that the current license is invalid.	The administrator should check that the license server is reachable and that a valid license has been applied.
1201015	This error indicates that there was a problem registering the user for push notifications.	The administrator should check that the API token is valid in their push notification settings.
1201016	The user's session cannot be found.	Wait one minute for the session to expire, and then try again.
1002006	Authentication failed due to an invalid PIN code.	Wait one minute for the session to expire, and then try again.
1201017	This indicates that there was an internal error creating an SSL client.	Wait one minute and try again. If the issue persists, contact HYPR support.
1202007	This indicates that an internal service was not reachable.	The administrator should check that all services are available and running.
1201018	Registration failed due to a timeout.	The user can wait a minute and try again.
1201020	The sessionId provided in the request is invalid.	Wait for session to timeout over a minute or so. Re-try
1202008	This indicates that the license server is not reachable.	The administrator should check that the license server is available and running.
1201021	There was a problem updating the status for the machine.	Check that the machine is paired and try again.
1201022	The authentication failed due to the presence of another pending authentication request.	Wait for a minute and try again.
1201023	The operation failed due to invalid request parameters.	Wait for a minute and try again. Contact support if the issue persists.
1202009	An invalid application was used.	Check that you have created and set up the application in the Control Center.
1202010	The FIDO operation failed due to invalid request data.	Try again. Contact support if the issue persists.
1202011	The workstation session was not found.	Wait for session to timeout over a minute or so. Re-try
1202012	There was an issue with the websocket connection between the server and workstation.	Use Offline Mode or restart the computer and try again.
1202013	Authorization between the device and workstation failed.	Check that the workstation can reach the Active Directory server, and that the workstation HYPR service is running. Otherwise restart the computer, or use Offline Mode.
1202014	The Control Center failed to reach the UAF server.	Check that the UAF server is running and reachable.
no usages	The authorization request has timed out: ClientAuthorizationRequest( version=1	Re-try. Can happen if the user took too long or the server was overwhelmed with traffic
no usages	A matching mobile request was not found for this ClientAuthorizationComplete request: ClientAuthorizationComplete(sessionId=null	Wait for session to timeout over a minute or so. Re-try
1201002	The user already has a pending registration request.	Device pairing may still be in progress. Try again in a couple of minutes, or contact support if the issue persists.
1201004	The user has a pending request with the same ID.	Wait for session to timeout over a minute or so. Re-tryaRegistration may still be in progress. Try again in a couple of minutes, or contact support if the issue persists.
1201005	The session provided is not valid.	Wait a minute and try again, or contact support if the issue persists.
1202016	The workstation does not appear to be registered.	Try again or contact support if the issue persists.
1201007	The registration request is invalid.	Try again after a minute or contact support if the issue persists.
1202017	This error indicates a problem with the SSL certificate.	Ensure that the certificate is in the correct format and try again.
1201008	This error indicates that the client cancelled registration and the current operation cannot proceed	Wait one minute and try again.
1202018	This error indicates an issue creating a session.	Code problem. Admin to check logs for session creation problem.
1202019	Ensure that the Action ID (Authentication Policy) is setup in Control Center for the Application. Action ID does not match Client Action ID.	Admin to check CC for policy setup.
1201006	The client or device software version is incompatible with the server.	Please contact support to confirm that you have the correct software version.
1202009	The application could not be found.	Please check that you have completed the application setup in the Control Center.
1202020	The application setup is incomplete or incorrect.	Please ensure that the action ID is configured for RPAppId in the Control Center.
1202021	Invalid data was supplied in the JSON request.	Check logs for specific request. Check API for correct format.
1202022	Could not find the device requested.	Please make sure your device has been paired with the computer.
1202023	There was a problem sending push notifications to the user.	Please make your device is paired, and push notifications are enabled.
1202024	There was an issue finding the user for the requested application.	Please ensure your device is registered to login with this website.
1201019	There was an issue communicating with the client.	Wait one minute and try again.
1202025	The operation on the workstation has timed out.	Wait one minute and try again.
1202026	There was an issue with push provider configuration.	Please make sure push notifications are enabled, and your device has been paired with the device manager.
1202027	There was an issue with push provider configuration. Either push is disabled or the url is null.	Check Control Center logs and contact HYPR support for assistance.
1202028	There was an issue with the challenge used in the FIDO operation.	Wait a minute and try again, check the audit log within the Control Center.
1201009	An authentication or registration attempt already exists.	Please wait a minute and try again. If the issue continues, check the audit log within the Control Center.
1201026	An authentication or registration attempt already exists.	Please wait a minute and try again. If the issue continues, check the audit log within the Control Center.
1201027	There's a pending unpairing request for this device.	Ensure that another de registration attempt is not in progress. Wait for a minute and re-try.
1202029	There was an error in the adapter processing. The adapter URL is not correct	Admin to ensure that the adapter url is valid and reachable from the server.
1202030	There was an error in the adapter processing. This was the resulting response bean from the adapter	Admin to check server logs for extension problems.
1202031	There is an issue with the extension JAR package.	Please ensure the identity provider extension follows the rules, and try again.
1202032	Failed to stop or unload the extension.	Please ensure the identity provider extension follows the rules, and try again.
1202033	Failed to load extensions. Path: <filesystem path where ext is stored>	Admin can look at server logs for failure details. Usually, it's filesystem permissions issue.
1203034	There was a problem with your identity provider extensions.	Admin to check server logs for the specific extension problem. A run time exception for a 3rd party product is not known to the server.

(Android) HYPR App & SDK 6.2.0+

Error Code	Cause	Recommended Resolution
11100	This error indicates the user has entered in an incorrect 'user presence' check when prompted for their workstation password. During the pairing process, an enterprise may require the user to type in their current password one final time to validate that they are the professional who has logged into the workstation. When this is incorrectly entered, such as in the case where a rogue or malicious user tries to register on a colleague's unlocked workstation, the pairing process will not complete.	1. Check that the user is on a secure network (office or VPN) try again. This will ensure the user is ready to begin pairing. 2. If the issue persists - Try to register again but proceed quickly through the pairing process. This will ensure that end user speed is not the cause of the issue. 3. If the issue persists - Guide the user to reboot workstation before trying again.
111010	Authenticator does not support the attestation type. This occurs when a policy is set to use a Full Basic Authenticator ADP SDK, but the developer used a Surrogate Authenticator Prefs SDK instead.	Modify your policy to use the correct AAIDs.
114010	Any generic failure that is not caused by the user but rather the underlying framework. Example: null pointer exceptions, invalid states, operating system errors, invalid develop implementations of interfaces, etc.	Check the logs for more details.
114011	The FacetId generated by the top-level application is not present on the Fido Server.	The FacetId needs to be added to the Fido Server FacetId list.
114012	There was no valid authenticator on the device that matched the policy from the server.	Discovery Failed due to no Authenticator matching the policy. Check your policy that is being used for valid authenticators.
114013	The negotiated server API version is too low for the attempted operation.	Upgrade the server to a version that supports the operation.
114020	The authenticator hardware is not supported on the device.	Authenticator Hardware Not Supported.
114030	The attempted authenticator during an authentication is not registered.	Register the authenticator before trying to authenticate with it.
114040	There is a list of transactions specified in the JSON, however, there is no transaction with the type "text/plain".	Correct the JSON being sent in the push notification.
114050	Permission was not given to use the camera for a barcode scan.	Give permission to the application to use the camera to scan the barcode.
114060	Server sent back an error.	Check server logs for more detail.
114070	Invalid SSL credentials were used.	Make sure that your SSL credentials are correct.
114071	Malformed Server URL was received or set in the application.	Check the URLs being set in the application or in the barcode.
114080	No internet connection.	Operation failed. Seems like you have no internet connection. Make sure you are connected to the internet and try again.
114090	The application was backgrounded.	User backgrounded the application, which is a cancel.
114100	Barcode scanner failed to start.	Internal SDK error. Check the logs for more details.
114101	Barcode scanner received a null camera exception.	Internal SDK error. Check the logs for more details.
114102	Barcode scanner received an access error.	Internal SDK error. Check the logs for more details.
114103	Barcode scanner preview exception.	Internal SDK error. Check the logs for more details.
114104	No barcode captured.	Internal SDK error. Check the logs for more details.
114105	Barcode JSON exception.	Internal SDK error. Check the logs for more details.
114110	Machine null during push notification received.	Internal SDK error. Check the logs for more details.
114120	Relying Party Adapter response not valid.	Internal SDK error. Check the logs for more details.
114121	Relying Party Adapter response database error.	Internal SDK error. Check the logs for more details.
114122	Relying Party Adapter workstation unlock user logged out.	Internal SDK error. Check the logs for more details.
114123	Relying Party Adapter workstation unlock user already logged in.	Internal SDK error. Check the logs for more details.
114124	Relying Party Adapter workstation unlock authentication timed out.	Internal SDK error. Check the logs for more details.
114125	Relying Party Adapter workstation unlock rejected by workstation.	Internal SDK error. Check the logs for more details.
114126	Relying Party Adapter workstation unlock complete rejected by workstation.	Internal SDK error. Check the logs for more details.
114130	Relying Party Adapter workstation lock failed, workstation unreachable.	Check if the workstation has internet access.
114140	Fido Payload Adapter JSON exception.	Internal SDK error. Check the logs for more details.
114150	Fido Client Adapter invalid activity action.	Internal SDK error. Check the logs for more details.
114160	Fido Client Manager JSON exception.	Internal SDK error. Check the logs for more details.
114161	Fido Client Manager could not find Fido Client Activity.	Internal SDK error. Check the logs for more details.
114162	Fido Client Manager no activity status result received.	Internal SDK error. Check the logs for more details.
114163	Fido Client Manager invalid activity result received.	Internal SDK error. Check the logs for more details.
114164	Fido Client Manager activity data result null.	Internal SDK error. Check the logs for more details.
114165	Fido Client Manager callback null.	Internal SDK error. Check the logs for more details.
114166	Fido Client Manager no discovery data received.	Internal SDK error. Check the logs for more details.
114167	Fido Client Manager invalid UAF intent type.	Internal SDK error. Check the logs for more details.
114168	Fido Client Manager intent type missing.	Internal SDK error. Check the logs for more details.
114169	Fido Client Manager missing error code.	Internal SDK error. Check the logs for more details.
114170	Fido Client Manager invalid error code.	Internal SDK error. Check the logs for more details.
114180	Deregister Activity not receive lower level error status code.	Internal SDK error. Check the logs for more details.
114181	Deregister Activity AAIDs JSON exception.	Internal SDK error. Check the logs for more details.
114200	QR Code parsing error.	Internal SDK error. Check the logs for more details.
114210	Machine progress exception.	Internal SDK error. Check the logs for more details.
114211	Machine progress device setup exception.	Internal SDK error. Check the logs for more details.
114212	Machine progress device setup callback success exception.	Internal SDK error. Check the logs for more details.
114213	Machine progress device setup callback fail exception.	Internal SDK error. Check the logs for more details.
114214	Machine progress get fido registrations exception.	Internal SDK error. Check the logs for more details.
114215	Machine progress add invalid OOB entry type.	Internal SDK error. Check the logs for more details.
114216	Machine progress device setup success machine null.	Internal SDK error. Check the logs for more details.
114217	Machine progress add post fido exception.	Internal SDK error. Check the logs for more details.
114220	Machine device setup exception.	Internal SDK error. Check the logs for more details.
114230	Machine delete exception.	Internal SDK error. Check the logs for more details.
114240	Machine unlock exception.	Internal SDK error. Check the logs for more details.
114250	Machine offline unlock exception.	Internal SDK error. Check the logs for more details.
114300	Machine operation init null.	Internal SDK error. Check the logs for more details.
114301	Machine operation audit event size 0.	Internal SDK error. Check the logs for more details.
114302	Machine operation not supported in API version, too low.	Internal SDK error. Check the logs for more details.
114303	Machine operation init machine null.	Internal SDK error. Check the logs for more details.
114310	Machine operation authentication request username empty.	Internal SDK error. Check the logs for more details.
114140	Machine operation log message empty.	Internal SDK error. Check the logs for more details.
114350	Machine operation device setup pin empty.	Internal SDK error. Check the logs for more details.
114351	Machine operation device setup callback response invalid.	Internal SDK error. Check the logs for more details.
114360	Machine operation device registration request empty parameter.	Internal SDK error. Check the logs for more details.
114361	Machine operation device registration request invalid.	Internal SDK error. Check the logs for more details.
114362	Machine operation device registration callback response invalid.	Internal SDK error. Check the logs for more details.
114370	Machine operation device setup invalid RP type.	Internal SDK error. Check the logs for more details.
114371	Machine operation device setup callback response invalid.	Internal SDK error. Check the logs for more details.
114380	Machine operation website deregistration device ID empty.	Internal SDK error. Check the logs for more details.
114381	Machine operation website deregistration request machines empty.	Internal SDK error. Check the logs for more details.
114382	Machine operation website deregistration request returned machines empty.	Internal SDK error. Check the logs for more details.
114390	Machine operation workstation deregistration device ID empty.	Internal SDK error. Check the logs for more details.
114391	Machine operation workstation deregistration request machines empty.	Internal SDK error. Check the logs for more details.
114392	Machine operation workstation deregistration request returned machines empty.	Internal SDK error. Check the logs for more details.
114400	Machine operation machine status request device ID empty.	Internal SDK error. Check the logs for more details.
114401	Machine operation machine status request RP App ID empty.	Internal SDK error. Check the logs for more details.
114402	Machine operation machine status callback response invalid.	Internal SDK error. Check the logs for more details.
114403	Machine operation machine status callback App Profile empty.	Internal SDK error. Check the logs for more details.
114410	Machine operation workstation unlock init invalid state.	Internal SDK error. Check the logs for more details.
114411	Machine operation worstation unlock cancel request session ID empty.	Internal SDK error. Check the logs for more details.
114420	Machine operation workstation unlock complete machine empty.	Internal SDK error. Check the logs for more details.
114421	Machine operation workstation unlock complete session ID empty.	Internal SDK error. Check the logs for more details.
114422	Machine operation workstation unlock complete invalid HMAC.	Internal SDK error. Check the logs for more details.
114423	Machine operation workstation unlock complete login cert empty.	Internal SDK error. Check the logs for more details.
114424	Machine operation workstation unlock complete request parameter empty.	Internal SDK error. Check the logs for more details.
114425	Machine operation workstation unlock complete callback invalid.	Internal SDK error. Check the logs for more details.
114426	Machine operation workstation unlock complete calback invalid offline payload.	Internal SDK error. Check the logs for more details.
114427	Machine operation workstation unlock complete callback machine empty.	Internal SDK error. Check the logs for more details.
114430	Machine operation workstation unlock session ID empty.	Internal SDK error. Check the logs for more details.
114431	Machine operation workstation unlock callback counter error.	Internal SDK error. Check the logs for more details.
114432	Machine operation workstation unlock callback offline exception.	Internal SDK error. Check the logs for more details.
114433	Machine operation workstation unlock callback machine empty.	Internal SDK error. Check the logs for more details.
114434	Machine operation workstation unlock callback response invalid.	Internal SDK error. Check the logs for more details.
114440	Machine operation magic link callback response invalid.	Internal SDK error. Check the logs for more details.
114450	Machine operation server info callback response invalid.	Internal SDK error. Check the logs for more details.
114460	Machine operation push token request device ID empty.	Internal SDK error. Check the logs for more details.
114461	Machine operation push token request machine ID empty.	Internal SDK error. Check the logs for more details.
114462	Machine operation push token request machine username empty.	Internal SDK error. Check the logs for more details.
114463	Machine operation push token request new token hmac empty.	Internal SDK error. Check the logs for more details.
114464	Machine operation push token request new token value empty.	Internal SDK error. Check the logs for more details.
114470	Machine operation registration cancel request PIN empty.	Internal SDK error. Check the logs for more details.
114480	Machine operation authentication cancel request session ID empty.	Internal SDK error. Check the logs for more details.
114490	Features operation features callback response invalid.	Internal SDK error. Check the logs for more details.
114500	Machine operation lock rquest session ID empty.	Internal SDK error. Check the logs for more details.
114501	Machine operation lock rquest RP app ID empty.	Internal SDK error. Check the logs for more details.
114502	Machine operation lock rquest device ID empty.	Internal SDK error. Check the logs for more details.
114503	Machine operation lock rquest machine ID empty.	Internal SDK error. Check the logs for more details.
114504	Machine operation lock rquest machineusername ID empty.	Internal SDK error. Check the logs for more details.
1110020	The PIN used during headless PIN registration was null.	Make sure that you are using the correct PIN. If the issue persists, please contact your support for more detail.
1110030	The PIN used during headless PIN authentication was null.	Make sure that you are using the correct PIN. If the issue persists, please contact your support for more detail.
1110040	The PIN used during Headless Pin Registration was invalid.	Make sure that you are using the correct PIN. If the issue persists, please contact your support for more detail.
1110050	The PIN used during headless PIN authentication was invalid.	Make sure that you are using the correct PIN. If the issue persists, please contact your support for more detail.
1111040	There were more fingerprint failures after the first lockout, resulting in the fingerprint reader being permanently locked.	Too many failure attempts. Fingerprint reader is locked. Please go to Android Settings and unlock fingerprint.
1111050	Your request to authenticate this device didn't complete in time.	Your request to authenticate this device didn't complete in time. Please try again.
1111060	Not enough storage is available for the operation to proceed.	Please free up disk space and try again.
1112010	Generic face registration failed with an unknown cause.	Please try again. If the issue persists, please contact your support.
1112010	Generic face authentication failed with an unknown cause.	Please try again. If the issue persists, please contact your support.
1112020	Face registration timed out.	Your request to enroll this device didn't complete in time. Please try again.
1112020	Face authentication timed out.	Your request to authenticate didn't complete in time. Please try again.
1112030	Face registration via Sensory failed.	Something went wrong with your authentication method. Please try again. If the issue persists, please contact your support.
1112030	Face authentication via Sensory failed.	Something went wrong with your authentication method. Please try again. If the issue persists, please contact your support.
1112060	Physical hardware not available on device.	Camera is currently not available. Please close any application which may have the camera in use.
1112070	This issue indicates that there is not enough storage available on device when attempting to use face recognition.	Not enough storage is available. Please free up memory and try again.
1113010	Generic voice registration failed with an unknown cause.	Something went wrong with your authentication method. Please try again. If the issue persists, please contact your support.
1113010	Generic voice authentication failed with an unknown cause.	Something went wrong with your authentication method. Please try again. If the issue persists, please contact your support.
1113030	Voice registration failed due to Sensory returning this error code.	Something went wrong with your authentication method. Please try again. If the issue persists, please contact your support.
1113030	Voice authentication failed due to Sensory returning this error code.	Something went wrong with your authentication method. Please try again. If the issue persists, please contact your support.
1113040	Voice permissions denied.	This app needs permission to use the microphone. Please enable it in the device settings.
1113050	The user has not registered with voice authentication.	Be sure that the user has registered voice authentication and try again.
1113060	Microphone is currently not available.	Please close any application which may have the microphone in use.
1113070	This error indicates there is not enough storage available on device to complete an operation with the voice authenticator.	Please free up memory and try again.
1114020	Palm recognition failed due to an unknown error.	Something went wrong with your authentication method. Please try again.
1114030	Palm recognition failed due to the palm not being recognized.	Please try again if your palm is registered with this device.
11100	In PIN Authenticator, cancel button or back button pressed.	No resolution is needed as this is normal behavior.
11100	During a fingerprint authentication, the cancel button or back button was pressed.	No resolution is needed as this is normal behavior.
11100	During a face authentication, the cancel button or back button was pressed.	No resolution is needed as this is normal behavior.
11100	During a voice authentication, the cancel button or back button was pressed.	No resolution is needed as this is normal behavior.
114012	Discovery failed due to no authenticator matching the policy.	Be sure that you are using an authentication that matches with the set policy. Please contact your support for more detail.
114020	This error indicates that the authenticator hardware is not supported, which resulted in an invalid application state.	This error is unlikely, but may occur if HYPR is used with a non-HYPR FIDO Client. Please contact your support for more detail.
114030	The authenticator registration does not exist in the ASM database.	Be sure that the authenticator is registered. If the issue persists, please contact your support for more detail.
114050	Camera permissions were denied when attempting to scan a barcode.	This app needs permission to use the camera. Please enable it in the app's settings.
114060	Server error occurred.	Please try again. or contact your support for more detail
114080	No network connection exists.	Make sure you are connected to the internet and try again.
114090	This error occurs if the app was backgrounded at any time during an operation.	Please try again, making sure to not background the app during an operation.
1110010	Authentication PIN incorrect.	Your PIN is incorrect. Please try again.
1110020	Registration Headless PIN null.	A headless PIN is not being sent properly during registration. Please check the implementation.
1110030	Authentication Headless PIN null.	A headless PIN is not being sent properly during authentication. Please check the implementation.
1110040	Registration Headless PIN invalid.	A headless PIN is not being sent properly during registration. Please check the implementation.
1110050	Authentication Headless PIN invalid.	A headless PIN is not being sent properly during registration. Please check the implementation.
1111010	Biometric not recognized.	Biometric not recognized. Please try again.
1111020	No biometrics found on this device.	No biometrics found on this device. You must add one in your phone's settings.
1111030	Too many failure attempts were made with the Biometric Prompt.	Too many failure attempts. Please wait to retry.
1111040	Too many failure attempts were made with the Biometric Prompt and it is permanently locked until reset in the Settings.	Too many failure attempts. Biometric reader is locked. Please go to Android Settings and unlock biometrics.
1111050	The Biometric Prompt authentication took too long.	Your request to authenticate this device didn't complete in time. Please try again.
1111060	The device ran out of storage space.	Not enough storage is available. Please free up memory and try again.
1112010	Sensory Face failed.	Please try again.
1112020	Sensory Face timed out.	Please try again.
1112030	Sensory Face failed with an external error.	Please try again.
1112040	Sensory Face camera was denied when attempting to use face recognition.	This app needs permission to use the camera. Please enable it in the device settings.
1112050	Sensory Face no face registered.	Be sure you are registered for face recognition.
1112060	Sensory Face media was unavailable.	Check to be sure no other application is using the camera.
1112070	Sensory Face the device ran out of storage space.	Not enough storage is available. Please free up memory and try again.
1113010	Sensory Voice failed.	Please try again.
1113020	Sensory Voice registration timed out.	Your request to enroll this device didn't complete in time. Please try again.
1113030	Sensory Voice authentication timed out.	Your request to authenticate didn't complete in time. Please try again.
1113040	Sensory Voice was denied microphone permissions when attempting to use voice recognition.	This app needs permission to use the microphone. Please enable it in the device settings.
1113050	Sensory Voice no voice registered.	Be sure you are registered for voice recognition.
1113060	Sensory Voice media was unavailable.	Check to be sure no other application is using the microphone.
1113070	Sensory Voice the device ran out of storage space.	Not enough storage is available. Please free up memory and try again.
1114010	Palm registration failed due to error.	Something went wrong with your authentication method. Please try again.
1114020	Palm authentication failed due to error.	Something went wrong with your authentication method. Please try again.
1114030	Palm authentication failed due to not recognized.	The palm was not recognized. Please try again.
1114040	Palm permissions denied.	This app needs permission to use the camera. Please enable it in the device settings.
1114050	Your request to enroll/authenticate this device didn't complete in time.	Your request to enroll/authenticate this device didn't complete in time. Please try again.
114111	This authentication request is expired.	User should start a new authentication.
115000	Action could not be started because HYPR is not initialized	Internal SDK error. Check the logs for more details.

(iOS) HYPR App & SDK 6.2.0+

Error Code	Cause	Recommended Resolution
10128	Operation cancelled by user	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
105017	FIDO authentication user cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
105007	FIDO registration user cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
106007	FIDO registration user cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
106011	FIDO registration user cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
106030	FIDO sign user cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
106035	FIDO transaction sign user cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
10999	The operation was cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
104018	FIDO authentication user cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
104011	FIDO registration user cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
107031	Face authenticator user cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
107029	Face authenticator user cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
107035	Face authenticator user cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
107004	Face ID authenticator user cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
107024	Face ID authenticator user cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
107012	Fingerprint authenticator user cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
107023	Fingerprint authenticator user cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
107019	PIN authenticator user cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
107046	Voice authenticator user cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
107044	Voice authenticator user cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
107050	Voice authenticator user cancelled	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow.
10201	ADP failed	Make sure that ADP initialized with correct configuration. Check debugger logs for more details.
10129	Data verification failed	Check debugger logs for more details.
10300	Key not found	Check debugger logs for more details.
10200	Secure Enclave failed	Check debugger logs for more details.
10100	SHA256 result not available	Check debugger logs for more details.
108002	ADP already initialized	Make sure that ADP initialized with correct configuration. Check debugger logs for more details.
108001	ADP not available	Make sure that ADP initialized with correct configuration. Check debugger logs for more details.
108000	ADP not initialized	Make sure that ADP initialized with correct configuration. Check debugger logs for more details.
105019	FIDO required attestation not supported	Check debugger logs for more details.
105020	FIDO transaction content cannot be rendered.	Check debugger logs for more details and make sure that imlementation follows SDK documentation recomendations.
105018	This error could happend when SDK Developer is trying to use unsupported FIDO command.	Check debugger logs for more details and make sure that imlementation follows SDK documentation recomendations.
105021	Unknkown error occured during the authentication.	1. User should try to authenticate again. 2. User should restart the application and try again. 3. Admin should analyze Audit Trail logs for this user if the problem is still happening.
105016	The user is trying to register with Authenticator, but it's not registered. Usually, it happens when authentication policy contains Authenticator which wasn't registered or was removed by the user.	1. Ensure that user have registered with this account before 2. Try to re-register and try again 3. Check logs for more details.
105022	FIDO cannot find key handles for the current username, aaid, keyIds.	1. Ensure that user have registered with this account before 2. Try to re-register and try again 3. Check logs for more details.
105012	FIDO authenticator for index not found	1. Ensure that user have registered with this account before 2. Try to re-register and try again 3. Check logs for more details.
105011	FIDO invalid authentication ASM request	1. Ensure that user have registered with this account before 2. Try to re-register and try again 3. Check logs for more details.
105013	FIDO authentication signing ASM request invalid	1. User should restart the application and try to authenticate again. 2. Check debugger logs for more details.
105010	FIDO Invalid authentication ASM request	1. User should restart the application and try to authenticate again. 2. Check debugger logs for more details.
105027	FIDO deregistration failed (multiple reasons)	1. User should try to de-register again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
105025	FIDO deregistration authenticator not found	1. User should try to de-register again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
105024	FIDO deregistration invalid ASM request	1. User should try to de-register again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
105030	FIDO deregistration cannot delete public private key pair	1. User should try to de-register again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
105029	FIDO deregistration khAccessTokenHash from server is not equal to the local one	1. User should try to de-register again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
105023	FIDO deregistration invalid ASM request type	1. User should try to de-register again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
105028	FIDO deregistration cannot find key handles for the current aaid, keyIds	1. User should try to de-register again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
105026	FIDO deregistration invalid ASM request	1. User should try to de-register again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
105038	FIDO get information invalid ASM request type	1. User should try to register again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
105037	FIDO get registration authenticator not found. Usually this error wiill occur when authentication policy has authenticators which are not available on user's device.	Admin should collect more informaton about user's device and ensure that authenticaton policy contains supported authentication method.
105035	FIDO get registration invalid ASM request	1. User should try to register again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
105036	FIDO get registration invalid ASM request type	1. User should try to register again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
105032	FIDO open settings authenticator not found	Try again or request support for more assistance.
105033	This error could happend when SDK Developer is trying to use unsupported FIDO command.	Check debugger logs for more details and make sure that imlementation follows SDK documentation recomendations.
105031	FIDO open settings invalid ASM request type	Try again or request support for more assistance.
105034	FIDO open setting unknown error	Try again or request support for more assistance.
105003	FIDO authenticator for index not found	Try again or request support for more assistance.
105002	FIDO invalid registration ASM request	1. User should try to register again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
105001	FIDO Invalid registration ASM request	1. User should try to register again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
105004	FIDO cannot generate registration request	Try again or request support for more assistance.
105006	FIDO registration failed (multiple reasons)	Try again or request support for more assistance.
105008	FIDO required attestation not supported	Try again or request support for more assistance.
105005	Error with ASM Registration	1. User should try to register again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
105005	Error with ASM Registration	1. User should try to register again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
10102	The authentication operation failed	Try again or request support for more assistance.
106019	FIDO deregistration authenticator not found	Try again or request support for more assistance.
106018	FIDO deregistration invalid authenticator command	Try again or request support for more assistance.
106036	FIDO get information invalid command	Try again or request support for more assistance.
106037	FIDO open settings invalid command	Try again or request support for more assistance.
106008	FIDO registration failed	Try again or request support for more assistance.
106009	FIDO registration result unavailable	Try again or request support for more assistance.
106010	FIDO registration result unknown	Try again or request support for more assistance.
106002	FIDO registration authenticator not found	Try again or request support for more assistance.
106016	FIDO registration key generation failed	Try again or request support for more assistance.
106017	FIDO registration hashing and signing response error	Try again or request support for more assistance.
106003	FIDO registration no public key data found	Try again or request support for more assistance.
106006	FIDO registration no raw signature created	Try again or request support for more assistance.
106004	FIDO registration no registration data found	Try again or request support for more assistance.
106005	FIDO registration no signed data created	Try again or request support for more assistance.
106001	FIDO registration invalid authenticator command	Try again or request support for more assistance.
106015	FIDO registration user already enrolled	Try again or request support for more assistance.
106012	FIDO registration enrollment failed	Try again or request support for more assistance.
106013	FIDO registration enrollment unavailable	Try again or request support for more assistance.
106014	FIDO registration enrollment result unknown	Try again or request support for more assistance.
106029	FIDO sign failed (multiple reasons)	Try again or request support for more assistance.
106028	FIDO sign unknown error	Try again or request support for more assistance.
106031	FIDO authentication user not enrolled	Try again or request support for more assistance.
106021	FIDO authentication authenticator not found	Try again or request support for more assistance.
106025	FIDO sign hashing and signing response error	Try again or request support for more assistance.
106022	FIDO authentication authenticator info not found	Try again or request support for more assistance.
106027	FIDO no raw signature created	Try again or request support for more assistance.
106026	FIDO failed to sign the command	Try again or request support for more assistance.
106033	FIDO transaction sign failed (multiple reasons)	Try again or request support for more assistance.
106034	FIDO transaction content cannot be rendered	Try again or request support for more assistance.
106032	FIDO transaction sign unknown error	Try again or request support for more assistance.
106020	FIDO authentication invalid sing command	Try again or request support for more assistance.
106023	FIDO authentication user not enrolled	Try again or request support for more assistance.
106024	FIDO cannot find key handles for the current username, aaid, keyIds	Try again or request support for more assistance.
104016	FIDO Failed to initialize ASM	Try again or request support for more assistance.
104019	FIDO authentication failed (multiple reasons)	Try again or request support for more assistance.
104020	FIDO authentication ASM request invalid	Try again or request support for more assistance.
104021	FIDO authentication UAF response invalid	Try again or request support for more assistance.
104017	FIDO no authenticators matched during authentication	Try again or request support for more assistance.
104015	FIDO Invalid authentication request	Try again or request support for more assistance.
104023	FIDO Failed to initialize ASM	Try again or request support for more assistance.
104024	FIDO deregistration failed (multiple reasons)	Try again or request support for more assistance.
104025	FIDO deregistration ASM request invalid	Try again or request support for more assistance.
104022	FIDO Invalid deregistration request	Try again or request support for more assistance.
104004	FIDO http used instead of https in UAF request	Ensure that you're using https FIDO Server URL and try again.
104001	FIDO UAF Protocol object missing/malformed. Usually this happens during the integration with the server.	1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
104003	Invalid request type in the FIDO Client.	1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
104006	FIDO Wrong number of facets retrieved from url	1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
104009	FIDO Failed to initialize ASM	1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
104012	FIDO registration failed (multiple reasons)	1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
104013	FIDO registration ASM request invalid	1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
104010	FIDO no authenticators matched during registration	1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
104008	FIDO Invalid registration request	1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
104014	FIDO registration UAF response invalid	1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
104027	FIDO Consumer’s AAID picker view controller doesn’t conform to HYPRAuthenticatorPicker category	1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
104007	FIDO Wrong facets format or content	1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
104005	FIDO Retrieving facets from url failed	1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
104002	FIDO UAF Protocol object missing/malformed	1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
104026	FIDO unknown operation	1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
1020000	HMAC validation failed	1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
10102	The deregister operation failed	Try again or request support for more assistance.
107025	Face authenticator user already enrolled	User should deregister before trying to register with this authenticator.
107028	Face authenticator cannot render content	Try again or request support for more assistance.
107030	Face authenticator user enrollment failed	Try again or request support for more assistance.
107032	Face authenticator enrollment timeout	User should try to register again and ensure that registration done in 60 seconds or less.
107033	Face authenticator user enrollment result unknown	Try again or request support for more assistance.
107038	Face authenticator user data migration to new version failed	Try again or request support for more assistance.
107026	User is not enrolled with Face Authenticator.	Try again or request support for more assistance.
107034	Face authenticator user verification failed	Try again or request support for more assistance.
107036	Face authenticator verification timeout	Your request did not complete in time. Please try again.
107037	Face authenticator verification result unknown	Try again or request support for more assistance.
107001	Face ID authenticator error. This is a system error returned by the iOS Interface communicating with Face ID Authenticator on the device.	Try again or request support for more assistance.
107006	Face ID authenticator user already enrolled	Try again or request support for more assistance.
107003	Face ID authenticator cannot render content	Try again or request support for more assistance.
107005	Face ID biometric removal not supported	Try again or request support for more assistance.
107002	Face ID authenticator not available. Usually this happens when iOS can't use Face ID. This can happend due to incomplete permissions or the problem with Face ID on this device.	1. User should ensure that Face ID permissions are granted for this application in the device settings. 2. Ensure that Face ID can be used by any other application. 3. Reboot the device and try again.
107009	Fingerprint authenticator error	Try again or request support for more assistance.
107014	Fingerprint authenticator user already enrolled	Try again or request support for more assistance.
107011	Fingerprint authenticator cannot render content	Try again or request support for more assistance.
107013	Fingerprint biometric removal not supported	Try again or request support for more assistance.
107010	Fingerprint authenticator not available	Navigate to device settings and make sure that Touch ID id registered. Restart the app and try to register/authenticate again.
10111	No camera permissions were granted required by Sensory Face Authenticator.	Navigate to device settings and make sure that app has permissions to use the camera. Restart the app and try again when permissions were granted.
10100	Parameters supplied were not valid for the specified operation	Try again or request support for more assistance.
102502	Parsing Licensing server response failed	Try again or request support for more assistance.
10112	Unable to successfully complete license setup	It looks like you are offline, so we couldn't complete the pairing process. Check that you are connected to the internet and try again.
102503	Parsing Licensing server response failed	Try again or request support for more assistance.
102501	Request to Licensing server failed	Try again or request support for more assistance.
107017	User is trying to register with PIN, but PIN authenticator user already enrolled	User should deregister before trying to register with this authenticator.
107018	PIN authenticator cannot render content.	1. Try to re-register and try again 2. Check logs for more details.
107020	Authentication Policy contains PIN Authenticator, but PIN authenticator is not enrolled for this user.	User should register PIN or policy should be modified to include only registered authenticators.
107021	PIN authenticator user data deletion error	1. User should try to de-register again. 2. If the problem is still happening then Admin need to collect logs and analyze it.
107022	PIN authenticator user not enrolled	User should register PIN or policy should be modified to include only registered authenticators.
1030010	Not enough permissions to enable QR scanner. User declined to grant camera permissions.	Navigate to device settings and make sure that app has permissions to use the camera. Restart the app and try again when permissions were granted.
10101	The registration operation failed	Try again or request support for more assistance.
102002	Parsing RP server response failed	Try again or request support for more assistance.
102003	Parsing RP server response failed	Try again or request support for more assistance.
102001	Request to the RP server failed	Try again or request support for more assistance.
10109	Unable to complete the remote device authentication (eg. push notification-based operation for web login or transaction)	We couldn't reach your device to unlock it. Check that it's turned on, and that you are connected to the internet, then try again.
10108	Unable to cancel the authorized unlock (eg. unlock windows machine)	It looks like you are offline, so we couldn't cancel the unlocking process. Check that you are connected to the internet and try again.
10102	Unable to register the remote device	Try again or request support for more assistance.
10110	Unable to complete the deregister of one or more remote devices	Check that you are connected to the internet and try again.
10104	Unable to register the remote device	Try again or request support for more assistance.
10105	Unable to register the remote device	Try again or request support for more assistance.
10107	Unable to unlock the remote device (eg. unlock windows machine)	It looks like you are offline, so we couldn't complete your login. Check that you are connected to the internet and try again.
10114	Unable to successfully complete reset app	It looks like you are offline, so we couldn't complete the pairing process. Check that you are connected to the internet and try again.
10113	Unable to successfully complete status request	It looks like you are offline, so we couldn't complete the pairing process. Check that you are connected to the internet and try again.
101004	FIDO Authentication get request failed	Try again or request support for more assistance.
101005	FIDO Invalid UAF authentication response received	Try again or request support for more assistance.
101006	FIDO Authentication send request failed	Try again or request support for more assistance.
101007	FIDO Deregistration get request failed	Try again or request support for more assistance.
101008	FIDO Invalid UAF deregistration response received	Try again or request support for more assistance.
101018	Remote Device OOB authentication failed	Something went wrong with your authentication method. Please try again.
101022	Remote Device Cancel unlock failed	Try again or request support for more assistance.
101017	Remote Device credentials not found during OOB authentication	Try again or request support for more assistance.
101012	Remote Device registration for existing user failed	Try again or request support for more assistance.
101009	Remote Device setup request failed	Try again or request support for more assistance.
101011	Remote Device registration for new user failed	Try again or request support for more assistance.
101010	Remote Device registration request failed	Try again or request support for more assistance.
101028	Failed to save Remote Device session during setup	Try again or request support for more assistance.
101021	Remote Device status update failed	Try again or request support for more assistance.
101013	Remote Device unlock authentication failed	Try again or request support for more assistance.
101015	Remote Device Authentication HMACs generation failed	Try again or request support for more assistance.
101016	Remote Device unlock failed	Try again or request support for more assistance.
101014	Remote Device unlock failed	Try again or request support for more assistance.
101031	Remote Device logged out during unlock request	Try again or request support for more assistance.
101032	Attempt to unlock already unlocked workstation	1. Try to unlock the account again. 2. Attempt to restart the computer and initiate the unlock again.
101019	No registered profiles found	Try again or request support for more assistance.
101001	FIDO Registration get request failed	Try again or request support for more assistance.
101002	FIDO Invalid UAF registration response received	Try again or request support for more assistance.
101003	FIDO Registration send request failed	Try again or request support for more assistance.
101033	You've reached the limit of paired web accounts.	Unpair an account you're not using and try again.
101036	The account on the current server already paired. Users can't re-pair the same account, de-registration is needed first.	Remove this account before trying to pair again. Ensure that you don't have this account paired on mobile app already.
101034	You've reached the limit of paired devices.	Unpair a computer you're not using and try again.
101037	The workstation on the current rp already paired	This computer is already paired with your HYPR app. You can unlock it from the home screen.
101035	Workstations limit reached	You've reached the limit of paired devices. Unpair a computer you're not using and try again.
1030001	Server API version higher than supported by the SDK	Update your mobile app and try again.
1030000	Server API version lower than supported by the SDK	Upgrade your server to use this Mobile SDK version.
107040	Voice authenticator user already enrolled. User is trying to regsiter with Voice, but it's already enrolled.	User should remove existing registration before trying to register with this authenticator again.
107043	Voice authenticator cannot render content.	Analyze SDK debugger logs and contact HYPR support for the assistance.
107042	Voice authenticator failed to de-register.	1. De-register Voice Authenticator and try again. 2. Analyze debugger logs for more details.
107045	Voice authenticator user enrollment failed.	User should try to perform the same action agan. Make sure that user is not backgrounding the app during the operation and don't press cancle button at anu point of the flow.
107047	Voice authenticator enrollment timeout. Usually, it happens when user didn't complete the enrollment process in 60 seconds.	User should try to register again in a quite place and ensure that registration done in 60 seconds or less.
107048	Voice authenticator user enrollment result unknown. Usually, it happens when user didn't authenticate on time or tried to authenticate with not registered voice.	1. User should try to authenticate with Voice again. 2. Re-register if the problem still occurs. 3. Analyze SDK debugger logs and contact HYPR support for the assistance.
107053	Voice authenticator user data migration to new version failed. Usually, it happens after HYPR SDK upgrade.	Analyze SDK debugger logs and contact HYPR support for the assistance.
107041	The user is trying to register with Voice Authenticator, but it's not registered. Usually, it happens when authentication policy contains Authenticator which wasn't registered or was removed by the user.	1. Register Voice Authenticator and try again. 2. Modify Authentication policy to only include registered authenticators
107049	Failed to authenticate the user with Voice. Usually, it happens when user didn't authenticate on time or tried to authenticate with not registered voice.	User should try to authenticate again in a quiet place and ensure that authentication done in 30 seconds or less.
107051	Voice authenticator verification timeout. Usually, it happens when user didn't authenticate on time or tried to authenticate with not registered voice.	User should try to authenticate again in a quiet place and ensure that authentication done in 30 seconds or less.
107052	Voice authenticator verification failed with unknown error.	1. User should try to authenticate again. 2. Admin should analyze SDK logs if the problem is still happening.
103000	Failed to match registration PIN. Usually, it happens when user scans incorrect or expired QR Code.	User should try again and ensure that correct QR code is scanned.
1010004	Failed to verify the public key for offline mode. Usually, it happens when authentication for the offline mode has failed.	User should try to authenticate again.
101038	The workstation on the current server already paired. Users can't re-pair the same computer, de-registration is needed first.	Remove this workstation before trying to pair again. Ensure that you don't have this computer paired on mobile app already.
101051	OOB Authentication cancelation failed.	1. User should try again in 3 minutes. 2. If the problem is still happening then Admin need to collect logs and analyze it.
101052	Device registration cancelation failed.	1. User should try again in 3 minutes. 2. If the problem is still happening then Admin need to collect logs and analyze it.
109006	Failed to consume offline tokens.	Reach the support.
109007	No offline tokens left.	Try regular unlock before next offline token attempt and if doesn't work reach the support.
109005	Failed to retrieve offline tokens.	Reach the support.
109004	Failed to store offline tokens.	Try regular unlock before next offline token attempt and if doesn't work reach the support.
109003	No signing certificated received from server.	Try regular unlock before next offline token attempt and if doesn't work reach the support.
109002	No offline tokens auth received from server.	Try regular unlock before next offline token attempt and if doesn't work reach the support.
109001	No offline tokens received from server.	Try regular unlock before next offline token attempt and if doesn't work reach the support.
109000	Generic offline tokens error.	Try regular unlock before next offline token attempt and if doesn't work reach the support.
101063	OOB mobile authentication failure request failed.	Failed to authenticate. User should try to authenticate again.
101062	If user has Domain machine registered for this user, the attempt to register VDI machine will fail.	Don't try to register VDI machine for the user with already registered Domain machine
101061	Unknown QR code type.	Reach the support.
1010011	Random AES iv generation failed during certificate-based login.	Reach the support.
101060	We couldn’t lock your computer. Please try again later or contact your Admin if this keeps happening.	Check if workstation has internet access - Try again or request support for more assistance - check feature flags are enabled.
101059	Pending OOB Authentication error.	In most of the cases - because there is no pending auth at the moment, either user didn't trigger it from the web or it is expired already.
101058	The session for this OOB Authentication request is handled already.	User should try to login trigger the login on the website one more time before trying to get the pending OOB Authentication request.
101057	Pending OOB Auth not supported for this machine type.	User should attempt to request pending OOB Authentication for web machines only.
101055	Push Notification Expired.	User should try to authenticate again.
101056	Remote Device lock failed.	Check if workstation has internet access - Try again or request support for more assistance
101052	Device registration cancelation failed.	1. User should try again in 3 minutes. 2. If the problem is still happening then Admin need to collect logs and analyze it.
109010	Failed to store discarded offline tokens	Try one more time and if doesn't work reach the support.
109011	Tokens Base64URL invalid format.	Try regular unlock before next offline token attempt and if doesn't work reach the support.
109012	Offline token field missing in user profile.	Try regular unlock before next offline token attempt and if doesn't work reach the support.
109013	FIDO auth payload error while accessing offline tokens.	Try regular unlock before next offline token attempt and if doesn't work reach the support.
109014	UAF client response error while accessing offline tokens.	Try regular unlock before next offline token attempt and if doesn't work reach the support.
109015	Authentication canceled while accessing offline tokens.	User canceled the authentication, no action needed.

Was this article helpful?

0 out of 0 found this helpful