WCCOAascii
The ASCII manager allows importing, exporting and change data points and data point types as well as configurations of data points. The information is passed to the ASCII manager in an ASCII file (that is the reason why the manager is called ASCII). Fore more information on ASCII manager and its options see ASCII manager.
ASCII In/Out Error Codes
Errors occurred during the ASCII import or export are written to the WCCOAascii<manager number>.log log file with the corresponding error code. Thereby means
- a negative error code that an error has occurred,
- a positive error code that a warning message should be noted
- and 0 that no errors occurred during the import/export.
The error codes have the following meaning:
| Error Code | Meaning |
| -1 | ASCII export interrupted. |
| -2 | General error during ASCII export. |
| -3 | Numbers of languages in config file and database differ (ASCII export). |
| -4 | Could not open RAIMA DB (ASCII export). |
| -5 | Errors during executing the ASCII initializing function (ASCII export). |
| -6 | Moving file failed (ASCII export). |
| -7 to -10 | ASCII export interrupted. |
| -11 | Cannot open file (ASCII input). |
| -12 | Error during ASCII initialization. |
| -13 | Errors during DP check. |
| -14 | Line <line number>: Data point <name> does not exist / first field must not be empty. |
| -15 | Default user or wrong password. |
| -16 | DP does not exist. |
| -17 | Attribute does not exist. |
| -18 | Element does not exist. |
| -19 | Attribute does not exist. |
| -20 | No DPT Container available. |
| -21 | Could not get type for attribute. |
| -22 | Cannot handle attribute type for attribute. |
| -23 | Could not set value for attribute. |
| -24 | Internal DP <name> not found. |
| -25 | Element of data point does not exist. |
| -26 | DP: <DPname> Type: <DPTname> does not exist. |
| -27 | Illegal character in name <name>. |
| -28, -31 | Can not get type for attribute <name>. |
| -29, -32 | Second value of attribute <name> is not sent (it was in the same line). |
| -30, -33 | Attribute <name> does not exist. |
| -34 | Warning: first field must not be empty in line <line number> - line ignored. |
| -35 | Warning: too many fields on line <line number> (max. <maxNumberOfAllowedLines>). |
| -35, -46 | String <string> is too long. |
| -36, -51 | Cannot handle attribute type for attribute <name>. |
| -37 to -40, -42 to -45 | Value <value> has wrong type for attribute <name>. |
| -41 | Cannot read integer value <value> for char attribute <name>. |
| -43 | Date format or time format error |
| -47 | Error in String <string> for attribute<name>. |
| -48 | Error in String %s. |
| -49 | <text> is not a langtext. |
| 49 | Warning if something is wrong with a Langtext (e.g. LANG keyword is not where expected, number of specified languages is wrong, or other syntax errors in a Langtext). |
| -50 | DpIdentifier <DpId> for attribute <name> does not exist. If, for example, the corresponding poll group data point does not exist when importing a peripheral address, error code -50 occurs. |
| -52 | Can not append value for attribute <name> in DynVar. |
| -53 | Type name illegal: <name>. |
| -54 | Warning: element name without type name found in line <line number>. |
| 55, 58 | <name>: Data point %s already defined with ID <id>. |
| 56 | Data point (xxx) with ID xxx already exists, new ID will be generated. |
| -57, -59 | Warning: first field must not be empty in line <line number> - line ignored. |
| -60 | Could not create simple message. |
| -61 | Error: doAliasRecord - Field: <number> not defined. |
| -62 | Line <line number>: Data point/Element <name> does not exist. |
| -63 | Warning: not enough fields in line <line number> - line ignored. |
| -64 | Data for type <typeName> not sent due to name error. |
| -65 | Warning: cannot determine difference between old and new type <typeName>. |
| -66 | Error: type <typeName> is not consistent - not created. |
| -67 | Error: illegal name <name> in type <typeName>. |
| -68 | Error: referenced type <typeName> does not exist |
| 69 |
<name>: Element with ID <id> other than <name> already exists, given ID will be ignored. Solution: Export the instances of the DPT separately from the source project. Delete the DPT and all its instances from the project before updating it to a higher WinCC OA version. Then, import the instances exported before manually to the target/updated project. |
| -70 | Error: illegal empty field before <name> in line <line number>. |
| -71 | Data point name illegal or undefined in some language near line <line number>. |
| -72 | Invalid Format 3/4 Specification - KeyWord Action not found. |
| -73 | No change permission for user: <user>. |
| -74 | Element name illegal or undefined in some language near line <line number>. |
| -75 | New/Delete permission missing for user: <user>. |
| -76 | No PowerConfigs found (ASCII export). |
| -77 | Cannot open file (ASCII export). |
| 77 | Data point element name was changed by the ASCII import |
| 83 | Attribute for one or more not existing data point elements has been found. The error has been ignored as "ignoreNonExistingDps" is active. |
Please note that for UNIX based operating systems an automatic conversion of negative return values to positive values is performed. To compare the return values with the entries in the table above following manual conversion must be performed:
if ( _UNIX && (rc > 127) )
rc -= 256;
