It looks like perhaps he has mixed-mode libraries on the machine or has something cross linked in the NI library tree OR the reportlib is fubar. .
Try using the development Labview engine and open the VI's giving you trouble from the TARGET directory ( SupportVIs directory) and see if the VI hierarchy is coming from the location you expect. If you can open the "offending" VI you should be able to chase down where the VI tree is messed up.
So open C:\__views\calTest_jvh\mastrv\Deployments\MASTRV-CalAndTest\target\SupportVIs\NI_report.lvclass with Labview and look at the FULL VI tree to see what is called out and missing.
Also open the Dialogs\Dialogs.lvlib lib in the TARGET path and see what that calls.
Post the deploy log too.
