Skip to content

Error display

All scripts that are started via the script interpreter (e.g. ScriptBefore.../ScriptAfter...) automatically output information via the Windows API function OutputDebugString. Messages displayed there can tell whether a script was called at all or whether the corresponding SCRIPT file was not found.

This makes it easy to identify the following 3 cases:

  • Script is not started for component type ID.
[...] ScriptAfterCheckInS N0001 : Copy Config file to [...]
[...] ScriptAfterCheckInS N0002 : script not found (`D:\vdServerArchive\VD$A\Scripting\Server\9D72DE8F21004CE4BE8C2BE11FC00403.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) must be adapted and the component type ID must be checked.
  • The script is not started at all.
  • There is no output when the script is executed. The following line is not displayed.
[...] Script[...] N0001 : Copy Configfile to [...]
  • The corresponding interpreter was not called. This may be due to the file being corrupted during transfer or being blocked by an anti-malware product. Log files (Windows Event Viewer) can provide further information here.
  • The script is started, but an error occurs.
  • If the script contains the call command, for example, external errors can cause the script to end unexpectedly.
  • In this case, the following line is output at the end of execution (exit code not equal to 0).
[...] Script[...] : Exitcode = -1 [Line 56] Returned from component type script
  • It must be checked here whether any error messages are mentioned in the preceding lines of the SCRIPT file that allow a more precise localization of the error.