PI Nexus+ / Administration Guide
Troubleshooting Scans and Connections
This chapter helps you find why scans fail or fall behind, and where each kind of target's own problems are covered. Installation problems (installer, website, database connection, license) are in Installation Troubleshooting in the Installation Guide.
Overview
This chapter helps you find why scans fail or fall behind, and where each kind of target's own problems are covered. Installation problems (installer, website, database connection, license) are in Installation Troubleshooting in the Installation Guide.
Where to look first
Work through these in order: the Scanning page's Needs attention tab, the Targets tab (worst first, with separate Inventory and Health columns), the failed run opened from History, the logs (see Support and Diagnostics), and finally a support bundle, whose scan-automation.json shows why work did or did not run.
Note: Test on an Admin page runs as the web application's identity, while scans run as the scanner service's identity. A passing test proves only the first. If the two identities differ, give both the same PI and AF read access.
Scanning
| Symptom | Cause | Fix |
|---|---|---|
| Scanning Status reads Needs action with nothing failing | Automatic monitoring was never started, or is paused, and health is getting old | Start or resume it under Admin > Scan Automation |
| A target stays on awaiting inventory | Its first full scan has not succeeded | Open its last inventory run and fix the cause; no health refresh runs until the baseline succeeds |
| Health fails while inventory succeeds | A source or permission problem on the health path, or too many objects could not be resolved | Read the health run's failures; check read access to the PI Points behind AF attributes |
| A queued item never starts | Full verification waits for the heavy-work window | Wait for the window, or use Run now on the Queued tab |
| Freshness does not move after a scan | The scan was narrowed to some PI Point rules, or did not succeed | Run an unscoped scan |
| An enabled target is never scanned automatically | Automatic is cleared for it, or the license does not name the PI Data Archive | Tick Automatic under Admin > Scan Automation; install a license that names the archive |
| Test passes but the target's scans fail with access errors | Scans run as the scanner service identity, which lacks the read access the web application's identity has | Give both identities the same PI, AF and SQL read access |
Problems with one kind of target
Problems with one kind of target are in the troubleshooting table at the end of its chapter: PI Data Archives (including the Module Database and the runtime poll), AF Servers and Databases, OpenID Connect, PI Vision Instances, PI Adapter Monitoring and Host Monitoring.
