1# Application Event Logging 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## 11100001 Application Event Logging Disabled
8
9**Error Message**
10
11Function disabled.
12
13**Description**
14
15- The **write** API is called to perform application event logging, but the system ignores related events because the logging function is disabled.
16- The **setEventParam** API is called to set custom event parameters, but the system ignores the calling because the logging function is disabled.
17
18**Possible Causes**
19
20The application event logging function is disabled.
21
22**Solution**
23
24Invoke the **configure** API to enable the application event logging function.
25
26   ```ts
27   import hiAppEvent from '@ohos.hiviewdfx.hiAppEvent';
28
29   hiAppEvent.configure({
30       disable: false
31   });
32   ```
33
34## 11101001 Invalid Event Domain Name
35**Error Message**
36
37Invalid event domain.
38
39**Description**
40
41- The **write** API is called to perform application event logging, but the system ignores related events because the input event domain name is invalid.
42- The **setEventParam** API is called to set custom event parameters, but the system ignores the calling because the input event domain name is invalid.
43
44**Possible Causes**
45
46The specified event domain name does not comply with the following rules:
47
48- The event domain name contains only digits, letters, and underscores (\_).
49- The event domain name starts with a letter and does not end with an underscore (\_).
50- The event domain name is not empty and contains a maximum of 32 characters.
51
52**Solution**
53
54Specify a valid event domain name.
55
56## 11101002 Invalid Event Name
57
58**Error Message**
59
60Invalid event name.
61
62**Description**
63
64- The **write** API is called to perform application event logging, but the system ignores related events because the input event name is invalid.
65- The **setEventParam** API is called to set custom event parameters, but the system ignores the calling because the input event name is invalid.
66
67**Possible Causes**
68
69The specified event name does not comply with the following rules:
70
71- The event name contains only the dollar sign ($), digits, letters, and underscores (_).
72- The event name must start with a letter or dollar sign ($) and end with a digit or letter.
73- The event name is not empty and contains a maximum of 48 characters.
74
75**Solution**
76
77Specify a valid event name.
78
79## 11101003 Invalid Number of Event Parameters
80
81**Error Message**
82
83Invalid number of event parameters.
84
85**Description**
86
87This error code is reported if the **write** API is called to perform application event logging but the system discards extra event parameters because the number of input event parameters exceeds the limit.
88
89**Possible Causes**
90
91The number of input event parameters exceeds 32.
92
93**Solution**
94
95Specify a valid number of event parameters.
96
97## 11101004 Invalid Event Parameter String Length
98
99**Error Message**
100
101Invalid string length of the event parameter.
102
103**Description**
104
105- The **write** API is called to perform application event logging, but the system ignores related event parameters because the value of the input event parameter is excessively long.
106- The **setEventParam** API is called to set custom event parameters, but the system ignores the calling because the input event parameter value is invalid.
107
108**Possible Causes**
109
110- The length of the string of the event parameter value passed by the **write** API exceeds 8 x 1024 characters.
111- The length of the custom event parameter value passed by the **setEventParam** API exceeds 1024 characters.
112
113**Solution**
114
115Specify an event parameter value with a valid length.
116
117## 11101005 Invalid Event Parameter Name
118
119**Error Message**
120
121Invalid event parameter name.
122
123**Description**
124
125- The **write** API is called to perform application event logging but the system ignores related event parameters because the input event parameter name is invalid.
126- The **setEventParam** API is called to set custom event parameters, but the system ignores the calling because the input event parameter name is invalid.
127
128**Possible Causes**
129
130The specified event parameter name does not comply with the following rules:
131
132- The event parameter name contains only the dollar sign ($), digits, letters, and underscores (_).
133- The event parameter name must start with a letter or dollar sign ($) and end with a digit or letter.
134- The event parameter name is not empty and contains a maximum of 32 characters.
135
136**Solution**
137
138Specify a valid event parameter name.
139
140## 11101006 Invalid Array Length of Event Parameter Values
141
142**Error Message**
143
144Invalid array length of the event parameter.
145
146**Description**
147
148This error code is reported if the **write** API is called to perform application event logging but the system discards extra array elements because the array of the event parameter value is excessively long.
149
150**Possible Causes**
151
152The array length of the event parameter value exceeds 100.
153
154**Solution**
155
156Specify a valid array length for the event parameter value.
157
158## 11101007 Invalid Number of Custom Event Parameters
159
160**Error Message**
161
162The number of parameter keys exceeds the limit.
163
164**Description**
165
166The **setEventParam** API is called to set custom event parameters, but the system ignores the calling because the number of event parameters is invalid.
167
168**Possible Causes**
169
170The number of custom event parameters passed exceeds 64.
171
172**Solution**
173
174Specify a valid number of custom event parameters.
175
176## 11102001 Invalid Watcher Name
177
178**Error Message**
179
180Invalid watcher name.
181
182**Description**
183
184This error code is reported if the **addWatcher** API is called to subscribe to application events but the system ignores the subscription because the specified watcher name is invalid.
185
186**Possible Causes**
187
188The specified watcher name does not comply with the following rules:
189
190- The watcher name can contain only digits, letters, and underscores (\_).
191- The watcher name starts with a letter and does not end with an underscore (\_).
192- The watcher name is not empty and contains a maximum of 32 characters.
193
194**Solution**
195
196Specify a valid watcher name.
197
198## 11102002 Invalid Filtering Event Domain Name
199
200**Error Message**
201
202Invalid filtering event domain.
203
204**Description**
205
206This error code is reported if the **addWatcher** API is called to subscribe to application events but the system ignores the subscription because the specified filtering event domain name is invalid.
207
208**Possible Causes**
209
210The specified filtering event domain name does not comply with the following rules:
211
212- The event domain name contains only digits, letters, and underscores (\_).
213- The event domain name starts with a letter and does not end with an underscore (\_).
214- The event domain name is not empty and contains a maximum of 32 characters.
215
216**Solution**
217
218Specify a valid filtering event domain name.
219
220## 11102003 Invalid Event Number
221
222**Error Message**
223
224Invalid row value.
225
226**Description**
227
228This error code is reported if the **addWatcher** API is called to subscribe to application events but the system ignores the subscription because an invalid event number is passed in the callback trigger condition.
229
230**Possible Causes**
231
232The event number passed in the input callback triggering condition is a negative number.
233
234**Solution**
235
236Specify a valid event number.
237
238## 11102004 Invalid Event Size
239
240**Error Message**
241
242Invalid size value.
243
244**Description**
245
246This error code is reported if the **addWatcher** API is called to subscribe to application events but the system ignores the subscription because an invalid event size is passed in the callback trigger condition.
247
248**Possible Causes**
249
250The event size passed in the input callback triggering condition is a negative number.
251
252**Solution**
253
254Specify a valid event size.
255
256## 11102005 Invalid Timeout Value
257
258**Error Message**
259
260Invalid timeout value.
261
262**Description**
263
264This error code is reported if the **addWatcher** API is called to subscribe to application events but the system ignores the subscription because an invalid timeout value is passed in the callback trigger condition.
265
266**Possible Causes**
267
268The timeout value passed in the input callback triggering condition is a negative number.
269
270**Solution**
271
272Specify a valid timeout value.
273
274## 11103001 Invalid Maximum Storage Quota
275
276**Error Message**
277
278Invalid max storage quota value.
279
280**Description**
281
282This error code is reported if the **configure** API is called to subscribe to application events but the system ignores the setting because the specified maximum storage quota is invalid.
283
284**Possible Causes**
285
286The maximum storage quota does not meet the following rules:
287
288- The quota value consists of only digits and a unit (including b|k|kb|m|mb|g|gb|t|tb, which are case-insensitive).
289- The quota value must start with a digit. You can determine whether to pass the unit. If the unit is left empty, **b** (that is, byte) is used by default.
290
291**Solution**
292
293Specify a valid maximum storage quota.
294
295## 11104001 Invalid Event Package Size
296
297**Error Message**
298
299Invalid size value.
300
301**Description**
302
303This error code is reported if the **setSize** API is called to set the threshold of the event package size but the system ignores the setting because the specified event package size is invalid.
304
305**Possible Causes**
306
307The specified event package size is a negative number.
308
309**Solution**
310
311Specify a valid event package size.
312