1# SE 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.
24
252. Set up a connection with the SE service again.
26
27## 3300102 No Such SE
28
29**Error Message**
30
31NoSuchElementError, the AID on the SE is not available or cannot be selected.
32
33**Description**
34
35The SE is unavailable.
36
37**Possible Causes**
38
391. Communication with the SE service is abnormal.
402. Communication of the SE chip is abnormal.
41
42**Solution**
43
441. Close the SE service and set up a connection with the SE service again.
452. Restart the device.
46
47## 3300103 Failed to Obtain the Access Rule
48
49**Error Message**
50
51SecurityError, the calling application cannot be granted access to this AID or the default applet on this session.
52
53**Description**
54
55The access rule cannot be obtained.
56
57**Possible Causes**
58
591. There is no access rule for the application on the SE.
60
61**Solution**
62
631. Write correct access rules to the SE.
642. Close the SE service and set up a connection with the SE service again.
65
66## 3300104 SE Chip I/O Exception
67
68**Error Message**
69
70IOError, there is a communication problem to the reader or the SE.
71
72**Description**
73
74The I/O of the SE chip is abnormal.
75
76**Possible Causes**
77
781. The communication with the SE chip is abnormal.
792. The SE chip is abnormal.
80
81**Solution**
82
831. Close the SE service and set up a connection with the SE service again.
84
852. Restart the device.
86