TN - AppSrv260324001 DB Dump Failure in AVEVA IDE 2017 Update 3

Document Author: Mataia Lewis

Product: AVEVA System Platform (Application Server)
Version: 2017 Update 3
Date: May 13, 2025
Keywords: DB Dump, OLE_E_NOSTORAGE, tmp file lock, COMException, Validate, Rebuild, Check-In, File in Use, Storage Error

Issue Summary 

Issue Summary

A customer reported a failure when performing a DB dump of selected objects in AVEVA IDE 2017 Update 3. The dump process failed with the following two errors:

Error 1: COMException - OLE_E_NOSTORAGE

This error indicates that one or more objects selected for export have not been assigned persistent storage in the Galaxy repository. This can happen if:

The object has never been saved or validated.

The object is corrupt or referencing missing components.

The object metadata hasn't been fully committed to the repository.

Error 2: File Lock on Temporary Dump File

This error suggests that the dump process is being blocked due to file access conflicts — either by a background application (e.g., antivirus) or a second IDE process using the same temp file.

Resolution Steps

To resolve both errors, follow the structured procedure below:

Step 1: Run AVEVA IDE as Administrator

Before proceeding with any operations:

Close all running IDE instances.

Right-click the IDE shortcut and select “Run as Administrator.”
This ensures proper permissions for file access and repository interaction.

Step 2: Recompile (Rebuild) and Validate the Object

This process forces the object to generate its required internal storage, helping eliminate the OLE_E_NOSTORAGE error.

A. Locate and Check Out the Object

In the Template Toolbox or Deployment View, right-click the affected object.

Select “Check Out.”

B. Open the Object and Trigger a Save

Double-click to open the object.

Make a minor edit (e.g., add and remove a space in a comment field).

Click Save, then Close the object.

C. Check In and Validate

Right-click the object again and select “Check In.”

While checked in, right-click again and choose “Validate.”

Note: In AVEVA IDE 2017 U3, the Validate option is only available when the object is checked in.

If validation is successful, the object now has assigned storage and is eligible for DB dump.

D. Repeat for All Affected Objects

Apply this process to each object that failed during the export.

 Step 3: Eliminate File Lock Issues

To resolve temp file access issues:

Ensure only one instance of the IDE is running.

Temporarily disable antivirus or add an exclusion for:

Manually clear the temp folder if needed (only when IDE is closed).

Restart the machine if locks persist and retry the dump operation immediately after reboot, before launching other applications.

Optional: Run Galaxy Repository Utility

If object integrity is still in question:

Run aaGRUtility.exe from:

Perform a GR Check/Repair on the Galaxy.

Conclusion

The errors observed during the DB dump process were caused by:

Objects missing repository storage due to skipped save/validate steps.

File lock conflicts in the temporary export directory.

By recompiling and validating each object while ensuring administrative access and exclusive file use, the DB dump process can proceed without issue.

If problems persist after following the above procedure, contact AVEVA Technical Support with:

The affected object names

Dump/export logs

A Galaxy backup for further review