1# SecureElement Error Codes 2 3> **NOTE** 4> 5> This topic describes only module-specific error codes. For details about universal error codes, see [Universal Error Codes](../errorcode-universal.md). 6 7## 3300101 Abnormal SE Service Status 8 9**Error Message** 10 11IllegalStateError, an attempt is made to use an SE session that has been closed. 12 13**Description** 14 15The SecureElement (SE) service is abnormal. 16 17**Possible Causes** 18 191. The SE service is disconnected. 20 21**Solution** 22 231. Close the SE service. 242. Set up a connection with the SE service again. 25 26## 3300102 No Such SE 27 28**Error Message** 29 30NoSuchElementError, the AID on the SE is not available or cannot be selected. 31 32**Description** 33 34The SE is unavailable. 35 36**Possible Causes** 37 381. Communication with the SE service is abnormal. 392. Communication of the SE chip is abnormal. 40 41**Solution** 42 431. Close the SE service and set up a connection with the SE service again. 442. Restart the device. 45 46## 3300103 Failed to Obtain the Access Rule 47 48**Error Message** 49 50SecurityError, the calling application cannot be granted access to this AID or the default applet on this session. 51 52**Description** 53 54The access rule cannot be obtained. 55 56**Possible Causes** 57 581. There is no access rule for the application on the SE. 59 60**Solution** 61 621. Write correct access rules to the SE. 632. Close the SE service and set up a connection with the SE service again. 64 65## 3300104 SE Chip I/O Exception 66 67**Error Message** 68 69IOError, there is a communication problem to the reader or the SE. 70 71**Description** 72 73The I/O of the SE chip is abnormal. 74 75**Possible Causes** 76 771. The communication with the SE chip is abnormal. 782. The SE chip is abnormal. 79 80**Solution** 81 821. Close the SE service and set up a connection with the SE service again. 832. Restart the device. 84