Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Mar 1, 2023 6:21:59 AM
Mar 1, 2023 6:21:59 AM
A .qvw.Oldfile may be visible in the QlikView Source Documents folder after a task or reload failure.
Reviewing the task log of the failing task will show:
Access to the path '\\[servername]\Path to Source Documents\DashboardName.qvw.oldfile' is denied
This is caused by read or write access errors to the temporary .oldfile which is created during the reload and distribution process. If the file cannot be accessed, the task will fail, and the file cannot be deleted.
Address the possible root causes of the file access issues, such as:
Once you haver verified that the .oldfile is no longer locked, restart the failed task. QlikView will delete the file (see information in the Cause section for a detailed process).
Distributions and and Reloads follow this process:
Behaviors worth being aware of:
If after a reload failure, a SourceDocument.qvw.Oldfile and a SourceDocument.qvw exist, check the task log and most likely the result will be an "access denied" failure on the .qvvw.OldFile.
This is probably due to the .qvw.Oldfile being locked by the QDS or a scanning agent. If you are not successful renaming, moving or deleting the .qvw.Oldfile, given some type of "Access Denied" error, the QDS is locking the file. Ensure login to the server using the QlikView service account if trying to rename or remove the file. The service account owns that file and it cannot be removed by any other account in most cases.
You can test this by creating a .qvw.Oldfile using the administrator account and running a reload. The .qvw.Oldfile does not go away. If you login with the service account and create the .qvw.Oldfile and run a reload, the .qvw.Oldfile will be removed.
If you are able to remove, rename or delete the file, then it may have been a temporary lock by a scanning agent. Try rerunning the task. It should be successful once the .qvw.Oldfile is removed.
The .qvw.Oldfile could present itself if a reload is in process, and the qvb process in Task Manager is "killed". The QDS may not be able to properly "unlock" the .qvw.Oldfile if present when the qvb process is killed.
When everything is working as it should, the .qvw.Oldfile should be present for just a few moments when the .qvw.tmp is being created. Once the .qvw.tmp is fully written and verified, the name change to the SourceDocument.qvw is done, and the .qvw.Oldfile is removed.