--- title: "Ultra Error Code List" slug: "ultra-error-code-list-1" updated: 2026-04-01T14:43:54Z published: 2026-04-01T14:43:54Z canonical: "support.kiosoft.com/ultra-error-code-list-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.kiosoft.com/llms.txt > Use this file to discover all available pages before exploring further. # Ultra Error Code List **This error code list applies to the Ultra series, including Ultra LX, Ultra VX, Ultra VQ-M, and Ultra VQ-FM.** ER21 Description: Sync parameter to reader failed Solution: First, perform a factory-reset on ULTRA using KLM. Then, locate the correct profile for the corresponding machine and reperform the setup. ER22 Description: NMS Update failed 1. During NMS operation, a failure occurred in parsing the configuration file, opening the file, or incorrect parameters. 2. During NMS operation, a failure occurred in uploading, opening, constructing the configuration file, etc. 3. During NMS operation, a failure occurred when attempting to download the remote profile file. Solution: Check network settings, retry NMS if needed. ER23 Description: Connect to NMS Server Failed Solution: Check network settings, retry NMS if needed. ER24 Description: Download Configure file from NMS Server failed Solution: Check network settings, retry NMS if needed. ER25 Description: Upload Configure file to NMS Server failed Solution: Check network settings, retry NMS if needed. ER26 Description: Upload saved log file to NMS Server failed Solution: Check network settings, retry NMS if needed. ER27 Description: Connect to TTI server fail Solution: Retry technician card. Confirm the network status. If the network is normal, use the correct technician card to swipe again with the ultra. ER28 Description: Read MSR card error Solution: Retry MSR magnetic swipe. ER29 Description: Verify CVC of MSR card error Solution: Retry MSR magnetic swipe. ER30 Description: Verify UVID of MSR card error Solution: Confirm whether the technician card being used is correct. Retry technician card. ER31 Description: The vendor ID of tech card error Solution: Confirm whether the technician card being used is correct. Retry technician card. ER32 Description: Inserting chip card on init mode will show this error. Not support chip card err Solution: try another technician card. ER33 Description: The swiped card is not tech card error Solution: Confirm whether the technician card being used is correct. Retry technician card. ER34 Description: The reader is unable to communicate with the machine. Solution: [ER34 Reasons and Solutions](/v1/docs/er34-reasons-and-solutions) ER35 Description: Communication error in the reader Solution: Try disconnecting the terminal from the power and then reconnecting it. ER36 Description: 1. Payment processor credentials are incorrect or not entered. 2. Reader doesn't have network and is not able to connect to payment processor. Solution: 1. Use the "Get Reader Info" command in KLM to check if the status is "connected" to verify that the reader has internet connection, or reboot and confirm NMS is successful. If not, troubleshoot network connectivity. 2. Verify VAR credentials are entered in correctly on ultra data or machine profiles. 3. Make new credentials if needed. 4. If the automated VAR function is adopted, it is necessary to confirm whether Washboard supports this function and ensure that it can correctly interact with Payroc to obtain the VAR credentials. ER37 Description: Laundry machine is busy now Solution: Check the status of the target machine. ER38 Description: Completion error Solution: Check network connectivity and verify that the correct master and back-up units for Ultra segment are running. ER39 Description: Completion get parameter failed Solution: Check network connectivity and verify that the correct master and back-up units for Ultra segment are running. ER40 Description: Completion set parameter failed Solution: Check network connectivity and verify that the correct master and back-up units for Ultra segment are running. ER41 Description: Completion set information failed Solution: Check network connectivity and verify that the correct master and back-up units for Ultra segment are running. ER42 Description: Completion failed Solution: Check network connectivity and verify that the correct master and back-up units for Ultra segment are running. ER43 Description: Completion get origin number failed Solution: Check network connectivity and verify that the correct master and back-up units for Ultra segment are running. ER44 Description: Completion get balance failed Solution: Check network connectivity and verify that the correct master and back-up units for Ultra segment are running. ER45 Description: Completion update balance failed Solution: Check network connectivity and verify that the correct master and back-up units for Ultra segment are running. ER46 Description: 1. Payment processor credentials are incorrect or not entered. 2. Reader doesn't have a network and is not able to connect to payment processor. Solution: 1. Use the "Get Reader Info" command on KLM to verify that the reader is programmed to the correct location ID and room number. 2. Use TMS present config to check if the VAR credentials are correct and match the other readers in the room. 3. Check the top-left corner of the reader display or use TMS present config to verify that there are only 1 Master and 1 Backup in the room. 4. After fixing, reboot the modem. 5. Check the router configuration. Is it configured in a DHCP mode? 6. Check if any other device in the router is using the master's ID address (192.168.8.2) ER47 Description: Payment error 2 Solution: Check network connectivity ER48 Description: Payment error 3 Solution: Check network connectivity ER49 Description: Payment error 4 Solution: Check network connectivity ER50 Description: Verify the mac value of message failed Solution: Check network connectivity and verify that the correct master and back-up units for Ultra segment are running. Validate that the Ultra is on the correct segment. ER51 Description: MSR Card - offline no connectivity error Solution: Check network connectivity. ER52 Description: offline, lost connectivity error (The reader has been in offline mode for three days and offline transactions are no longer permitted) Solution: Check network connectivity. Put the reader in online mode. ER53 Description: offline transaction not supported (The current terminal has entered the offline state, and the configuration of the current terminal does not support the offline mode) Solution: Check network connectivity. ER54 Description: offline transaction does not support chip card Solution: Check network connectivity. ER55 Description: Cycle Changed, Start machine failed Solution: The user cannot change cycle selection, start the transaction again with the proper cycle selection. ER56 Description: Pin Pad not running Solution: Retry setup, First, perform a factory-reset on ULTRA using KLM. Then, locate the correct profile for the corresponding machine and re-perform the setup. ER57 Description: Maytag machine response the Vend Price is 0. (A bug in the MAYTAG machine occurs when the phone repeatedly puts the MAYTAG machine into the service mode. In such cases, an abnormal situation arises: the obtained cycle price is 0.) Solution: Retry transaction. ER92 Description: WRONG SITE CODE (The site code in the value card does not match with the reader.) Solution: Check whether the site code configured by the profile and user's value card is consistent. If the profile is configured with the wrong site code, then factory reset the reader; the reader will need to be set up again. ER99 Description: BALANCE OVERFLOW (The balance of the user's value card is greater than $99.99.) Solution: It is necessary to keep the balance of this card below 99.99. OFFLINE NOT SUPPORTED FOR CONTACTLESS Description: Offline mode doesn't support contactless card Solution: Try an MSR card or chip card to do offline transactions or check the network status and make the reader online PLEASE CALL FOR SERVICE Description: Offline mode doesn't support chip card Solution: Try MSR card or call for service Batch Nearly Full Description: Reader saved 498 transaction records which don't complete successfully. Solution: Wait for daily settlement or do manual settlement Batch Full Description: Reader saved 500 transaction records which don't complete successfully, can't do new transaction Solution: Wait for daily settlement or do manual settlement UNRECOGNIZED READER Description: UNRECOGNIZED READER PROFILE CHANGE Description: Machine type change between redemption and no-redemption PAYMENT FAILED Description: MDB pay fail Solution: The user needs to reselect the goods and start a new round of the transaction process. DISPENSE FAILED Description: MDB deliver good failed (There has been an anomaly in the MDB Vending machine) Solution: Check whether the working status of the MDB vending machine is normal. TRANS TYPE/NOT SUPPORTED Description: This trans type is not supported. Solution: Use another trans type. Perform a factory-reset on ULTRA using KLM. Then, locate the correct profile (Check the corresponding transaction type) for the corresponding machine and re-perform the setup. PAYMENT TYPE/NOT SUPPORTED Description: This payment type is not supported. Solution: Use another payment type. Perform a factory-reset on ULTRA using KLM. Then, locate the correct profile (Check the corresponding transaction type) for the corresponding machine and re-perform the setup. ERROR/LAUNDRY PRICE/TOO HIGH Description: Laundry price is too big Solution: Retry a new flow or power down/up the machine READ CARD ERROR/TRY AGAIN Description: Read card failed Solution: Retry or use another card CARD NOT SUPPORT Description: API invalid card or payment method not supported Solution: Use another card WIRELESS NETWORK CONNECTION FAILED Solution: Replug the network cable INSUFFICIENT BALANCE Solution: Buy more balance DEX COLLECTION/FAILED Description: MDB DEX collection failed (DEX is the communication protocol of the MDB machine. This error indicates that communication with MDB has failed.) Solution: 1. Check whether the connection cable between the terminal and the MDB machine is functioning properly. 2. Check if the DEX switch of the MDB is turned on. DISPENSE/FAILED Description: MDB start failed Solution: Check the connection cables between the reader and MDB **Cloud based card errors** ANF Description: Account not found Solution: Bind the card to the account E001 Description: Get price failed Solution: 1. Check if the cloud card is bound to the account 2. Check if the account is registered E002 Description: Deduct money failed Solution: 1. Check if the cloud card is bound to the account 2. Check the third-party response log E007 Description: Network is unavailable Solution: Use KioSoft modem E008 Description: CJSON Parse (WB returns error text) (Explanation: A washboard interface that does not support this function was requested, and the data returned by the interface is not in JSON format.) Solution: Close cloud flare filter on OM or Confirm with the Wash board whether this function is supported. E010 Case 1: Use on KPOS Description: select cycle timeout 60s Solution: Rerun flow or power down/up the reader and machine Case 2: Reader power on Description: Get Random Key failed Solution: Restart the terminals in different times E012 Description: Reverse failed Solution: Check internet E013 Description: No KioSoft modem Solution: Use KioSoft modem E014 Description: No Modem Solution: Use KioSoft modem E015 Description: Account is disabled Solution: Go to server->Vendor Portal->Location Management to enable the account E016 Description: Other errors E017 Description: BALANCE IS NEGATIVE Solution: Add funds to the account E018 Description: INSUFFICIENT POINTS Solution: Not use points **KPOS Error Code** E001 Description: invalid employee card Solution: Re-tap or use another employee card or contact support E002 Description: employee not clocked in Solution: Re-tap or use another employee card or contact support E003 Description: invalid work order card Solution: Re-tap or use another order card or contact support E004 Description: work order not active Solution: Use another order card or contact support E005 Description: invalid employee card and work order card Solution: Re-tap or use another card or contact support E006 Solution: wait then tap employee card E007 Solution: wait then tap work order card E008 Solution: tap card ok, and then processing with KPOS server E009 Description: laundry machine in use Solution: Wait for a while E010 Description: select cycle timeout 60s Solution: Rerun flow or power down/up the reader and machine E011 Description: start laundry machine failed Solution: Check the cable between the reader and the machine or power down/up the reader and machine E012 Description: update work order status failed Solution: Check network connectivity E013 Description: update work order status succ E014 Description: get API session key failed Solution: Check network connectivity E015 Description: API create JSON object failed Solution: Check network connectivity E016 Description: API malloc fail Solution: Power down/up the reader E017 Description: API request failed Solution: Check network connectivity E018 Description: API response parse failed Solution: Check network connectivity E019 Description: server does not support KPOS API Solution: Contact support E020 Description: In the multi or incremental mode of the universal pulse machine, the user needs to select the cycle first before conducting the transaction; otherwise, an error will be displayed. Solution: please select the cycle first and then make the transaction E021 Description: network error Solution: Check network connectivity E022 multi work Description: The error returned by the server-side API is verified by the server itself. Means An order card associated with multiple orders. Solution: Employee card/Order card has a problem. The user needs to confirm whether these cards are still usable. E023 order completed Description: The error returned by the server-side API is verified by the server itself. Means Order completed. Solution: Employee card/Order card has a problem. The user needs to confirm whether these cards are still usable. E024 Description: missing param Solution: Check network connectivity or contact support E025 Description: KPOS server no response Solution: Check network connectivity E026 Description: decryption failed Solution: Perform a factory-reset on ULTRA using KLM. Then, locate the correct profile for the corresponding machine and re-perform the setup. In this way, the terminal can re-exchange the encryption and decryption keys with the server E027 Description: other error LEN ERR A3 Description: It means POS ID Error. The TSYS Host has already changed the response text; it will not respond “POS ID ERROR”. The TSYS App has already modified this logic on 2029/09/16. It uses the response code instead of using the response text. Solution: Change to another POS ID and re-activate the device. Incorrect merchant type Description: The MID associated with the merchant is not configured in Washboard. Solution: Log in to KioCentral, then go to: Settings → General Settings → Credentials for New Deployment (Automation) (Payroc). Ensure that the MID and Template ID are properly configured.