- 0 minutes to read

Prerequisites for Installing Nodinite

Before installing Nodinite, ensure you have the necessary prerequisites for your target version. The requirements differ significantly between v7 and v6.

On this page, you will learn:

✅ Prerequisites for Nodinite v7 (recommended)
✅ Prerequisites for Nodinite v6 (legacy)
✅ Differences between v7 and v6 requirements
✅ Common prerequisites for both versions

Choose Your Version

^{New 7.x} Nodinite v7 (Recommended)

Nodinite v7 uses a PowerShell-based installation approach that simplifies deployment and configuration with .NET 9. All prerequisites are detailed in the installation guide.

Install Nodinite v7 - Prerequisites Section

Key Requirements:

Windows Server 2019 or later
PowerShell 7 installed
.NET 9.0 Runtime + ASP.NET Core Hosting Bundle
Latest DacFX (SqlPackage.exe)
IIS with required Windows Features
SQL Server 2016 or later
MSDTC configured

Tip
Nodinite v7 offers a much simpler installation process compared to v6. The PowerShell script automates most configuration tasks.

Nodinite v6 (Legacy - No Longer Supported)

If you need legacy v6 with the deprecated Install and Update Tool (web-based MSI installer):

Important
Nodinite v6 is no longer supported. We strongly recommend upgrading to v7 for the latest features, security updates, and active support.

If you need to reference v6 prerequisites:

Prerequisites - Install and Update Tool

Key Requirements:

Windows Server 2012 R2 or later (2019+ recommended)
.NET Framework 4.8
DacFX (SQL Server binaries)
IIS with Default Web Site
SQL Server 2012 or later
MSDTC configured

Comparison: v7 vs v6 Prerequisites

Requirement	^{New 7.x} Nodinite v7	Nodinite v6
Windows Server	2019+ (2016 min)	2012 R2+
Installation Tool	PowerShell 7 script	MSI + Web UI
.NET Runtime	.NET 9	.NET Framework 4.8
Configuration	Portal + PowerShell	Web-based UI
IIS Setup	Automated by script	Manual configuration
Certificate Setup	Portal configuration	Manual web.config
OAuth 2.0 Support	Yes	No
Support Status	Active	Deprecated

Common Prerequisites (Both Versions)

These requirements apply to both Nodinite v7 and v6. Use these tables as verification checklists during planning and installation.

SQL Server Requirements

Requirement	Specification	Priority	Notes
SQL Server version	2016 or later	Vital	2019+ recommended for performance and support lifecycle.
Collation	Latin1_General_CI_AS	Vital	Case-insensitive required. Cannot be changed after installation without rebuild.
Authentication	Windows or SQL Auth	Vital	Windows Authentication recommended for security. SQL Auth supported.
Installation permissions	`sysadmin` role	Vital	Required during installation only. Can be reduced post-install.
DacFX binaries	Latest SqlPackage.exe	Vital	Download from DacFX. Used for database deployments and upgrades.
Connection encryption	TLS 1.2+	Important	Configure encrypted connections for production. See ConnectionStrings.

SQL Server hosts all Nodinite data—verify these requirements before proceeding. SQL Server Connection Strings

IIS (Internet Information Services)

Requirement	Specification	Priority	Notes
IIS Role	Installed and configured	Vital	Web Server role with required features.
Windows Authentication	Enabled	Vital	Required for user authentication in Web Client.
ASP.NET modules	Core modules installed	Vital	v7 requires ASP.NET Core Hosting Bundle. v6 requires ASP.NET 4.x.
Application Pools	.NET CLR configured	Vital	v7: No Managed Code. v6: .NET Framework 4.x.
Default Web Site	Running	Important	v6 requires Default Web Site. v7 can use custom sites.

IIS hosts the Nodinite Web Client and APIs—all features must be properly configured. IIS Windows Features

Network and Security

Requirement	Specification	Priority	Notes
Firewall rules	Web Client, Web API, Log API ports	Vital	Default ports: 443 (HTTPS), 80 (HTTP). Configure Windows Firewall rules.
DNS records	Custom domain (optional)	Good to Know	Recommended for production. Example: `nodinite.company.com`
SSL/TLS Certificate	Valid certificate for HTTPS	Important	Strongly recommended for production. Self-signed OK for DEV/TEST.
Certificate trust	Trusted by clients	Important	Import CA certificate to trusted root if using internal CA.
Network latency	< 10ms to SQL Server	Important	Nodinite is database-intensive. High latency degrades performance.

Secure communication is critical for protecting integration data. Hardening

Service Accounts and Permissions

