User interface

Bladed Knowledge Centre Help library Troubleshooting User interface

Menu text size is too large

The Windows display scaling setting may need to be adjusted if the text size of the menu bar in the main Bladed GUI window appears to be too large.

To try to resolve the issue:

• Close the Bladed GUI
• Right-click on the Windows desktop and click “Display settings”
• Change the text size setting to 100%
  
  
  
  
• Restart Bladed

If this does not resolve the issue, click here for further suggested workarounds for resolving font and display issues (click here to download the "Font Fix.reg" file referenced in the document).

MATLAB errors

Problem:

When attempting to open or close certain screens in the Bladed GUI, a message box appears stating "Failed to call GHView.dll" (or similar) is displayed. This is usually associated with failure to open a screen such as the Turbine View.

This also applies to some other DLLs, such as CallView.dll and sometimes dtlinmod.dll.

Cause:

The DLL file in question is a MATLAB one (MATLAB version 7.2) which has complex dependencies on the MATLAB runtime framework and other parts of the environment (which certain screens and functionality depend on). The error indicates that there is a problem with the MATLAB runtime.

Solution:

To try to fix this issue in Bladed 4.12 and earlier versions, try replacing the AsynchMatlabInitialiser DLL file in the Bladed program folder, using the instructions below (please note that this is not relevant for Bladed 4.13 or later versions):

• Close all Bladed instances.
• Rename the existing AsynchMatlabInitialiser.dll file in the Bladed program folder to e.g. AsynchMatlabInitialiser_OLD.dll to back up the existing version.
• Download the new version of the DLL file using this link.
• Copy the downloaded DLL file into the Bladed program folder.
• Open Bladed and try running a MATLAB calculation, e.g. the Linear Model post-processing, to test if the fix has been successful.

Some other suggestions which have worked for this problem in the past are listed below, in the approximate order that we suggest trying them:

• Make sure you are running as Administrator (right-click the Bladed icon, choose Run as administrator from the context menu).
• Check regional settings. If these are non-UK, it can prevent MATLAB from working properly.
• Make sure you are running Bladed "normally", i.e. by clicking an icon in Start Menu / Desktop / File Explorer. (Running from within a command prompt can cause problems with MATLAB paths).
• Check whether there are multiple (potentially conflicting) versions of MATLAB installed on the machine.
• Firewall or other security settings can be a factor. If GHView used to work and doesn’t any more, ask your IT department if anything of this kind has changed recently.
• Re-run the Bladed installer, including only the Matlab Runtime option (untick all other options). This will fix repair the installation in the unlikely event that it was corrupted.
• Whitelist Bladed_m72.exe / temporarily suspend antivirus.
• Registry settings: MATLAB calculations only have visibility of the run-time library when launched from the Bladed user interface. When the user interface loads it reads the MATLAB runtime path from the registry. Please check that the following key is present in the registry by running the Registry Editor. You can do this by clicking the Windows Start Menu and typing regedit.
  The key to look for is: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Bladed_m72.exe
  Check the key has the following string values:
  • A “(Default)” string value containing the UI path of the last Bladed version installed, e.g. C:\DNV\Bladed 4.16\Bladed_m72.exe
  • A “Path” string value similar to the following:
    C:\WINDOWS\SysWOW64\GarradHassan\Common Files\Matlab\7.2\v72\bin\win32;C:\WINDOWS\SysWOW64\GarradHassan\Common Files\Matlab\7.2\v72\runtime\win32;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\ia32\compiler;C:\Program Files (x86)\Common Files\Intel\Shared Files\fortran\bin\ia32;
• It may be necessary to reinstall the MATLAB runtime framework. Use the Bladed installer for this, and when you get to the “Select Components” screen, untick Bladed and tick MATLAB Runtime.
• Check whether Bladed_m72.exe is being run in XP Compatibility mode. (Right-click on the file, choose "Properties", then the Compatibility tab.Check whether the "Run this program in Compatibility mode" box is ticked, and whether the associated dropdown is set to Windows XP. If this mode is not enabled, try enabling it).

If none of these work, you may need to try setting the MATLAB path in a command prompt, then running Bladed from the same command prompt. Do this as follows:

