Hi,
The first thing I would check is to see the versions of NI-VISA on each machine. I have seen errors like this before when moving to a newer version of the driver. In that case, the newer version of NI-VISA detected an error dealing with the parity that the previous driver did not pay attention to. Because it was not a problem for that specific application, and because the parity was being changed on the fly, it only happened sometimes and the problem was solved by simply ignoring the error. It could be something similar since you are upgrading versions of TestStand.
This specific error can also be caused by using the incorrect resource name, so check to ensure that this is not the case, and that you can communicate with the resource through Measurement and Automation Explorer. Once you ensure that the device can be communicated with through MAX on the new computer, then we can figure out why it won't work in the TestStand program.
John M
Applications Engineer