The tables below list error codes that you may encounter when running analytic scripts.
Scripting engine start-up errors
| Error Code | Description |
|---|---|
| 202 | System error. |
| 203 | The evaluation period has expired. |
| 204 | The evaluation period has expired. |
| 205 | Activation failed. |
| 206 | Maximum number of sessions reached. |
| 207 | Memory initialization problem(s). |
| 209 | Unknown script error. |
| 210 | Database profile password is missing. |
| 211 | Server connection failure. |
| 212 | An unsupported command was encountered. |
| 213 | A dialog box was generated by the script. |
| 256 | The scripting engine failed to start. |
Scripting engine error codes
| Error Code | Description |
|---|---|
| 1000 | No preferences file (*.prf) was found. A new default preferences file was created. |
| 1001 | The preferences file (*.prf) is missing some required information. A new default preferences file was created. |
| 1002 | The scripting engine cannot start because no preferences file (*.prf) was found and a new default preferences file cannot be created because the necessary folder permissions do not exist. |
| 1003 | The project has been upgraded from an earlier version. A copy was saved with a .old extension. |
| 1004 | The project file could not be processed. The last saved project was used. |
| 1005 | No project file specified. |
| 1006 | The specified project file does not exist. |
| 1007 | The specified project file is read-only. |
| 1008 | The specified project is currently being used by another application. |
| 1009 | The specified .old project file cannot be used. You must specify a project file with the .ACL extension. |
| 1010 | The specified project file is not an Analytics project file. |
| 1011 | The project could not be converted to Unicode. |
| 1012 | The specified project file cannot be saved as an earlier version. |
| 1013 | Unable to open the log file for writing. |
| 1014 | No script was specified. |
| 1015 | The specified script does not exist. |
| 1016 | The Analytics license was not found or is invalid. |
| 1017 | A required library file (*.dll) was not found. |
| 1018 | Data could not be saved to the working directory because it does not have write permissions. |
| 1019 | The Analytics subscription could not be validated. |
| 1020 | The Analytics license cannot be released. |
| 1021 | An unknown error occurred. |
Command errors
The table below lists the error codes that are returned when an analytic script fails because of an invalid ACLScript command. The error code number returned identifies the command that failed.
| Error Code | Command |
|---|---|
| 1 | SAMPLE |
| 2 | EXTRACT |
| 3 | LIST |
| 4 | TOTAL |
| 5 | DEFINE |
| 6 | COMMENT |
| 7 | QUIT |
| 8 | STOP |
| 9 | BYE |
| 10 | USE |
| 11 | OPEN |
| 12 | SAVE |
| 13 | DISPLAY |
| 14 | ACTIVATE |
| 15 | CLOSE |
| 16 | HELP |
| 17 | COUNT |
| 18 | STATISTICS |
| 19 | HISTOGRAM |
| 20 | STRATIFY |
| 21 | SUMMARIZE |
| 22 | EXPLAIN |
| 23 | GROUP |
| 24 | ELSE |
| 25 | END |
| 26 | CANCEL |
| 27 | SUBMIT |
| 28 | DELETE |
| 29 | RANDOM |
| 30 | SORT |
| 31 | FIND |
| 32 | DIRECTORY |
| 33 | TYPE |
| 34 | DUMP |
| 35 | INDEX |
| 37 | SET |
| 40 | DO |
| 41 | TOP |
| 42 | EXPORT |
| 43 | VERIFY |
| 44 | SEEK |
| 45 | JOIN |
| 46 | MERGE |
| 47 | SEQUENCE |
| 48 | CALCULATE |
| 49 | |
| 50 | LOCATE |
| 51 | RENAME |
| 54 | COPY |
| 55 | REPORT |
| 56 | EJECT |
| 58 | LET |
| 59 | ACCUMULATE |
| 63 | ACCEPT |
| 64 | ASSIGN |
| 65 | AGE |
| 66 | CLASSIFY |
| 67 | PROFILE |
| 68 | DO REPORT |
| 69 | LOOP |
| 70 | PAUSE |
| 71 | SIZE |
| 72 | EVALUATE |
| 73 | DIALOG |
| 74 | IF |
| 75 | GAPS |
| 76 | DUPS |
| 77 | SQLOPEN |
| 78 | PASSWORD |
| 79 | IMPORT |
| 80 | REFRESH |
| 81 | NOTIFY |
| 82 | CONNECT |
| 83 | RETRIEVE |
| 84 | FIELDSHIFT |
| 85 | BENFORD |
| 86 | CROSSTAB |
| 87 | (not used) |
| 88 | ESCAPE |
| 89 | NOTES |
| 90 | FUZZY DUPLICATE |
| 91 | EXECUTE |
| 92 | ACCESSDATA32 |
| 93 | ACCESSDATA64 |
| 94 | APPEND |
| 95 | RCOMMAND |
| 96 | CVSPREPARE |
| 97 | CVSSAMPLE |
| 98 | CVSEVALUATE |
| 99 | OUTLIER |
| 100 | FUZZYJOIN |
| 101 | CLUSTER |
| 102 | TRAIN |
| 103 | PREDICT |
Analytic job processing errors
Note
Some of these errors are specifically associated with the legacy products Analytics Exchange and AX Exception.
| Error Code | Error message |
|---|---|
| -10 | The analytic results could not be saved because the destination results folder was deleted after the analytic started running. |
| -11 | Job was stopped. |
| -12 | Stopped due to server shut down. |
| -13 | Failed to create results. |
| -16 | Could not run due to server properties configuration error. |
| -17 | Unable to create uniquely named results directory. |
| -19 | Job was skipped. |
| -20 | Could not prepare publish result tables. |
| -21 | Could not publish results to AX Exception. |
| -22 | Publish failed. Invalid table name. |
| -23 | Publish failed. One or more of the table's column names are too long. |
| -24 | Publish failed. Invalid values within data cells within an Analytics table. |
| -25 | Publish failed. Not supported data types within table fields. |
| -26 | Publish failed. Could not connect to AX Exception server. |
| -27 | Job did not run. The user was removed or does not have permission. |
| -28 | Job did not run. Unexpected error. See the server log and Analytics log for details. |
| -29 | Could not copy data files. The analytic failed because the required data files could not be copied to the jobs directory. |
| -30 |
Job did not run. The analytic link is broken. |
| -31 |
Publish failed. The exception mapping file could not be located. |
| -32 |
Publish failed. Failed to parse the exception mapping file. |
| -34 | Failed to store job results. Check that there is sufficient space on the drive storing the jobs folder and that no data files are locked. |
