1# Distributed Scheduler 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## 16600001 The system ability works abnormally.
8
9**Error Message**
10
11The system ability works abnormally.
12
13**Description**
14
15This error code is reported when the system ability is abnormal.
16
17**Possible Causes**
18
19The possible causes are as follows:
201. The DMS service is not started.
212. The **binder** object of DMS is not obtained.
223. Other services on which ability continuation depends are not started or the **binder** object is not obtained.
23
24**Solution**
25
26Try again later or restart the device.
27
28## 16600002 The specified token or callback is not registered.
29
30**Error Message**
31
32The specified token or callback is not registered.
33
34**Description**
35
36This error code is reported if the token or callback used in an API of **continuationManager** is not registered when the API is called.
37
38**Possible Causes**
39
40The specified token or callback is not registered.
41
42**Solution**
43
44Register the token or callback before calling the API.
45
46## 16600003 The number of token registration times has reached the upper limit.
47
48**Error Message**
49
50The number of token registration times has reached the upper limit.
51
52**Description**
53
54This error code is reported when the number of times that the **continuationManager.registerContinuation** API is called has reached the upper limit.
55
56**Possible Causes**
57
58The number of token registration times has reached the upper limit.
59
60**Solution**
61
62Use a registered token. Do not register the token too frequently.
63
64## 16600004 The specified callback has been registered.
65
66**Error Message**
67
68The specified callback has been registered.
69
70**Description**
71
72This error code is reported when the **continuationManager.on** API is called with a callback the same as a previous one.
73
74**Possible Causes**
75
76The same callback is used for repeated registration.
77
78**Solution**
79
80Use a different callback for registration.
81
82## 16300501 The system ability works abnormally.
83
84**Error Message**
85
86The system ability works abnormally.
87
88**Description**
89
90This error code is reported when the system ability is abnormal.
91
92**Possible Causes**
93
94The possible causes are as follows:
951. The DMS service is not started.
962. The **binder** object of DMS is not obtained.
973. Other services on which ability continuation depends are not started or the **binder** object is not obtained.
98
99**Solution**
100
101Try again later or restart the device.
102
103## 16300502 Failed to get the missionInfo of the specified missionId.
104
105**Error Message**
106
107Failed to get the missionInfo of the specified missionId.
108
109**Description**
110
111This error code is reported when calling the **distributedMissionManager.continueMission** API fails.
112
113**Possible Causes**
114
115The possible causes are as follows:
1161. An incorrect mission ID is passed in.
1172. The mission information corresponding to the mission ID does not exist.
118
119**Solution**
120
121Verify the mission ID.
122
123## 16300503 The application is not installed on the remote end and installation-free is not supported.
124
125**Error Message**
126
127The application is not installed on the remote end and installation-free is not supported.
128
129**Description**
130
131This error code is reported if the application is not installed on the remote end and the installation-free feature is not supported when the **distributedMissionManager.continueMission** API is called.
132
133**Possible Causes**
134
135The application to continue is not installed on the remote end, and the installation-free feature is not supported.
136
137**Solution**
138
1391. Check whether the application has been installed on the remote end.
1402. Check whether the remote end supports installation-free.
141
142## 16300504 The application is not installed on the remote end and installation-free is supported. Try again with the freeInstall flag.
143
144**Error Message**
145
146The application is not installed on the remote end and installation-free is supported. Try again with the freeInstall flag.
147
148**Description**
149
150This error code is reported if the application is not installed on the remote end and installation-free is supported when the **distributedMissionManager.continueMission** API is called.
151
152**Possible Causes**
153
154The application to continue is not installed on the remote end, and installation-free is supported. However, the **freeInstall** flag is not carried.
155
156**Solution**
157
158Try again with the **freeInstall** flag.
159
160## 16300505 The operation device must be the device where the application to be continued is currently located or the target device.
161
162**Error Message**
163
164The operation device must be the device where the application to be continued is currently located or the target device.
165
166**Description**
167
168This error code is reported if the operation device is not the device where the application to be continued is currently located (source device) or the target device when the **distributedMissionManager.continueMission** API is called.
169
170**Possible Causes**
171
172The operation device is not the source or target device.
173
174**Solution**
175
176Use the source or target device for the operation.
177
178## 16300506 The local continuation task is already in progress.
179
180**Error Message**
181
182The local continuation task is already in progress.
183
184**Description**
185
186This error code is reported if the local continuation task is in progress when the **distributedMissionManager.continueMission** API is called.
187
188**Possible Causes**
189
190The continuation task has been initiated and is not complete yet.
191
192**Solution**
193
194Wait until the continuation task is complete.
195
196## 16300507 Failed to get the missionInfo of the specified bundleName.
197
198**Error Message**
199
200Failed to get the missionInfo of the specified bundle name.
201
202**Description**
203
204This error code is reported when calling the **distributedMissionManager.continueMission** API with **bundleName** specified fails.
205
206**Possible Causes**
207
208The possible causes are as follows:
2091. An incorrect bundle name is passed in.
2102. The mission information corresponding to the bundle name does not exist.
211
212**Solution**
213
214Verify the bundle name.
215
216## 3 Failed to flatten the object.
217
218**Error Message**
219
220Failed to flatten the object.
221
222**Description**
223
224This error code is reported if the system parameter **DMS_PROXY_INTERFACE_TOKEN** fails flattening when an API of **continuationManager** is called.
225
226**Possible Causes**
227
228The system parameter **DMS_PROXY_INTERFACE_TOKEN** fails to be written in serialization.
229
230**Solution**
231
232Make sure the system functions properly. Restart the system when needed.
233
234## 7 The object is null.
235
236**Error Message**
237
238The object is null.
239
240**Description**
241
242This error code is reported if DMS and other objects are empty or reading in serialization fails when an API of **continuationManager** is called.
243
244**Possible Causes**
245
246The possible causes are as follows:
2471. Reading the input parameters in serialization fails.
2482. The DMS service is not started or the **binder** object is not obtained.
2493. Other services on which DMS depends are not started or the **binder** object is not obtained.
250
251**Solution**
252
2531. Check whether the input parameters are valid.
2542. Check whether the DMS service is started normally. Restart the service or device when needed.
2553. Check whether other services on which DMS depends are started normally. Restart the services or device when needed.
256
257## 29360207 The number of registrations has reached the upper limit.
258
259**Error Message**
260
261The number of registrations has reached the upper limit.
262
263**Description**
264
265This error code is reported when the number of times that the **continuationManager.register** API is called exceeds the upper limit.
266
267**Possible Causes**
268
269The number of device registration times has reached the upper limit.
270
271**Solution**
272
273Restart the service and avoid frequent registration.
274
275## 29360208 The token is not registered.
276
277**Error Message**
278
279The token is not registered.
280
281**Description**
282
283This error code is reported when an API of **continuationManager** is called with an unregistered token.
284
285**Possible Causes**
286
287The token is not registered.
288
289**Solution**
290
291Register a token and use it in the API.
292
293## 29360209 The callback has been registered.
294
295**Error Message**
296
297The callback has been registered.
298
299**Description**
300
301This error code is reported when the **continuationManager.on** API is called with a callback the same as a previous one.
302
303**Possible Causes**
304
305The specified callback has been registered.
306
307**Solution**
308
309Do not use the same callback for repeated registration.
310
311## 29360210 The callback is not registered.
312
313**Error Message**
314
315The callback is not registered.
316
317**Description**
318
319This error code is reported when the **off**, **updateConnectStatus**, or **startDeviceManager** API of **continuationManager** is called with a callback that has been not registered by calling **on**.
320
321**Possible Causes**
322
323The specified callback is not registered.
324
325**Solution**
326
327Register a callback and use it in the API.
328
329## 29360211 Failed to connect to the ability.
330
331**Error Message**
332
333Failed to connect to the ability.
334
335**Description**
336
337This error code is reported if connection to the specified ability fails when the **startDeviceManager** API of **continuationManager** is called.
338
339**Possible Causes**
340
341The specified token is invalid or the target ability is not working properly.
342
343**Solution**
344
345Check whether the token is valid and whether the corresponding ability is normal. Restart the service or device when needed.
346
347## 29360214 The type of callback is not supported.
348
349**Error Message**
350
351The type of callback is not supported.
352
353**Description**
354
355This error code is reported when the **callback** parameter in the **on** or **off** API of **continuationManager** is set to an incorrect type.
356
357**Possible Causes**
358
359The callback type is not supported.
360
361**Solution**
362
363Pass a supported type for the **callback** parameter.
364
365## 29360215 Invalid connection state.
366
367**Error Message**
368
369Invalid connection state.
370
371**Description**
372
373This error code is reported when the **status** parameter in the **updateConnectStatus** API of **continuationManager** is invalid.
374
375**Possible Causes**
376
377The **status** parameter is invalid.
378
379**Solution**
380
381Use a valid value for the **status** parameter.
382
383## 29360216 Invalid continuation mode.
384
385**Error Message**
386
387Invalid continuation mode.
388
389**Description**
390
391This error code is reported when the **ContinuationExtraParams.continuationMode** parameter in the **register** or **startDeviceManager** API of **continuationManager** is invalid.
392
393**Possible Causes**
394
395The **ContinuationExtraParams.continuationMode** parameter is invalid.
396
397**Solution**
398
399Use a valid value for the **ContinuationExtraParams.continuationMode** parameter.
400