Bladed Knowledge Centre Help library Troubleshooting Installation
Running installers requires administrator privileges
All Windows installers should be run by right-clicking on the installer file and clicking the Run as administrator option in the context menu.
All Linux installers should be run using the sudo option.
If Bladed does not appear to have installed correctly, try running the installer again, ensuring that it is run with administrator privileges.
Sentinel Run-time Environment Installer v7.103 error
An error message is displayed when running a Bladed 4.15 or earlier installer, stating that there was an "error when starting the aksfridge service with parameters 1216 2 1":
This error has been reported when installing Bladed on Windows 11 machines.
Cause:
This error message is displayed by the v7.103 Sentinel licence runtime installer (which is run as part of the overall Bladed 4.15 (or earlier) installation process, if the Sentinel HASP Runtime Environment option is selected on the Select Components installer screen).
The specific cause of this error is not known, but it is likely to be due to the licence runtime version being incompatible with the Windows version that it is being installed on. v7.103 of the license runtime pre-dates the release of Windows 11, and may therefore be incompatible with certain builds of this OS version.
Solution:
The issue can be resolved by running a Bladed 4.16 (or later) installer - this includes a later version of the Sentinel licence runtime (v9.16), which is backwardly compatible with Bladed 4.15 and earlier versions. Please follow the steps below:
- Download a Bladed 4.16 (or later) installer from the Downloads page.
- If you cannot download Bladed installers from the Downloads page, please contact us for further assistance.
- Run this installer by right-clicking on the installer file and selecting the Run as administrator option.
- On the Select Components installer screen, untick the Bladed option, and make sure that the Sentinel HASP Runtime Environment option is ticked (it should already be ticked by default).
- Proceed through the rest of the installer screens.
- If the installer finishes running successfully, run the pre-Bladed 4.16 installer again (i.e. the installer that was run originally, which produced the error message) using the Run as administrator option, to ensure that this version is fully installed.
- Note that the Sentinel HASP Runtime Environment option on the Select Components installer screen will not be ticked by default, as the licence runtime has now already been installed by other installer in the previous step.
Installation log files
Bladed installers generates up to three log files. These can be inspected to check for issues during the installation process.
To obtain the installation log files:
- Open File Explorer.
- Enter %temp% in the address bar - this opens the temporary system folder for the logged in user.
- Find all files with a format similar to Setup Log 2025-01-15 #001.txt in the folder.
- The filenames begin with "Setup Log", followed by the date of the installation and an incrementing installation counter.
- Up to three files related to each installation are generated, with #001, #002 and #003 suffixes by default, corresponding to the Bladed, Batch and PreProcessing components of the overall installation.
- Note that if more than one installation is attempted on the same day, the number suffixes will continue to be incremented (i.e. #004, #005, #006, etc.). You may need to inspect the contents of the files to identify the relevant files related to a particular installation, e.g. by using the timestamps within the files.
- Send all relevant log files as email attachments to the Bladed support team for further assistance with any installation issues.
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