The Error Codes from ezScript are outlined below. You can interpret these return codes within your build make systems or command batch files and handle your own error exceptions and conditions. These return codes are the equivalent of Windows ErrorLevel Codes.

ErrorLevel

Description

0

Operation was completed successfully.

1

Non-supported command.

  • Try upgrading to a newer version of Alchemy CATALYST.

2

Invalid or incorrect command line parameter specified.

  • Check syntax and programmer reference material for ezScript command.

3

Cannot create file/folder.

  • Check file/folder permissions.

4

File open failure.

  • Check for valid filename/path and permissions.

5

Cannot extract file successfully.

  • Check filename/folder name for permissions.

6

Missing Parameter: A destination folder was not specified.

  • Add destination folder to command and retry,

7

Cannot create TTK.

  • Check for valid filename and folder permissions.

8

Cannot find folder in Project TTK

  • File folder mismatch when importing translations. Check name of folder and that it exists in Project TTK.

9

Invalid filename or file type parameter.

  • Check for valid filename/path and permissions.

10

Cannot Update file for this Project TTK.

  • Attempt to update a file in a Project TTK has failed. Check file exists in Project TTK.

12

File Error: An empty or invalid file has been specified.

  • Check for valid filename/path and permissions.

13

File Error: Glossary extraction failed due to incorrect filename or insufficient permissions.

  • Check for valid filename/path and permissions.

14

Required glossary name was missing.

  • Check for valid filename/path and permissions.

15

Incorrect folder name specified as parameter.

  • Check for valid filename/path and permissions.

16

TMX Source or Target Language parameter missing.

  • Verify source and target languages are valid for TMX file.

17

The Polling for a License command could not retrieve a license and has been unsuccessful.

  • Check Machine ID is valid and is accessible via LAN/WAN.
  • Check network permissions.
  • Consult the ServerLicenses.log on the Alchemy NLM Server to determine the error at the server level.

18

ezScript feature not allowed with current license type.

  • Upgrade to Localizer or Developer/PRO to use this command function.

19

Incomplete installation detected or required 3rd party installation could be missing.

  • Re-install Alchemy CATALYST.
  • Make sure you have all the required Alchemy Components activated.
  • Make sure all necessary 3rd party components are installed on the machine.

Contact the support team for any further information.

20

Evaluation License Error: Cannot find a valid Alchemy CATALYST evaluation license.

  • Check evaluation license has not expired. If it has request a new one.

24

The insertion of the .NET file failed.

  • There will be a reason written to the log to indicate the reason behind the fail. For example a referenced image may not have been found.

26

There is a problem with the file CatAl20.dll which is required for file extraction

  • Re-register the file CatAL20.dll by running NetReg.reg.
  • Re-install Catalyst.

27

There is a problem with the file CatAlWpf.dll which is required for file extraction

  • Re-register the file CatAlWpf.dll by running NetReg.reg.
  • Re-install Catalyst.

28

There is a problem with Assembly Linker for recompiling the .NET file

  • Re-install Catalyst might fix the problem.

29

Clean Up Expert: TTK file has the same Source and Target Languages

  • Open the TTK files to be cleaned up and make sure that the Source and target Languages have been set correctly.

30

There are no translated TTKs in GlobalLink Enterprise with the TTK file name specified.

  • Check your ezScript settings and verify the settings.

31

There was an error creating the target folder for the files retrieved from GlobalLink Enterprise.

  • Make sure you can create a folder in the path you have specified.

32

GlobalLink Enterprise retrieval failed.

  • Check that you can connect to your GlobalLink Enterprise instance using a web browser and try again.

33

The supplied language is not valid.

  • Check the language codes in your GlobalLink Enterprise instance.
  • The language will be omitted for this submission.

34

Error reading target language settings.

  • Verify the target language syntax. Multiple target languages need to be separated by a space e.g. "en-ie fr-fr".

35

The TXLF file belonging to a TTK in a downloaded submission could not be found.

  • Please re-download it again from GlobalLink Enterprise to the same directory as this TTK, then re-try opening the TTK.

36

Error writing temporary configuration information for GlobalLink Enterprise submission.

  • Please check you have appropriate file permissions and try again.

37

The supplied target languages does not match.

  • The TTKs’ target languages did not match any of the GlobalLink Enterprise target languages selected by the user for this submission.
  • This will only happen if you do not use the /all switch and the languages don’t match.
  • Verify the languages codes against your GlobalLink Enterprise instance.

38

The GlobalLink Enterprise web service API returned an error

  • Check the ezScriptBatchLog.txt for additional information regarding the error.
  • Check your GlobalLink Enterprise instance in a web browser and then retry.

39

Could not connect to GlobalLink Enterprise

  • Check your GlobalLink Enterprise instance in a web browser and then retry.

40

Error while running the /GetLangs command.

  • Could not open the stats.xml file within the TTK file for processing.
  • Check what the version number the TTK file was saved in.