Error display

All scripts which are started via the script interpreter (for example, ScriptBefore…/ScriptAfter…) automatically issue information via the Windows API function OutputDebugString. Messages displayed there can provide information about whether a script was called at all or the associated SCRIPT file was not found.

Through this, the following 3 cases can be easily identified:

• The script will not be started for the component type ID.
  • […] ScriptAfterCheckInS N0001 : Copy Configfile to […]
• […] ScriptAfterCheckInS N0002 : script not found (D:vdServerArchiveVD$AScriptingServer9D72DE8F21004CE4BE8C2BE11FC00403.script)
• In this case, the script was not called because the corresponding SCRIPT file was not found.
• To correct this error, the corresponding INI file (here:ScriptAfterCheckInS.ini) needs to be checked and the component ID needs to be checked.
• The script will not be started.
• There is no output when the script is executed. The following line will not be displayed.
  • […] Script[…] N0001 : Copy Configfile to […]
• The corresponding interpreter was not called. This may be because the file was damaged during transfer or is blocked by an anti-malware product. Log files (Windows Event Viewer) can provide further information here.
• The script has started, but an error occurs.
• For example, if the script contains the Call command, external errors may cause the script to end unexpectedly.
• In this case, the following line is output at the end of the execution (exit code not equal to 0).
  • […] Script[…] : Exitcode = -1 [Line 56] Returned from component typ script
• Here, you need to check whether any error messages are mentioned in the preceding lines of the SCRIPT file, which would allow a more precise limitation of the error.