Step 8: Verify Functionality
Verify that Nodinite 7 works before you remove the v6 installation in Step 9. Until then, v6 is still on disk, which makes this the last cheap point to stop and investigate.
Prerequisites
- Step 7 completed – Monitoring Agents updated
- Access to the Web Client
Steps
Open the Web Client at
http://<server name>:<Web Client port>, using the port from the Portal Servers step.Sign in.
Note
If sign-in fails, users are prompted unexpectedly, or you see Kerberos or SSPI errors, check Service Principal Names (SPN) and Restoring Kerberos Transparent Login After v7 Upgrade before you change ports or reinstall services.
Verify that every Core Service web site runs: Web Client, Web API, Log API, Logging Service, Monitoring Service, and MCP Server. A stopped MCP Server is by design when you selected Keep the MCP Server stopped.
Check the Monitoring Agents status in the Web Client.
Review logs for errors or warnings:
- The Log Audits in the Web Client for upgrade-related events
- AI → Diagnostics for built-in health checks and component status
- Windows Event Viewer → Application and System logs for Nodinite errors
- IIS logs (default:
C:\inetpub\logs\LogFiles) for HTTP errors on each web site
Navigate the menus and open a Log View.
Note
Until you complete Step 12, expect errors from the Non-Events and Azure Logic Apps agents: they still call the old v6 URLs. Confirm in the error details that they reference the old URLs; Step 12 fixes them.
Completion Checklist
- Web Client reachable and working
- All Core Services running without errors
- Monitoring Agents listed with the correct status
- Log Audits show no critical errors
- AI Diagnostics health checks pass
- Windows Event Viewer shows no Nodinite errors
Troubleshooting
Web Client Not Accessible
The Web Client doesn't open in the browser. Check the following:
- The Web Client IIS application pool is started
- The firewall allows the Web Client port; see Network and Firewall Overview
- IIS logs and Event Viewer
- The .NET 10 Hosting Bundle is installed after the IIS Windows Features
Monitoring Agents Showing Error Status
Agents show an error or offline status. Check the following:
- The agents' IIS application pools are running
- The agent ports in the agent configuration
- The agent logs in the Web Client
- Restart IIS if needed