Step 4: Run PowerShell Script
Execute the migration script to update Nodinite Core Services to v7.
Prerequisites
- Step 3 completed – Binaries downloaded and extracted
- Pickup Service stopped and disabled
- PowerShell 7 installed with administrator privileges
- User is sysadmin on SQL Server instance
Steps
If applicable; Stop and disable the Nodinite Pickup Log Events Service:
- Open Services (
services.msc) - Find "Nodinite Pickup Log Events Service"
- Right-click → Stop
- Right-click → Properties → Startup type: Disabled
- Open Services (
Open PowerShell 7 as Administrator
Navigate to the extracted folder:
cd C:\Temp\Nodinite7-UpdateUnblock all files in the extracted folder:
dir -r | unblock-fileWindows marks files downloaded from the internet as potentially unsafe. This must be done before running any script from the package.
Run the Core Services script:
.\Core-services-Only.ps1If you used placeholder values in the Nodinite Portal, override them with parameters:
# Example with password as SecureString $pwd = ConvertTo-SecureString 'P@ssw0rd' -AsPlainText -Force .\Core-services-Only.ps1 -WebClientServiceAccountPassword $pwdWait for script completion
Verify Web Client is accessible:
http://localhost:40000(or your configured port)
Completion Checklist
- Pickup Service stopped and disabled
- Files unblocked with
dir -r | unblock-file - PowerShell script completed without errors
- Web Client accessible at configured URL
- Can log in to Web Client
- Database migrated successfully
Troubleshooting
"Execution policy" Error
Problem: PowerShell refuses to run script.
Solution:
Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process
"Access Denied" on Database
Problem: Script fails with SQL permission error.
Solution:
- Verify PowerShell 7 user is sysadmin on SQL Server instances (depending on your configuration, multiple instances may be used)
- Check SQL Server authentication mode (integrated vs mixed; integrated is required for Windows auth)
- Verify SQL Server service is running
Web Client Shows "500.21" Error
Problem: "Handler not recognized" error in browser.
Solution:
- Install latest .NET 10.0 Hosting Bundle
- Restart IIS:
iisreset /restart(administrator command prompt)