M-Tag: Error Codes & their description
Error codes displayed in Oloid app while using M-Tag
Error codes displayed in Oloid app while using M-Tag
Error
Error Description
Error occurs in
Resolution
E-01
When user doesn’t perform the required action & connection gets timeout
Foreground & Background mode
Before connection timeout, user can retry & perform the required action
E-04
Error occurs when there is missing configuration in portal for user/endpoint. For instance, Wiegand Format/Badge Binary/Secondary id issues.
Foreground & Background mode
User needs to contact the tenant admin. Admin can connect with Oloid Support
E-05
An unknown & an intermittent error observed mainly in Android devices
Foreground & Background mode
User needs to contact the tenant admin. Admin can connect with Oloid Support. Also, it is recommended to upload the logs using “Settings option” in “Profile” tab after receiving this error.
E-06
When M-Tag is not connected to the app, nearby available M-Tags become visible but are not close enough to perform the action/transaction. The connection gets timeout if not reached near the M-Tag to complete the transaction.
Foreground & Background mode
User can retry by performing the required action by reaching near the M-Tag. If the problem still persists, tenant admin can reach Oloid Support
E-07
When user tries to make a transaction within the duration of success delay.
Foreground & Background mode
Needs to wait till success delay to make a new transaction.
Bluetooth Credentials Unavailable
When Bluetooth credentials are not created/expired for the user.
Foreground & Background mode
User needs to contact the tenant admin for creating/extending the validity of Bluetooth credentials
Mobile keys are invalid. Please contact admin
When Bluetooth credentials expired while using the app. If app is killed & re-launched, error changes to “Bluetooth Credentials Unavailable”.
Foreground & Background mode
User needs to contact the tenant admin for creating/extending the validity of Bluetooth credentials
⌘I