Troubleshooting Common PI Vision Errors: A Guide for Users

PI Vision problems can originate in the browser, PI Vision server, AF, Data Archive, security configuration, or the underlying data source.

A structured troubleshooting sequence helps users and administrators isolate the correct layer.

Display does not load

First determine whether the problem affects one user, one display, or the complete PI Vision environment.

Check:

• Browser and network access

• PI Vision service availability

• Authentication

• Whether other displays load

• Whether the problem occurs for another user

This separates a local client issue from a server-wide issue.

Value shows no data or an error

Identify the data source used by the symbol.

If it is a PI Point, check the point directly. If it is an AF attribute, verify the AF data reference and source tag.

Also review permissions and current data state.

Value is stale

Compare the displayed timestamp with the expected update interval.

Then check the source PI Point, interface or connector, and any analysis that writes the value.

A stale display value can be a source-data problem rather than a PI Vision problem.

Display shows the wrong value

Verify that the symbol references the intended tag or AF attribute.

After migrations and AF changes, old server or asset references can remain in displays.

Trends have gaps

Check the PI Point history for the same time range.

If the archive contains the gap, investigate collection and source behavior. If the history is complete, review display configuration, time range, permissions, and calculation dependencies.

Calculated value is wrong

Trace the display to the analysis output and then review analysis inputs, status, and logic.

Do not edit the display to hide a calculation problem.

Permission errors

Confirm that the user has appropriate access to PI Vision and the underlying PI or AF data.

Use approved security changes. Do not give broad access only to make the error disappear.

Capture evidence before escalation

Record:

• Display name

• User

• Time of failure

• Affected symbol or value

• Screenshot when useful

• Source tag or AF path when known

• Whether the problem affects other users

This information helps the PI administrator reproduce the issue.

The practical objective

Troubleshoot from the visible symptom back to the source. Separate browser, PI Vision, AF, analysis, Data Archive, and source-system problems before changing configuration.