After running a report, some temp files may be left behind in the Temp folder

Article:TECH47346  |  Created: 2006-01-06  |  Updated: 2007-01-05  |  Article URL
Article Type
Technical Solution



After running a report, some temp files may be left behind in the Temp folder


This behavior can occur when a report fails to complete, and it can also happen when running reports from one Veritas Storage Exec (tm) server on another Storage Exec server.

When generating a report,  the general process is as follows:
  • The Storage Exec SEFileSvr.exe process will create a file with a prename of WQWFS_*.txt on the server where the data source resides that holds the information relative to the data in the report.
  • The WQWFS_*.txt will be copied to the server where the report is run.
  • The Storage Exec SERptSvr.exe process will create a file with the prename of WQDCOMFile_*.txt on the server where the report is run.
  • The WQDCOMFile_*.txt will be the copy of the WQWFS_*.txt file that originated on the server with the data source.
  • The WQDCOMFile_*.txt is then manipulated into the format of the report, renamed to the actual report name,  and finally, by default, placed in the \Program Files\VERITAS\Storage Exec\Reports directory for permanent storage.

The location of these temp files will be the environmentally set "temp" directory for the user account that Storage Exec services are configured to use. For more information on the Storage Exec service account, reference TechNotes 272976 and 281628 (links in the Related Documents section below). Storage Exec by default will delete these temporary files when it has completed processing each one. However, if two reports are scheduled at the same time, it is possible that the second process could modify the file name variable before the first one has been deleted and consequently orphan this first temporary file. Typically, if one of these temporary files is orphaned by the process,  it will be the WQWFS_*.txt file, but the same can also happen for the WQDCOMFile_*.txt files.

In such a situation, Storage Exec will not subsequently remove the orphaned file. Hence, in an environment where multiple reports are regularly scheduled to run at the same time, these orphaned files can build up and consume considerable disk space. If this disk space consumption is having a negative impact on a server utilized in Storage Exec reporting operations, then the orphaned files can be manually deleted.

Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.

There are no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. However, the issue is currently scheduled to be addressed in the next major revision of the product. Please be sure to refer back to this document periodically as any changes to the status of the defect will be reflected here.  Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests.  Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.

Please contact your Symantec Sales representative or the Symantec Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue.  For information on how to contact Symantec Sales, please see

Supplemental Materials

DescriptionReport temp files are left behind on remote servers.

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices