Batch

Batch log file

The Batch application creates a log file of all significant events. This can be inspected to check for issues related to Batch, and will normally be requested by the Bladed support team when investigating Batch problems which cannot be immediately resolved.

To obtain the Batch log file:

1. Open File Explorer.
2. Enter %temp% in the address bar - this opens the temporary system folder for the logged in user.
3. Find the GH.BatchFramework.Client.log file in the folder. Note that older versions of the log file may also be present in the folder, with a number appended at the end of the filename, e.g. GH.BatchFramework.Client.log.1, GH.BatchFramework.Client.log.2, etc.:
   
   
   
   
   • It is important to find the specific log file(s) that covers the timespan of the problem occurring, as well as the Batch startup which is often a stage when problems show themselves. The relevant file(s) can be identified by checking the timestamps within the files.
   • If you have difficulty in finding the relevant log file(s) It may be helpful to close Batch (right-click the Batch icon in the Windows system tray, and click Exit), restart Batch (by searching for "Batch" in the Start menu, or running a simulation in Batch from the Bladed GUI), carry out whatever steps are needed to reproduce the error, and locate the log file(s) that cover the whole sequence of startup and error occurrence.
4. Send all relevant log files as email attachments to the Bladed support team for further assistance with any Batch issues.

Note that you may need to gather log files from more than one machine in some instances, e.g. where it's not clear if the problem is with the manager or runner.

Error: Could not find Batch framework

An error message is displayed stating that the Batch Framework could not be found when starting the Bladed GUI.

Cause

Batch is not installed on the machine.

Solution

Try running the Bladed installer again to reinstall Bladed. If the same error message still occurs, please contact us for further assistance.

Error: A listener already exists on port 808

This message can have a few variations, but the common theme is that Batch fails and an error window appears which mentions port 808, "IP endpoint 0.0.0.0:808" or similar.

Cause

Batch uses port 808 for communication. The error message is indicating that two processes are conflicting over the use of a resource (port 808) which can only be used by one at a time. It could mean another Batch process is trying to use the same runner, but it could be any application and may have nothing to do with Batch or Bladed.

Solution

Check what process is binding to port 808 via the command line. Use the "netstat" command as illustrated below to do this:

Once you know the Process ID (or "PID") - 2424 in this example - you can find out from Task Manager what the process/service is. Make sure you look at the “Details” tab in Task Manager (and not the "Processes" tab, as it does not include all processes and services).

In this example, PID 2424 is the Bladed Batch manager itself, which shows that there is no conflict on port 808. However, if you have had the error message there will probably be a different process binding to this port. Often the answer is to stop the process that is binding to the port and then Batch will start working again.

Intel graphics drivers conflict

There a is specific known conflict with some Intel graphics drivers, which also use port 808. If this appears to be the source of the conflict, it may be possible to install an updated graphics driver which resolves this issue. Please see this Intel support page for further details.

Error: Program terminated unexpectedly (for Bladed 4.10 or earlier jobs)

A Batch job using Bladed 4.10 or earlier fails with a "Program terminated unexpectedly" error, but it runs successfully from the Bladed GUI using the "Run Now" button.

Cause

A potential cause of the error message is that the Batch client was not started with admin rights, which are required to run Bladed 4.10 simulations. This may have happened if Batch was opened at the same time as Bladed 4.11 or later (which does not require the use of admin rights), but the job being run from the Batch instance uses Bladed 4.10 or earlier (which does require admin rights).

Solution

Follow the steps below:

• Close the currently running instance of the Batch client (if applicable), by right-clicking on the Batch icon in the Windows system tray, and clicking Exit.
• Start the Batch client application by right-clicking on the Start menu shortcut (or the GH.BatchFramework.Client.exe file in the Batch application folder) and selecting the Run as administrator option.
• Reset the failed job in the Batch job list.
• Try running the job again.

If the error still occurs after following the steps above, please contact us for further assistance.

Error: Sequence contains no matching element

The Batch client user interface terminates with a handled exception stating that the "Sequence contains no matching element". The Batch log file also contains a corresponding entry:

System.InvalidOperationException: Sequence contains no matching element

Cause

This results from the corruption of a Batch configuration resulting from a failure to save a job status correctly or a crash during a prior operation.

Solution

The simplest resolution to this is the deletion of the contents of the Batch folder: C:\Users\XXXXX\DNV\Batch\DefaultBatchDirectory (by default).

WARNING! Deletion of the contents of this folder will remove the corrupted element but also the Batch configuration - it will need to be set up again.

Simulation with external controller crashes in Batch with DiscPlot DLL error

Simulations with external controllers crash when run from Batch with an error message similar to

"Windows Error 0 was returned from LoadLibraryW when trying to load the dll 'C:\Users\XXXXX\DNV\Batch\DefaultBatchDirectory\Jobs\job_XXXXX\..\DiscPlot.dll'"

reported in the message file.

Description

The DiscPlot.dll file is responsible for displaying the real-time results window when simulations that use external controllers are run from the Bladed GUI; the file resides in the Bladed installation folder (e.g. C:\DNV\Bladed 4.13). When run from Batch, the DiscPlot.dll is not normally present in the folder that dtbladed searches in (the parent folder of the location of the .in file, which in this case is the Batch Jobs folder). However, if the DLL is not found then the simulation should still continue anyway without any problems, with the real-time results window not being shown (an entry is also written to the message file to record the fact the DLL was not found).

In some rare cases a crash has been reported to occur near the start of the simulation, with an error message that refers to an error having occurred when trying to load the (missing) DiscPlot.dll file.

Solution

Although the cause of this problem is not known, a potential solution is to copy the DiscPlot.dll and DiscPlot.txt files from the Bladed installation folder into the Batch Jobs folder, i.e. so that the DLL is present in the folder that dtbladed searches in.

Error: Method not found - AWS GetCredentials()

The following error message is shown:

Method not found: Amazon.Runtime.AWSCredentials.GH.Bolt.AWS.Contracts.lAWSCredentialsProvider.GetCredentials()'.

Cause

There may be a mixed version of Batch installed.

Solution

Uninstall Batch, and run the latest Bladed installer to install the latest Batch version.

Need help?

If the information above does not help to resolve your problem, please contact us for further assistance.

When contacting us, please provide all relevant details related to the problem, such as:

• Dongle number (e.g. DT/1234) or Key ID
• Screenshots of any error messages or other symptoms
• Steps to reproduce the problem
• Any relevant log files