Hi Kevin. I don't know what causes the problem, but I have seen it on our systems as well.
Our solution was to have our application stop and then start the variable engine every time
it launches. Stopping might not be ok for you depending on how your applications are
architected, but for us it is fine.
We use two System Exec.vi calls, with the following strings:
net stop "national instruments variable engine"
net start "national instruments variable engine"
Haven't had any instances of the application coming up w/o the variable engine since
we added this initialization step.
Matt