When running a Velocity Report, I receive a message that says "The listed Archive files could not be found"
- Hadden Grant
When running a Velocity report, the system will attempt to attach archive files to SQL. Once attached, they will pull the data out of the archive to process the report requested.
If the archive files can’t be found, or if the system doesn’t think the files exist, it will generate the below message indicating the archive files can’t be found.
- 1 Make sure the archive files listed in the error exist in the correct location in SQL
- 2 Check to make sure the windows account used to start the Velocity services has full permissions to both the *.mdf and *.ldf archive files.
- 3 Check to make sure the DB owner for the Velocity database and Master database are the same
- 4 Check to make sure the Trustworthy setting in the Velocity database properties is set to True
- 5 Check to make sure the “Enable CLR Integration” is checked within the SQL Servers “Surface Area Configuration for Features”
- 6 Check to make sure the kekUDP SQL Assemblies has its permission set to External Access.
To resolve this issue, follow the steps below:
Make sure the archive files listed in the error exist in the correct location in SQL
Log into Velocity SQL, select Databases, Velocity, Tables, locate dbo.ArchiveFiles, open Top 200 Rows, compare the data in ArchiveFiles to the error recieved
Check to make sure the windows account used to start the Velocity services has full permissions to both the *.mdf and *.ldf archive files.
Check to make sure the DB owner for the Velocity database and Master database are the same
Right click on the Velocity Database, select Properties, select Files
Open System Databases, right click Master, select Properties, then Files
Check to make sure the Trustworthy setting in the Velocity database properties is set to True
Right click on the Velocity Database, select Properties, select Options
Check to make sure the “Enable CLR Integration” is checked within the SQL Servers “Surface Area Configuration for Features”
C:\Windows\SysWOW64\SQLServerManager15.msc to find SQL Server Configuration Manager
Open Surface Area Configuration for Features, and check Enable CLR integration
Check to make sure the kekUDP SQL Assemblies has its permission set to External Access.
Open the Velocity Database, select Programmability, Assemblies, then choose kekUDP
If the problem persists, make sure the archives can be attached manually to SQL to validate the process can work outside of Velocity. If the problem continues, please call Tech Support.