Why Does the Update VI Calls Tool Prompt me to Convert the SupportFile.dlf Datalog File to the Current Format?Primary Software: Primary Software Version: 4.1 Primary Software Fixed Version: 2010 SP1 Secondary Software: N/A
Problem: I ran the Update VI Calls tool, from TestStand 4.1 or later, on a Windows XP machine and I was prompted to convert the SupportFile.dlf datalog file to the current format as shown in the screenshot below.
I also receive this dialog after running the tool when TestStand was launched as an administrator on Windows Vista and Windows 7 machines. Why am I receiving this prompt and how can I resolve the issue so I am no longer prompted? Solution: This issue is fixed in TestStand 2010 SP1 and later. This prompt will only be displayed on Windows XP machines, or Windows Vista and Windows 7 machines when TestStand is run as an administrator, if the Update VI Calls tool is run on a sequence file that contains a step configured to call a LabVIEW Express VI. Clicking the Cancel button will result in the Update VI Calls tool displaying the following status for LabVIEW Express VI steps: Status: Skipped. The configuration dialog timed out. Check for any popup dialogs in LabVIEW. You might have to close and relaunch LabVIEW. Clicking the Convert button will allow the Update VI Calls tool to resume and complete successfully. After you convert the datalog file once, you will no longer encounter this dialog. If the Update VI Calls tool is ever run on Windows Vista or Windows 7 machines when TestStand was launched as a non-administrator, steps configured to call certain LabVIEW Express VIs will result in the same status: Status: Skipped. The configuration dialog timed out. Check for any popup dialogs in LabVIEW. You might have to close and relaunch LabVIEW. To resolve both of the above mentioned issues, download the attached zip file and extract the contents to the <TestStand>\Components\Tools\UpdateVIs directory of all TestStand versions, between 4.1 and 2010, that are installed on your machine. Note: When prompted to replace the files that already exist in the <TestStand>\Components\Tools\UpdateVIs directory, choose to do so.
Related Links: KB 5JSBE5US: Why Does the Update VI Calls Tool Return the Status: Skipped. The configuration dialog timed out.? KB 4VODFC2I: How Can I Update All The VI Calls In A TestStand Sequence? Attachments:  UpdateVICalls_Fix.zip
Report Date: 03/28/2011 Last Updated: 08/01/2011 Document ID: 5JRE8GUS |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
