Known problems and limitations

Edit online

Known problems and limitations

  • The Scripting Feature is not supported on Windows™ 2003 64-bit systems.

  • Kill after timeout does not work on Solaris™ and Windows™ 32-bit OS agents.

  • The fcp_daemon can stop running scripts in Windows™ 32 bit if some scripts do not complete within the timeout period and the user enabled intensive tracing. If fcp_daemon stops running scripts, the data reported on the console reflects the last time that the script was run. It is also possible that the OS agent stops returning data. Stopping the fcp_daemon process allows the agent to resume proper operation.

  • SCRIPT_NONZERO_RETURN is returned instead of SCRIPT_NOT_FOUND or SCRIPT_LAUNCH_ERROR on Solaris™.

  • The scripting feature does not provide full globalization; some issues can be found by using Nationalized characters in property files or script outputs.

  • On Windows™ OS agent, there is no possibility of running scripts residing on a mapped network drive.

  • When the Windows™ OS agent is upgraded, the scripting feature is not enabled by default. Edit the KNTENV and change `KNT_FCP_SCRIPT=FALSE` to `KNT_FCP_SCRIPT=TRUE`