hfss failed to checkout license verification

Or, if a case subdirectory is used (i.e.zip/tar/etc the input files at the directory level where the command will be executed.The Rescale platform will assume that the prepared input files are packaged at the top directory level.Rescale will execute the software Command(s) indicated on the Software Settings page in the same working directory where the compressed files will be unpacked.Use relative file paths in scripts, input files and other job definitions.Ensure that the compressed input file deck will expand to the proper directory paths.Ensure that all of the required files have been included in the job either individually or in a compressed (zip, tarball, etc) input file deck.While there are a wide variety of failure mechanisms, some of the most common issues as well as steps to diagnose and avoid them are listed below. These error codes, of course, are not the most instructive, however, they provide a starting point for debugging. Undetermined exit mode, including explicit termination of the process or out of memory Common exit codes you may encounter: Exit Code out of memory, core dump, out of disk space, etc), the process will produce a non-zero exit code. When the program does encounter an explicit system error (i.e. This of course does not guarantee that the job ran as you intended. While a job may complete with code 0, this simply means that the process ran without producing any errors. If an analysis method runs smoothly and exits cleanly without posting any error messages it should produce: One key field to look for is the “exit code” at the end of the process_output.log file. Most of the time, the error can be identified here.Carefully review this log file and look for warning or error messages.If the file is too large, you may first need to download the file before viewing it in a text editor.View the process_output.log file using the screen icon in the Actions column.Usually log or process is a sufficient search term.To find the process_output.log file go to the Job Results page.It will also log any potential error messages.

This file logs the standard output from the software analysis method you are running. The first step we would always suggest for every job, successful or otherwise is to review the process_output.log file.

Does the command properly pass the validation step ( Validating Input) with a green check? Are there error messages present in the Job Logs section?Īre there error messages present in the Job Logs section?.

Review the output on the Job Status pageĮxamine the job history on the Gantt chart.

We will also discuss ways on how to avoid and correct them. We will try to show you how to diagnose some of these errors.

In this guide we will show you some common sources of errors encountered by users running jobs in batch on the Rescale platform.

Hfss failed to checkout license verification