Requirement	Specification	Priority	Notes
Service accounts	Dedicated domain/local accounts	Vital	Never use personal accounts. Create dedicated service principals.
Log on as service	Right assigned	Vital	Windows Security Policy: `SeServiceLogonRight` required.
SQL Server access	Database permissions	Vital	`db_owner` on Nodinite databases. `sysadmin` during install only.
IIS App Pool identity	Configured	Vital	Service account must be App Pool identity for Web Client.
File system access	Read/Write to install folder	Important	Typically `C:\Program Files\Nodinite\` and temp folders.
Agent permissions	Platform-specific	Important	BizTalk Agents need BizTalk Admin. SQL Agents need `VIEW SERVER STATE`.

Proper service account configuration prevents authentication and permission errors.

Hardware Recommendations

Plan hardware resources based on your workload and environment type (DEV/TEST/PROD).

Minimum Requirements (DEV/TEST Environments)

Resource	Specification	Priority	Notes
CPU	2 cores (x64)	Vital	Sufficient for development and small test environments only.
RAM	8 GB	Vital	Minimum for basic operation. Increase if co-hosting SQL Server.
Disk	50 GB free space	Vital	OS + Nodinite + small SQL databases. Not suitable for production.

Minimum specs are for non-production environments only.

Recommended for Production

Resource	Specification	Priority	Notes
CPU	4+ cores (x64)	Vital	More cores improve multi-threaded processing. 8+ cores for high-volume logging.
RAM	16-32 GB	Vital	16 GB for app server. 32+ GB if SQL Server co-hosted. Scale based on workload.
System disk	100 GB SSD	Important	Fast storage for OS and Nodinite binaries. Premium SSD recommended in Azure (P20+).
SQL data disk	300+ MB/s R/W	Vital	Separate volume. Premium SSD (P30+) in Azure. Monitor IOPS and latency.
Backup storage	Network share or volume	Vital	Calculate: (# DBs × DB size × retention days). Example: 3 × 60GB × 3 days = 540 GB.

Production workloads require robust hardware—inadequate resources cause performance issues and outages.

Planning Your Nodinite Solution - Detailed infrastructure planning

Detailed Prerequisite Verification

Use these detailed checks to verify all prerequisites before installation.

IIS Windows Features Verification

IIS must be installed with required features before installing .NET components.

Installation order is critical:

First: Install IIS Windows Features - Required for hosting Nodinite Web applications
Second: Install .NET Framework 4.8 - Required for Log API WCF services
Third: Install .NET 9 Hosting Bundle - MUST be installed AFTER IIS features

IIS Windows Features - Complete feature list, PowerShell installation scripts, and troubleshooting

Important
Common Installation Failure: Installing the .NET 9 Hosting Bundle BEFORE IIS features will NOT install the ASP.NET Core Module V2. This causes Nodinite 7 Web Client and Web API to fail with "500.19" errors. Always install IIS features first, then the Hosting Bundle.

.NET Framework 4.8 Verification

.NET Framework 4.8 is required for Log API WCF services.

Check if installed:

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

Expected result: Release value should be 528040 or higher (indicates .NET Framework 4.8 or later)

Install if missing:

Download: .NET Framework 4.8
Install on the Nodinite Application Server
Reboot if prompted

Note
Windows Server 2022 and later include .NET Framework 4.8 by default.

.NET 9 Hosting Bundle Verification

.NET 9 Hosting Bundle is required for Nodinite v7 Web Client and Web API.

Check if ASP.NET Core Module V2 is installed:

# Verify ASP.NET Core Module V2 installation
$modulePath = "$env:SystemRoot\System32\inetsrv\aspnetcorev2.dll"
if (Test-Path $modulePath) {
    Write-Host "✅ ASP.NET Core Module V2 is installed" -ForegroundColor Green
    (Get-Item $modulePath).VersionInfo | Format-List
} else {
    Write-Host "❌ ASP.NET Core Module V2 is NOT installed" -ForegroundColor Red
    Write-Host "Install the .NET 9 Hosting Bundle and ensure IIS features were installed first" -ForegroundColor Yellow
}

Expected result: ✅ ASP.NET Core Module V2 is installed

If not installed:

Verify IIS features are installed (see IIS Windows Features)
Download: .NET 9.0 Runtime + ASP.NET Core Hosting Bundle
Run installer on the Nodinite Application Server
Run iisreset to reload IIS configuration
Re-run verification script above

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 results:

SQL Server version: 2016 or later (2019+ recommended)
Server Collation: Latin1_General_CI_AS (case-insensitive)
Is SysAdmin: 1 (required during installation)

DacFX (SqlPackage.exe) Verification

DacFX is required for database deployments and upgrades.

Check if SqlPackage.exe is installed:

# Common installation paths
$paths = @(
    "C:\Program Files\Microsoft SQL Server\170\DAC\bin\SqlPackage.exe",
    "C:\Program Files\Microsoft SQL Server\160\DAC\bin\SqlPackage.exe",
    "C:\Program Files\Microsoft SQL Server\150\DAC\bin\SqlPackage.exe"
)

$found = $false
foreach ($path in $paths) {
    if (Test-Path $path) {
        Write-Host "✅ SqlPackage.exe found: $path" -ForegroundColor Green
        & $path /version
        $found = $true
        break
    }
}

if (-not $found) {
    Write-Host "❌ SqlPackage.exe not found" -ForegroundColor Red
    Write-Host "Download DacFX from: https://aka.ms/dacfx-msi" -ForegroundColor Yellow
}

If not installed:

Download: DacFX (SqlPackage.exe)
Install on the Nodinite Application Server
Note the installation path for use in the Portal configuration

MSDTC Verification

Microsoft Distributed Transaction Coordinator (MSDTC) is required for 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 results:

Service Status: Running
StartType: Automatic
NetworkDtcAccess: 1 (enabled)
NetworkDtcAccessTransactions: 1 (enabled)

MSDTC Configuration Guide - Complete configuration steps

PowerShell 7 Verification

PowerShell 7 is required to run the installation script.

Check PowerShell version:

# Check PowerShell version
$PSVersionTable.PSVersion

# Check execution policy
Get-ExecutionPolicy -List

Expected results:

Major version: 7 or higher
Execution policy: RemoteSigned, Unrestricted, or Bypass (not Restricted)

If PowerShell 7 not installed:

Download: PowerShell 7
Install on the Nodinite Application Server
Open new PowerShell 7 terminal (not Windows PowerShell 5.1)

Set execution policy if needed:

# Allow running downloaded scripts (requires admin)
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

Troubleshooting Installation Issues

Use these troubleshooting steps when installation fails or components don't work as expected.

Script Execution Policy Errors

If PowerShell blocks script execution:

# Check current execution policy
Get-ExecutionPolicy

# Set execution policy to allow scripts (requires admin)
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

PowerShell Execution Policy Documentation

Database Connection Failures

If installation fails to connect to SQL Server:

Verify SQL Server service is running - Check Services.msc or use Get-Service -Name MSSQLSERVER
Confirm you have sysadmin role - Run SQL Server Verification script above
Test connection manually - Use Test-NetConnection -ComputerName SQL01 -Port 1433
Check firewall rules - Ensure SQL Server traffic is allowed (typically port 1433)
Verify connection string - Review encryption and certificate trust settings

SQL Server Connection Strings - Complete connection string reference

IIS Application Pool Failures

If IIS application pools fail to start:

Ensure service account has "Log on as a service" right - Check Local Security Policy → User Rights Assignment
Verify service account password is correct - Test credentials with runas command
Check account is not locked or expired - Verify in Active Directory Users and Computers
Review IIS logs - Check C:\inetpub\logs\LogFiles for detailed errors
Verify ASP.NET Core Module V2 - Run .NET 9 Hosting Bundle Verification above

IIS Windows Features - Complete IIS configuration guide

Service Installation Failures

If Windows Services fail to install:

Confirm service account has permissions - Account must have rights to install Windows Services
Verify no existing services with same name - Check Services.msc for conflicts
Check Windows Event Logs - Review Application and System logs for detailed error messages
Ensure service account is not local Administrator - Use dedicated service accounts instead

Using Verbose Mode for Troubleshooting

Capture detailed installation logs for analysis:

# Run with verbose output and save to log file
.\Nodinite7-DEMO-Installation.ps1 -Verbose *>&1 | Tee-Object -FilePath "C:\Temp\Installation-Log.txt"

This captures all output (including verbose messages) to both console and log file for later analysis or sharing with Nodinite Support.

Previous Step

1. Planning Your Nodinite Solution - Infrastructure and licensing considerations

Next Step

3. Installation Guide - Choose your installation path (v7 or v6)

How to perform hardening
SQL Server Connection Strings
IIS Windows Features
MSDTC Transactions
Updating Nodinite v7
v6 Installation Guide - Legacy v6 installation instructions

Explore Nodinite for 30 days – completely free

See how Nodinite resolves your technical issues, in a

LIVE Demo!

Prerequisites for Installing Nodinite

Choose Your Version

New 7.x Nodinite v7 (Recommended)

Nodinite v6 (Legacy - No Longer Supported)

Comparison: v7 vs v6 Prerequisites

Common Prerequisites (Both Versions)

SQL Server Requirements

IIS (Internet Information Services)

Network and Security

Service Accounts and Permissions

Hardware Recommendations

Minimum Requirements (DEV/TEST Environments)

Recommended for Production

Detailed Prerequisite Verification

IIS Windows Features Verification

.NET Framework 4.8 Verification

.NET 9 Hosting Bundle Verification

SQL Server Verification

DacFX (SqlPackage.exe) Verification

MSDTC Verification

PowerShell 7 Verification

Troubleshooting Installation Issues

Script Execution Policy Errors

Database Connection Failures

IIS Application Pool Failures

Service Installation Failures

Using Verbose Mode for Troubleshooting

Previous Step

Next Step

Related Topics

...

^{New 7.x} Nodinite v7 (Recommended)