Hello TimA2011,
It appears that you have found a work around for this issue but I would like to confirm that you have only had to revert to the default MAX configuration once to solve this issue (and not something that has to be done each time you use this VI). If so, then as is explained in the Knowledge Base Article that Izzy included, this may have been caused by corruption within MAX. If this is a step that has to be done repeatedly, then I would expect something else is causing this issue such as a service not being started or possibly anti-virus software. I'd simply like to get confirmation in order to provide others with a solution as to how to fix this issue long-term.
Wes W
Application Engineering
National Instruments
www.ni.com/support
