- 5 minutes to read

Verify Nodinite Prerequisites

Run these checks on the Nodinite Core Services server before you start the Installation Guide. Each check takes a minute and catches the problems that otherwise surface halfway through an install. The full list of what to prepare is on the Prerequisites page; this page shows how to verify it.

  • ✅ Confirm the IIS features, .NET Framework 4.8, and the .NET 10 Hosting Bundle in the right order
  • ✅ Check the SQL Server version, collation, and your sysadmin rights
  • ✅ Find DacFX (SqlPackage), MSDTC, and PowerShell 7
  • ✅ Let the CLI's install-prerequisites and validate commands check the rest

Understanding the Verification Order

The checks follow the installation order. The ASP.NET Core Module V2 only installs when the IIS features are already there, so the order matters.

graph LR A["fa:fa-server IIS features"] --> B["fa:fa-code .NET Framework 4.8"] B --> C["fa:fa-code .NET 10 Hosting Bundle"] C --> D["fa:fa-database SQL Server"] D --> E["fa:fa-file-prescription DacFX (SqlPackage)"] E --> F["fa:fa-shield-check MSDTC"] F --> G["fa:fa-terminal PowerShell 7"]

The verification order on the Core Services server: IIS Windows Features first, then the .NET runtimes, then SQL Server, DacFX, MSDTC, and PowerShell 7 for the CLI.

Check Why it matters Fix it with
IIS features and .NET Framework 4.8 The Web Client and Web API run in IIS; .NET Framework 4.8 hosts the older agents IIS Windows Features
.NET 10 Hosting Bundle Installs the ASP.NET Core Module V2 for the v7 Core Services Verify ASP.NET Core Module
SQL Server Hosts the Configuration Database and the Log Databases SQL Server Sysadmin Requirements
DacFX (SqlPackage) Deploys and upgrades the databases SqlPackage install options
MSDTC Distributed transactions between the databases MSDTC
PowerShell 7 Runs the CLI (Nodinite.Installer.Cli.exe) PowerShell 7

IIS Features and .NET Framework Verification

Install the IIS features first, then .NET Framework 4.8 (already present on Windows Server 2022 and later), then the .NET 10 Hosting Bundle, as the diagram above shows. IIS Windows Features has the complete feature list, the PowerShell installation scripts, and troubleshooting.

Important

Common Installation Failure: Installing the .NET 10 Hosting Bundle BEFORE the IIS features does NOT install the ASP.NET Core Module V2. The Nodinite v7 Web Client and Web API then fail with "500.19" errors. Always install the IIS features first, then the Hosting Bundle.

Check .NET Framework 4.8 

Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full'|Select-Object Version, Release

Expected result: Release 528040 or higher (.NET Framework 4.8.1 reports 533509). If it is lower, install .NET Framework 4.8 on the servers that host the .NET Framework 4.8 Monitoring Agents, and reboot if prompted.

.NET 10 Hosting Bundle Verification

Use the PowerShell script Verify ASP.NET Core Module to check that the .NET 10 Hosting Bundle is installed and the ASP.NET Core Module V2 is present. If it is missing, confirm the IIS features, run the Hosting Bundle installer again (Repair) on the Core Services server, run iisreset, and re-run the script.

SQL Server Verification

Check SQL Server version and collation 

-- Check SQL Server version
SELECT @@VERSION AS 'SQL Server Version';

-- Check database collation
SELECT SERVERPROPERTY('Collation') AS 'Server Collation';

-- Verify your login has sysadmin role
SELECT IS_SRVROLEMEMBER('sysadmin') AS 'Is SysAdmin';

Expected result:

  • Version: SQL Server 2012 or later. That is what the Nodinite databases target: compatibility level 110 for the Configuration Database and 100 for the Log Databases. Separately, run a SQL Server version that Microsoft still supports.
  • Collation: the Nodinite databases are created with SQL_Latin1_General_CP1_CI_AS (case-insensitive), whatever the server default is. The query shows the server default for comparison.
  • Is SysAdmin: 1 during installation. Without sysadmin, see SQL Server Sysadmin Requirements.

DacFX (SqlPackage.exe) Verification

DacFX is required for database deployments and upgrades.

Check if SqlPackage.exe is installed 

# List SqlPackage.exe in the common DacFX installation paths (150, 160, 170, ...)
Get-ChildItem "C:\Program Files\Microsoft SQL Server\*\DAC\bin\SqlPackage.exe" -ErrorAction SilentlyContinue |
    ForEach-Object { $_.FullName; & $_.FullName /version }

Expected result: at least one path with a version; no output means DacFX is missing.

If not installed

MSDTC Verification

Microsoft Distributed Transaction Coordinator (MSDTC) must be configured for Nodinite distributed transactions.

Check MSDTC configuration 

# Check MSDTC service status
Get-Service -Name MSDTC|Select-Object Name, Status, StartType

# Check MSDTC security settings
$msdtcPath = "HKLM:\SOFTWARE\Microsoft\MSDTC\Security"
Get-ItemProperty -Path $msdtcPath|Format-List

Expected result: Status Running, StartType Automatic, and NetworkDtcAccess and NetworkDtcAccessTransactions both 1. The MSDTC Configuration Guide has the complete configuration steps.

PowerShell 7 Verification

PowerShell 7 is required to run the CLI (Nodinite.Installer.Cli.exe) from an elevated prompt.

Check PowerShell version 

# Check PowerShell version
$PSVersionTable.PSVersion

Expected result: major version 7 or higher (not Windows PowerShell 5.1). The execution policy doesn't matter: the CLI is a signed executable, not a .ps1 script. If a check fails during the install itself, see Troubleshooting Installation Issues.

Let the CLI Check Too

The CLI (Nodinite.Installer.Cli.exe) has two checks of its own. Neither changes anything unless you ask it to. Run them from the extracted package root.

install-prerequisites detects IIS, Windows Authentication, the ASP.NET Core Hosting Bundles and, optionally, SQL Server Express. By default it only detects. Add --apply (run as administrator) to install what is missing, and --skip-sql or --skip-hosting-bundles to leave those out.

.\Nodinite.Installer.Cli.exe install-prerequisites --verbose

validate checks the configuration file from the Portal before you deploy: the JSON and its required fields, database connectivity, port availability, the IIS prerequisites, the service accounts, and the TLS and secret-management certificates. Add --output report.json --format json to save a report.

.\Nodinite.Installer.Cli.exe validate --config .\<server>\config.cli.json --verbose

Run validate before deploy-environment. deploy-environment runs the same pre-flight checks anyway, and stops before it deploys anything when one fails. Troubleshooting Installation Issues shows how to read the result table.

Next Steps