Wiki source code of Codes d'erreurs

Last modified by jhurst on 2021/04/21 10:01
Show last authors
1 = DigDash Enterprise error codes =
2
3 This document references the error codes generated by DigDash Enterprise. These errors are displayed in the DigDash Enterprise interface or appear in the log file (accessible from the **Configuration / Server status page** ).
4
5 {{ddtoc/}}
6
7 = Connection errors =
8
9 * **ERR-DD-LOG001**  : Authentication failed
10
11 ~=> Check the user name and password entered for the connection.
12
13 * **ERR-DD-LOG002 ** : User is not logged in
14
15 ~=> Refresh the page displayed to connect again
16
17 * **ERR-DD-LOG003 ** : The server does not accept any logon for the moment.
18
19 ~=> User authentication has been disabled (for example, allows maintenance of the DigDash server). Activation / deactivation of user authentication is done from the **Configuration / Server status ** page ( **Activation of authentication** button in the **Sessions** section )
20
21 * **ERR-DD-LOG004 ** : The maximum number of active sessions has been reached.(((
22 ~=> The maximum number of active licenses authorized by your license has been reached. See the **Configuration / License management ** page for more information on the number of available sessions. You can also view and delete active sessions from the **Configuration / Server status page** (click **List** in the **Sessions** section )
23 )))
24 * **ERR-DD-LOG005**  : The maximum number of active sessions for this user has been reached
25
26 ~=> The maximum number of active licenses authorized by your license for this user has been reached. See the **Configuration / License Management ** page for more information. You can also view and delete active sessions from the **Configuration / Server status page** (click **List** in the **Sessions** section )
27
28 * **ERR-DD-LOG006 ** : The user password must be changed.(((
29 ~=> This error appears only when the user tries to connect to an administration page, and his password has expired. This error does not appear if the user connects to the dashboard, instead a mandatory password change interface will be offered.
30 )))
31 * **ERR-DD-LDP001**  : Connection to the LDAP server failed
32
33 ~=> Check that the LDAP server is started and functioning properly.
34
35 * **ERR-DD-ACL001**  : Authorization (s) refused. The following authorization (s) are missing: "Authorization name"
36
37 ~=> Open the **Configuration / user management ** page to check and modify, if desired, the permissions available to the user
38
39 = Server errors =
40
41 * **ERR_DD_CFG001** : System configuration error
42
43 ~=> Check and test your system configuration from the **Configuration / Server settings** page . Check the log file for more information (accessible from the **Configuration / Server status page** ).
44
45 * **ERR-DD-ERR003**  : Server error. Please contact the administrator
46
47 ~=> Check the errors generated by the server in the log file (accessible from the **Configuration / Server status page** )
48
49 * **ERR-DD-PRG001 ** **: ** Server did not return status
50
51 ~=> Check that your server is started and responds correctly. If necessary, restart the server. Also check if errors have been generated in the log file (accessible from the **Configuration / Server status page** )
52
53 * **ERR-DD-API001**  : The server returned an empty response(((
54 ~=> Check that your server is started and responds correctly. If necessary, restart the server. Also check if errors have been generated in the log file (accessible from the **Configuration / Server status page** )
55 )))
56 * **ERR-DD-API002**  : The server did not respond quickly enough(((
57 ~=> Check that your server is started and responds correctly. If necessary, restart the server
58 )))
59 * **ERR-DD-API003**  : Invalid return type. The "Method name" method did not return the expected data type(((
60 ~=> System error. Contact your administrator and / or DigDash support if this error occurs. You will most certainly be asked for a complete log relating to the error, for analysis of the problem (accessible from the **Configuration / Server status page** )
61 )))
62 * **ERR-DD-CMS001 ** : The CMS plugin was not loaded: "Name of the plugin"(((
63 ~=> System error. Contact your administrator and / or DigDash support if this error occurs. You will most certainly be asked for a complete log relating to the error, for analysis of the problem (accessible from the **Configuration / Server status page** ).
64 )))
65 * **ERR-DD-CMS002**  : The CMS server is invalid: "Server name"
66
67 ~=> Test the server used from the **Configuration / Document management** page . If necessary, modify the parameters entered (name, password, etc.).
68
69 * **ERR-DD-CMS003**  : The file was not retrieved from the CMS: "File name"
70
71 ~=> Check that the file is present in the document server used and that the server is accessible.
72
73 * **ERR-DD-CMS004**  : Access to the CMS server is not authenticated: "Server name"(((
74 ~=> Test the server used from the **Configuration / Document management** page . In particular, check the authentication used to access the server.
75 )))
76 * **ERR-DD-CMS005**  : The file was not sent to the CMS: "File name"
77
78 ~=> Check the status of the server used from the **Configuration / Document management** page . If necessary, modify the information entered (name, password, etc.). Also verify that you have write permissions on the server.
79
80 * **ERR-DD-CMS006**  : The file has not been deleted from the CMS: "Server name"(((
81 ~=> Check the status of the server used from the **Configuration / Document management** page . If necessary, modify the parameters entered (name, password, etc.). Also verify that you have write permissions on the server.
82 )))
83 * **ERR-DD-CMS007**  : Access to the CMS server is prohibited: "Server name"
84
85 ~=> Check your access rights to the indicated server
86
87 * **ERR-DD-SMS001**  : The sending of the SMS failed
88
89 ~=> Check the configuration of the SMS service from the page on the **Configuration / Server settings** page
90
91 = Dictionary access errors =
92
93 These errors concern the metadata dictionaries used by DigDash Enterprise: translation dictionaries, formats, colors, javascript functions, ... accessible from the Tools menu in the administration console.
94
95 * **ERR-DD-REP001**  : Unable to open the dictionary: "Dictionary name"
96
97 ~=> The XML corresponding to the dictionary may be corrupted. Open the XML in a browser to check its validity. Check the log file for more information (accessible from the **Configuration / Server status page** )
98
99 * **ERR-DD-REP002**  : Invalid entry in the dictionary: "Entry name"
100
101 ~=> Check and modify the entry indicated (may contain an invalid character or use an identifier already used, ...)
102
103 * **ERR-DD-REP003**  : No valid entry in the dictionary: "Dictionary name"(((
104 ~=> System error. Contact your administrator and / or DigDash support if this error occurs. You will most certainly be asked for a complete log relating to the error, for analysis of the problem (accessible from the **Configuration / Server status page** )
105 )))
106 * **ERR-DD-REP004**  : Unable to save the dictionary: "Dictionary name"
107
108 ~=> Check that the DigDash server is still active. Also check that the storage space is not full and that the dictionary backup is performed by a user with write rights on the server.
109
110 * **ERR-DD-REP005**  : Unable to update the dictionary: "Dictionary name"(((
111 ~=> Check that the DigDash server is still active. Also check that the storage space is not full and that the dictionary backup is performed by a user with write rights on the server.
112 )))
113 * **ERR-DD-REP006 ** : Unable to update the dictionary: "Dictionary name", the element is out of sync
114
115 ~=> You are trying to update an item that has been modified by another user while you are editing it. The element is therefore no longer up to date compared to the version on the server. You must recover the version appearing on the server before making your updates.
116
117 * **ERR-DD-REP007**  : Unable to update the dictionary: "Name of the element", the name already exists
118
119 ~=> The element added in the dictionary uses a name already used. You must use unique names for each item in the dictionary.
120
121 = Plugin errors =
122
123 * **WNG-DD-DFL001**  : No plugin found for the data source: "Source name"(((
124 ~=> System error. Contact your administrator and / or DigDash support if this error occurs. You will most certainly be asked for a complete log relating to the error, for analysis of the problem (accessible from the **Configuration / Server status page** )
125 )))
126 * **WNG-DD-DFL002**  : No plugin found for the transformation: "Name of the transformation"(((
127 ~=> System error. Contact your administrator and / or DigDash support if this error occurs. You will most certainly be asked for a complete log relating to the error, for analysis of the problem (accessible from the **Configuration / Server status page** )
128 )))
129 * **WNG-DD-DFL003**  : No output plugin for the stream: "Stream name"(((
130 ~=> System error. Contact your administrator and / or DigDash support if this error occurs. You will most certainly be asked for a complete log relating to the error, for analysis of the problem (accessible from the **Configuration / Server status page** )
131 )))
132
133 = Errors in the portfolio and information flows =
134
135 * **ERR-DD-WAL001** : Invalid **wallet **
136
137 ~=> Check the log for more information (accessible from the **Configuration / Server status page** )
138
139 * **ERR-DD-WAL002**  : Invalid portfolio item identifier
140
141 ~=> The element indicated does not exist in the information portfolio or this element is new and the session of the user requesting it does not yet know it. In this case, log out and log back in to update the user's wallet.
142
143 * **ERR-DD-WAL003**  : Error loading stream history: "Stream name"
144
145 ~=> Check if the flow still exists and if the flow history contains elements. Refresh the flow history to update it.
146
147 * **ERR-DD-WAL004**  : The stream was not found
148
149 ~=> The indicated flow no longer exists in the information portfolio or this flow is new and the session of the user requesting it does not yet know it. In this case, log out and log back in to update the user's wallet.
150
151 * **ERR-DD-WAL005 ** : Loading of the information portfolio failed
152
153 ~=> The **.iwt** file corresponding to the portfolio concerned cannot be loaded. Verify that the server is started and responds correctly. If this is the case, check if errors are recorded in the log file (accessible from the **Configuration / Server status page** )
154
155 * **ERR-DD-WAL006**  : The stream history element was not found(((
156 ~=> This error occurs if there is no history entry for the flow (for example if the refresh of the cube failed or if it is a flow containing user-specific data and not been refreshed for the logged in user). Refresh the flow history to check if it is updated correctly.
157 )))
158 * **ERR-DD-ADM004**  : Error flow
159
160 ~=> status of the information portfolio when at least one flow in it contains an error. Unfold the information portfolio to obtain more information on the flow (s) concerned.
161
162 * **ERR-DD-CUB001**  : The cube does not exist
163
164 ~=> When viewing flow, the cube was not found. Refresh the cube to verify that the generation of this cube goes smoothly.
165
166 * **ERR-DD-CUB002**  : The generation of the cube failed. The cube generation failed due to an invalid source file.
167
168 ~=> Edit the data source to update the source file used by it (the file may no longer exist in the document server or the document server is not accessible)
169
170 * **ERR-DD-CUB003**  : The writing of the result cube failed. Unable to write the result cube.(((
171 ~=> Check the disk space on the DigDash Enterprise server and the write rights of the Tomcat process. The process must be able to write to the DigDash data cubes folder (see system configuration documentation).
172 )))
173 * **ERR-DD-CUB004 ** : the transformation data source failed. Cannot write result cube during data source transformation.(((
174 ~=> Check the indicated cause of the cube generation failure
175 )))
176 * **ERR-DD-CUB005 ** : The generation of the cube failed. Cause: "cause
177
178 ~=> Check the indicated cause of the cube generation failure
179
180 * **ERR-DD-MOD001 ** : Data model not found or invalid. The data source does not exist or is misconfigured.
181
182 ~=> The information flow does not reference any data source or references an absent or invalid data source. Edit the information flow to change the data source used.
183
184 * **ERR-DD-MOD002**  : **Render** model not found or invalid. The display configuration is missing or incorrect.(((
185 ~=> Edit the information flow to modify its visualization
186 )))
187 * **ERR-DD-MOD003**  : Invalid text entry
188
189 ~=> The error occurs during the video generation of the streams: check the video generation **parameters from the Visualization / audio and video configuration parameters** dialog box .
190
191 * **ERR-DD-MOD004**  : No navigation model
192
193 ~=> Error appearing in the display of text type graphs when the configuration is incorrect: check the configuration of text generation (from **Configuration of visualization / Advanced parameters / Configuration of text generation** )
194
195 * **ERR-DD-MOD005**  : The structure of the data source has changed. Changes have been detected in the structure of the data source. Please check the configuration of the data model.
196
197 ~=> Edit the data source to check the changes detected (the error tells you the list of columns found in place of those initially existing)
198
199 * **ERR-DD-MOD006**  : The condition is not fulfilled for the flow "Name of the flow" on the device "Name of the device".
200
201 ~=> This message is displayed if you use conditional synchronization. The condition to be fulfilled for the stream to be synchronized on the device is not fulfilled. For more information, edit your information flow and check the condition used in the **Devices ** tab (click on the toothed wheel to display the condition).** **
202
203 * **ERR-DD-INT001**  : User interrupt
204
205 ~=> This error is displayed if the user voluntarily interrupts a task (updating flows for example). Run the task again to clear the error.
206
207 * **ERR-DD-OUT001 ** : Type of output type not supported
208
209 ~=> Some graphics cannot use all the export formats (PDF, PPT, HTML, Image, ...). Use a different format for exporting your graph.
210
211 * **ERR-DD-EXP001**  : Unable to export the stream. An error occurred during the export of the flow: "Name of the flow" in "Type of export"
212
213 ~=> Check if an error is generated during the export: type F12 in your browser to display the error console. Also check the generated log (accessible from the "  **Configuration / Server status**  " page).
214
215 * **ERR-DD-SYN001**  : Synchronization error
216
217 ~=> check the logs for more information on the error (accessible from the **Configuration / Server status page** ).
218
219 * **ERR-DD-SVG001 ** : SVG interpretation error
220
221 ~=> Error generating video stream. Check the logs for more information (accessible from the **Configuration / Server status page** ).
222
223 * **ERR-DD-SVG002**  : SVGTranscodingError
224
225 ~=> Error generating video stream. Check the logs for more information (accessible from the **Configuration / Server status page** ).
226
227 * **ERR-DD-PLG001**  : Plugin execution error. The plugin failed: "Name of the plugin"(((
228 ~=> System error. Contact your administrator and / or DigDash support if this error occurs. You will most certainly be asked for a complete log relating to the error, for analysis of the problem (accessible from the **Configuration / Server status page** ).
229 )))
230 * **ERR-DD-PLG002 ** : Unable to clone the plugin: "Plugin name"(((
231 ~=> System error. Contact your administrator and / or DigDash support if this error occurs. You will most certainly be asked for a complete log relating to the error, for analysis of the problem (accessible from the **Configuration / Server status page** ).
232 )))
233 * **ERR-DD-PLG003**  : The creation of the plugin failed: "Name of the plugin"(((
234 ~=> System error. Contact your administrator and / or DigDash support if this error occurs. You will most certainly be asked for a complete log relating to the error, for analysis of the problem (accessible from the **Configuration / Server status page** ).
235 )))
236 * **ERR-DD-PLG004 ** ; Plugin authentication error. The plugin needs authentication: "Name of the plugin"(((
237 ~=> System error. Contact your administrator and / or DigDash support if this error occurs. You will most certainly be asked for a complete log relating to the error, for analysis of the problem (accessible from the **Configuration / Server status page** ).
238 )))
239 * **ERR-DD-PLG005**  : Class of plugin not found: "Name of plugin"(((
240 ~=> System error. Contact your administrator and / or DigDash support if this error occurs. You will most certainly be asked for a complete log relating to the error, for analysis of the problem (accessible from the **Configuration / Server status page** ).
241 )))
242 * **ERR-DD-TDS001**  : Loading of the data source failed. Loading table data source failed: "Data source name"
243
244 ~=> Check that the data source used is accessible (the document server used must be accessible and the data source must appear on the server)
245
246 * **ERR-DD-TDS002**  : The data source is not recognized. The array data source was not recognized: "Name of the data source"
247
248 ~=> The type of data source used is not recognized by DigDash. Check the data source (invalid file name extension, ...)
249
250 * **ERR-DD-TDS003**  : Download of data source failed: "Name of data source"
251
252 ~=> Check the data source used by the information flow (the file used may no longer appear in the document server or the document server used may not be accessible)
253
254 * **ERR-DD-TDS004**  : Transformation of the data source failed. The table data source has not been transformed: "Name of the data source"
255 * => transformation of Excel crosstab into flat table failed. Check the parameters used for this transformation (from the advanced options of the Excel data source configuration)
256 * **ERR-DD-TDS005**  : The data source union / join **failed** . The data source union / join failed when unioning the child data sources.
257
258 ~=> check the log file for more information ((accessible from the **Configuration / Server status page** )
259
260 * **ERR-DD-ENG001**  : Unable to execute the flow: An error occurred while executing the flow.
261
262 ~=> Check in the log file (accessible from the **Configuration / Server status** menu ) if errors have been generated.
263
264 * **ERR-DD-ENG002**  : Unable to execute the flow "Name of the flow": The server did not return any results.
265
266 ~=> Check in the log file (accessible from the **Configuration / Server status** menu ) if errors have been generated.
267
268 * **ERR-DD-ENG003**  : Unable to execute the flow "Name of the flow": The flow is disabled.
269
270 ~=> Activate the feed by checking the box to the left of the feed name
271
272 * **ERR-DD-SQL001**  : Query on SQL database failed
273
274 ~=> check the syntax of your SQL query.
275
276 ~=> OR check the execution time allocated for the request ("timeout") in the advanced parameters of the data source (this may not be sufficient for the execution of your request).
277
278 * **ERR-DD-SQL002**  : Connection to SQL database failed(((
279 ~=> test the connection used and modify it if necessary (the connections are visible from the **Tools \ Database Connection Manager** menu or from the query edition)
280 )))
281 * **ERR-DD-OLP001**  : The query on the OLAP database failed
282
283 ~=> Check the syntax of your OLAP request.
284
285 ~=> OR check the execution time allocated for the request ("timeout") in the advanced parameters of the data source (this may not be sufficient for the execution of your request)
286
287 * **ERR-DD-OLP002**  : Connection to the OLAP database failed(((
288 ~=> Test the connection used and modify it if necessary (the connections are visible from the **Tools** menu **\ database connection manager** or from the query edition)
289 )))
290 * **ERR-DD-MDX001**  : MDX does not authorize several uses of the hierarchy "Name of the hierarchy" on the dimension "Name of the dimension". Please use the corresponding dimension attributes.
291
292 ~=> Modify the MDX used to comply with the MDX standard
293
294 * **ERR-DD-DEV001**  : Device not found: "device name"(((
295 ~=> Check the list of configured devices from the **Tools \ Device management ** menu in the administration console
296 )))
297
298 = Admin console errors =
299
300 * **ERR-DD-ADM001**  : Documentation is not available.
301
302 ~=> Copy the documentation to the installation directory of DigDash Enterprise (named below <install_dd>).
303
304 To do this, open the DigDash installation file (install_dd_version.zip) then extract the **documentation** directory to **<install_dd> / documentation** .
305
306 Similarly, extract the **apache-tomcat / webapps / root / documentation directory ** in the zip to the **<install_dd> / apache-tomcat / webapps / root / documentation directory**
307
308 * **ERR-DD-ADM002**  : Unable to launch the system browser.(((
309 ~=> Check the browser selected for displaying flows in the administrative console (from the **Tools \ Options ** menu in the administrative console). Favor the use of Chromium if possible.
310 )))
311
312 Using the Firefox browser requires the installation of XulRunner (installation possible from the **Tools \ Options** menu )
313
314 * **ERR-DD-ADM003**  : Problem while launching the media player.(((
315 ~=> Check the browser selected for displaying feeds in the administrative console (from the **Tools \ Options ** menu in the administrative console). Favor the use of Chromium if possible.
316 )))
317
318 Using the Firefox browser requires the installation of XulRunner (installation possible from the **Tools \ Options** menu )
319
320 = Errors when creating derived measures =
321
322 * **ERR-DD-BID001** : This name already exists, please enter a different one.(((
323 ~=> Each measurement must have a different name in the data model. Change the name entered in **the Measure name** field
324 )))
325 * **ERR-DD-BID002** : The name of the measurement must not be empty.
326
327 ~=> Enter a name in **the Measure name** field
328
329 * **ERR-DD-BID003** : The variable must not be empty.(((
330 ~=> Enter a name for your variable
331 )))
332 * **ERR-DD-FPY001** : The formula field is empty.(((
333 ~=> Enter a formula for your variable.
334 )))
335 * **ERR-DD-VAR001** : The format of "number" is incorrect. Please check the value entered(((
336 ~=> For example the. (not the comma) must be used as a decimal separator.
337 )))
338 * **ERR-DD-VAR002** : The minimum and maximum values ​​are incorrect (the minimum must be less than the maximum).(((
339 ~=> Modify the minimum and / or maximum values.
340 )))
341 * **ERR-DD-VAR003** : The default value must be between the minimum and the maximum.
342
343 ~=> In the case of calculated variables, check that the default value is between the minimum and maximum values ​​entered.
344
345 * **ERR-DD-VAR004** : The default value must be defined in the list of values.
346
347 ~=> In the case of explicit variables, the default value must be part of the list of possible values ​​entered manually.
348
349 * **ERR-DD-VAR005** : The name field is empty.
350
351 ~=> In the case of explicit variables, enter a name for each of the values ​​entered. .
352
353 * **ERR-DD-VAR006** : The increment value must be different from 0.
354
355 ~=> In the case of calculated variables, enter an increment value other than 0.
356
357 * **ERR-DD-JSE001** : Problem during the evaluation of the JS code:. "JS" .. (arguments: "list of arguments")
358
359 ~=> Modify the JS code used.
360
361 * **ERR-DD-JSE002** : Problem during the evaluation of the JS code:. "JS" .. (arguments: "list of arguments")
362
363 ~=> Modify the JS code used.
364
365 = File access errors =
366
367 * **ERR-DD-FIL001**  : Unable to open the file: "File name"
368
369 ~=> Check that the file exists. Also check the read / write rights on the file.
370
371 * **ERR-DD-FIL002**  : Cannot copy the file: "Name of file 1" to "Name of file 2"
372
373 ~=> Copy error when synchronizing files. Check the write rights and the space available on the server to which the file must be copied.
374
375 * **ERR-DD-FIL003**  : Unable to save the file: "File name"(((
376 ~=> Check the write rights and the space available on the server to which the file must be saved.
377 )))
378 * **ERR-DD-DIR001**  : Unable to create the folder: "Folder name"(((
379 ~=> Check the write rights and the space available on the server on which the folder must be created.
380 )))
381 * **ERR-DD-DIR002 ** : Unable to access the folder: "Folder name"(((
382 ~=> Check the write rights and the space available on the server on which the file must be saved.
383 )))
384 * **ERR-DD-URL001**  : **Malformed** URL: "URL"
385
386 ~=> Check the URL indicated
387
388 * **ERR-DD-URL002**  : Error downloading the URL "URL"
389
390 ~=> Check the URL used
391
392 * **ERR-DD-URL003 ** : Connection to the server failed
393
394 ~=> Check that the server used is well connected
395
396 * **ERR-DD-URL004**  : The server did not respond quickly enough
397
398 ~=> Check that the server used is connected
399
400 * **ERR-DD-DTR001**  : Error during media transcoding. Stream transcoding failed.
401
402 ~=> The video generation failed (check the logs accessible from **Configuration / Server status** for more information)
403
404 = XML error =
405
406 * **ERR-DD-XML001**  : **Malformed** XML file
407
408 ~=> Check the XML file indicated by opening it for example in a browser
409
410 * **ERR-DD-XML002**  : Problem while saving XML(((
411 ~=> Check the write rights and the space available on the server on which the folder must be created.
412 )))
413 * **ERR-DD-XML003**  : Invalid XML configuration
414
415 ~=> check in the log file (accessible from **Configuration / Server status** ) ** **the XML concerned and the nature of the problem.
416
417 * **ERR-DD-XML004**  : Bad root tag in the XML file
418
419 ~=> Check the root tag in the XML file indicated
420
421 = File cleaner errors =
422
423 The status of the file cleaner is available from the **Configuration / Server status page in the ** "File cleaner status" section. A red cross indicates that an error has occurred. Position your mouse on this cross to obtain information on the error:
424
425 * **WNG-DD-FGC001**  : File cleaning canceled due to active task (s).
426
427 ~=> The file cleaner only passes if no task is active (if tasks are active, new cleaning attempts will be made later).
428
429 Consult the documentation "advanced settings of system parameters" (digdash_enterprise_guide_avance_systeme_en.pdf), section **Automatic file cleaning ** for more information on the operation of the file cleaner and the parameters that can be used
430
431 * **WNG_DD_FGC002 ** : Cleaning of files canceled due to active session (s).
432
433 ~=> The file cleaner only passes if no user session is active. Consult the documentation "advanced settings of the system parameters" (digdash_enterprise_guide_avance_systeme_fr.pdf), section **Automatic file cleaning ** for more information on the operation of the file cleaner and the parameters that can be used (possibility of automatically deleting active sessions when the cleaner starts up) , for example).
434
435 = License errors =
436
437 * **ERR-DD-LIC001** : Access denied (check license)
438
439 ~=> Open the **Configuration / License management** page to check your license: check that the key is identical to that provided by our sales team. Test the license to obtain information on it. Contact our sales team if the problem persists.
440
441 * **ERR-DD-LIC002** : The identifier of this key is unknown. Please verify your license key.
442
443 ~=> Open the **Configuration / License management** page to check your license: check that the license key entered is the one provided by our sales team. Contact our teams if the key provided does not work.
444
445 * **ERR-DD-LIC003** : Unable to decrypt the key. Please verify your license key.(((
446 ~=> Open the **Configuration / License management** page to check your license: check that the license key entered is the one provided by our sales team. Contact our teams if the key provided does not work
447 )))
448 * **ERR-DD-LIC004** : The license has expired.(((
449 ~=> Open the **Configuration / License management** page to check the expiration date of your license. Contact our sales team to acquire DigDash Enterprise or extend its evaluation.
450 )))
451 * **ERR-DD-LIC005** : Unable to parse the key. Please verify your license key.(((
452 ~=> Open the **Configuration / License management** page to check your license: check that the license key entered is the one provided by our sales team. Contact our teams if the key provided does not work
453 )))
454 * **ERR-DD-LIC006** : Unable to migrate to this license. It does not allow you to authorize as many users. Please verify your license key or remove users from the current license.
455
456 ~=> the error occurs if you are using a license with fewer users than the license you are currently using. Check the key provided with our sales team.
457
458 * **ERR-DD-LIC007** : The key is in an unsupported version. Please verify your license key.
459
460 ~=> Contact the DigDash sales department who will provide you with a key corresponding to your version of DigDash Enterprise.
461
462 * **ERR-DD-LIC008** : Invalid license. Please verify your license key.(((
463 ~=> Open the **Configuration / License management** page to check your license: check that the license key entered is the one provided by our sales team. Contact our teams if the key provided does not work
464 )))
465 * **ERR-DD-LIC009**  : Access denied (check license).
466
467 ~=> Open the **Configuration / License management ** page to verify that the key used is the one supplied to you. Contact DigDash sales if the key provided does not work.
468
469 = Password errors =
470
471 The following errors are displayed if the user does not respect the password policy set up by the administrator of DigDash Enterprise (for more information on setting up a password policy, see the documentation password_policy_config_en.pdf).
472
473 In the following cases, the user must change his password to comply with the rules:
474
475 * **ERR-DD-POLI001** : The attribute "Attribute name" does not correspond to the defined model
476 * **ERR-DD-POLI002** : The attribute "Attribute name" must contain at least one capital letter
477 * **ERR-DD-POLI003** : The attribute "Attribute name" must contain at least one lower case
478 * **ERR-DD-POLI004** : The attribute "Attribute name" must contain at least one numeric character
479 * **ERR-DD-POLI005** : The attribute "Attribute name" must contain at least one special character
480 * **ERR-DD-POLI006** : The attribute "Attribute name" must not contain the uid
481
482 = Other errors =
483
484 * **ERR-DD-RSS001 ** : Error loading RSS "name of RSS"
485
486 ~=> the indicated RSS cannot be loaded. Check the logs for the cause of the problem
487
488 * **ERR-DD-RSS002**  : Empty RSS to "RSS name"
489
490 ~=> the indicated RSS is empty.
491
492 * **ERR-DD-ERR001**__ __: An error has occurred
493
494 ~=> check the logs (accessible from the **Configuration / Server status page** ) for more information on the nature of the problem
495
496 * **ERR-DD-ERR002**  : Not implemented
497
498 ~=> the indicated function is not implemented. See DigDash for more information.