I have an implemented design open in the Vivado Device window. I select a path in the Timing window which also selects the path in the Device window.
If the selected path is contained within a PBLOCK (for example, pblock_1) and that PBLOCK is deleted from the Physical Constraint window (or I use the "delete_pbock pblock_1" Tcl command), I see errors similar to the following:
The Timing results table is not being correctly refreshed after the pblock is deleted and the stale data results in the exception.
This issue has been fixed in Vivado 2016.3.