I agree, this is really strange. Especially since it seems to work with the other two systems. Have you tried a fourth system yet? To see if the problem is just this one machine? I did a search of our bug database, and didn't come up with any hits for that error number. I hate to say it, but you may need to rebuild that system. If the problem becomes more widespread- in that it shows up on other deployments, I would contact NI's Applications Engineers and talk to someone directly about the problem.