Error -307831 When Saving System Definition File in VeriStand System Explorer

Issue Details

I am experiencing an issue in VeriStand where the System Explorer throws an error if I try to save a large System Definition file twice in a short period. Despite the error, the System Definition still gets saved. The error message I see is shown below. What causes this error and how can be prevented?

Error -307831 occurred at System Explorer.lvlib:System Explorer Wrapper.vi.ProxyCaller >> System Explorer.lvlib:System Explorer Wrapper.vi >> System Explorer.lvlib:System Explorer.vi >> Gateway Watchdog.lvlib:Gateway Watchdog.vi >> System Explorer Framework.lvlib:Save.vi >> NIVSSDF_Filemanager.lvlib:Save NIVSSDF.vi >> NIVS_DataStorage.lvlib:SaveDataXMLFile.vi

 

Possible reason(s):

NI VeriStand: Unable to save file to the specified path. 

=========================

NI VeriStand: System.IO.IOException: The process cannot access the file '\System Definition File.nivssdf' because it is being used by another process.

Solution

The error -307831, "NI VeriStand: Unable to save file to the specified path" can be seen when saving a System Definition file in VeriStand System Explorer due to several reasons:

• File Size and Timeout: If the System Definition file is very large, the time it takes to access and save the file may exceed the allowed time for the operation, causing the error.
• File Access Conflicts: The error occurs when the file is being accessed by another process, such as another instance of System Explorer or synchronization software like OneDrive or Google Drive.
• File Permissions: If the file is set to read-only, the save operation will fail. In this scenario the error description is replaced by:

Possible reason(s):

NI VeriStand: Unable to save file to the specified path.

============================================

NI VeriStand: Destination file is read only.

To prevent this issue:

• Ensure that you are not trying to save the System Definition file simultaneously from multiple instances of System Explorer.
• Ensure no other applications are accessing the file during the save operation. For example, temporarily disable synchronization software like OneDrive or Google Drive while saving the System Definition file to prevent file access conflicts.
• Verify that the System Definition file is not set to read-only. In a Windows-based system this can be done by right-clicking the file, selecting “Properties,” and ensuring the “Read-only” attribute is unchecked.