You're right. I would post to the Xilinx forums since I did another search and this error comes up in multiple versions of Xilinx. And in almost every case, corrective action was filed on Xilinx's part, so this definitely seems to be a Xilinx error rather than that of LabVIEW.
