- 0 minutes to read

Step 4: Run PowerShell Script

Execute the migration script to update Nodinite Core Services to v7.

Prerequisites

Steps

  1. 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

  2. Open PowerShell 7 as Administrator:

    • Start Menu → Search "PowerShell 7" → Right-click → Run as administrator

  3. Navigate to the extracted folder:

    cd C:\Temp\Nodinite7-Update

  4. Unblock all files in the extracted folder:

    dir -r | unblock-file

    Windows marks files downloaded from the internet as potentially unsafe. This must be done before running any script from the package.

  5. Run the Core Services script:

    .\Core-services-Only.ps1

  6. If you used placeholder values in the Nodinite Portal, override them with parameters:

    # If all service accounts share the same password
$pwd = ConvertTo-SecureString 'P@ssw0rd' -AsPlainText -Force
.\Core-services-Only.ps1 `
    -WebClientServiceAccountPassword        $pwd `
    -WebApiServiceAccountPassword           $pwd `
    -LogApiServiceAccountPassword           $pwd `
    -LoggingServiceServiceAccountPassword   $pwd `
    -MonitoringServiceServiceAccountPassword $pwd

    # If each service account has a different password
$pwdWebClient   = ConvertTo-SecureString 'WebClientP@ss'   -AsPlainText -Force
$pwdWebApi      = ConvertTo-SecureString 'WebApiP@ss'      -AsPlainText -Force
$pwdLogApi      = ConvertTo-SecureString 'LogApiP@ss'      -AsPlainText -Force
$pwdLogging     = ConvertTo-SecureString 'LoggingP@ss'     -AsPlainText -Force
$pwdMonitoring  = ConvertTo-SecureString 'MonitoringP@ss'  -AsPlainText -Force
.\Core-services-Only.ps1 `
    -WebClientServiceAccountPassword         $pwdWebClient  `
    -WebApiServiceAccountPassword            $pwdWebApi     `
    -LogApiServiceAccountPassword            $pwdLogApi     `
    -LoggingServiceServiceAccountPassword    $pwdLogging    `
    -MonitoringServiceServiceAccountPassword $pwdMonitoring

  7. Wait for script completion. If this takes more than a few minutes, click the prompt and press the Enter key, you may have blocked the console and as such interrupting the proces.

  8. 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)

Next Step