Bladed versions affected: all current 4.x versions
Date of last article update: 22nd December 2022
=========================================================================
When attempting to open or close certain screens in Bladed, a message box pops up saying "Failed to call GHView.dll". 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 apparently dtLinmod.dll too.
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.
To try to fix this issue, please try replacing the "AsynchMatlabInitialiser" DLL file in the Bladed program folder, using the instructions below:
- 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 by clicking on 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 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 the IT department if anything of this kind has changed recently.
- Re-run the Bladed installer, including only the Matlab 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:\Program Files (x86)\DNV GL\Bladed 4.8\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 “Install options” 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 installation directory
- Set the path variable to include matlab folders (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 (by the command Bladed_m72.exe)
If this works, for future convenience you can create a simple batch file in the bladed installation folder, and place the above two commands into the batch file (the "set path" followed by bladed_m72.exe). Then you'd run this batch file as Administrator in future instead of running bladed_m72.exe directly.