• Open a command prompt as Administrator in the Bladed program folder
• Set the path variable to include MATLAB folders, using the command below:
  set path=C:\WINDOWS\SysWOW64\GarradHassan\Common Files\Matlab\7.2\v72\bin\win32;C:\WINDOWS\SysWOW64\GarradHassan\Common Files\Matlab\7.2\v72\runtime\win32;%path%
• Launch the Bladed user interface from this command prompt (using the command Bladed_m72.exe)

If this works, for future convenience you can create a simple batch file in the Bladed program folder, and place the above two commands into the batch file (the set path followed by Bladed_m72.exe). Then can you run this batch file as Administrator in future instead of running Bladed_m72.exe directly.

"Terminal services (remote terminal) detected" error

The following error message is shown when trying to open the Bladed user interface on a machine over an remote desktop (RDP) session:

Local licence error: Terminal services (remote terminal) detected (haspStatusTerminalServiceDetected).

Cause:

The remote machine is using a standalone licence (i.e. a standalone dongle is plugged into the remote machine). The licensing system does not allow standalone licences to be used on machines which are accessed remotely.

Solution:

If you wish to connect remotely to a machine using an RDP session, the remote machine must be hosting a network dongle.

"Automation Error" / "Graphics error" when launching Tower, Wind Data and Data View screens

An "Automation Error" or "Graphics error" is reported and the Bladed user interface crashes following dismissal of the error dialog in the following scenarios:

• Viewing monopile tower definitions
• Viewing the wind data within a wind file
• Plotting Bladed results using the Data View screen

The error message may appear like this:

The errors manifest only when the Windows version used is Win 10 Build 1909 or newer and the user is accessing the machine over a Remote Desktop (RDP) connection. All known cases of this error were also reported on computers that have an NVIDIA Quadro family graphics card.

Solution (General):

The general solution is to disable the local computer policy that mandates the use of Windows Display Driver Model (WDDM) display driver for RDP on the RDP host machine - i.e. the machine that you are running the Bladed User Interface on.

Note that an alternative solution is also available specifically for the scenario where the Data View screen is being used (see Solution (Data View scenario) section below).

Follow the steps below to make the necessary policy change.

1. Establish an RDP connection to the machine that is showing the error.
2. Launch the Group Policy Editor (search either for Edit group policy or gpedit.msc"** in Windows Search > right-click > click Run as administrator).
   
   
   
   
3. Navigate to the following policy group within the Group Policy Editor:
   
   Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment
   
   Within this group, locate the setting named Use WDDM graphics display driver for Remote Desktop Connections and disable it. You can double-click the setting to bring up the policy editor, choose the Disabled radio button and click OK to perform this edit. See images below for reference:
   
   
   
   
   
   
4. Restart the remote machine to allow the setting change to take effect.
5. Reconnect to the remote machine over RDP and check the Bladed functionality that originally caused the error to make sure the fix has been effective.

Solution (Data View scenario):

Alternatively, it is possible to avoid the "Graphics error" when plotting results using the Data View screen by using the separate Results Viewer application instead (available to download from the Downloads page). This application can be installed on the remote machine and used over an RDP session, and it is not affected by the graphics issue.

"Run-time error ‘13’: Type mismatch" error

This error occurs when Bladed 4.3.0.79 (and all earlier versions) request a licence hosted on a NetTime 250+ dongle.

There are two possible workarounds:

1. Upgrade to Bladed 4.3.0.80 or later.
2. Use a different dongle type, such as a NetTime 50, or a local dongle. Contact us to discuss making changes to your licences/dongles.

"Run-time error ‘91’: Object variable or With block variable not set" error

This error occurs when the user chooses the Retry option after the initial licence check fails on start-up:

The issue affects Bladed 4.9 to 4.11, and has been fixed in the following versions:

• 4.9.0.34
• 4.10.0.26
• 4.11.0.16

User interface licence log file

The user interface licence log file (HASPUI.LOG) can be generated if the user interface licence is not functioning correctly:

1. Open an administrator command prompt (type cmd.exe into the Start menu, right-click the app and choose Run as administrator).
2. Change directory to the Bladed installation folder, e.g. cd /d “C:\DNV\Bladed 4.17”
3. Run the command: Bladed_m72.exe -log
4. Reproduce the issue, and close Bladed.
5. A log with filename HASPUI.LOG will have been written to the Bladed installation folder.

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