Troubleshooting the "Returned 0 matches" error
Who is this article for?
Users troubleshooting the "search for file pattern '123.map.1.*' in Runtime/Data/DocumentFiles/1 returned 0 matches" issue.
Server access is needed to check the document files folder.
The error indicates that the expected server files are missing. This article outlines potential causes.
1. Accessing a review and downloading a document
This often occurs if the PR instance was moved between servers incorrectly. When moving, the application pool, backend service, database, and document files must be stopped and backed up simultaneously. If files are backed up but the PR instance remains active on the old server, new documents may be added there, causing mismatches when the database is moved later.
Similarly, if document files and database are copied to a new server, but the application still points to the old database, deleting a document can cause inconsistencies between old and new data.
Restoring a database backup without matching document files can also cause this issue.
Therefore, the database and document files must always be kept coordinated.
Additionally, security software might quarantine or delete document files, causing this error.
If files are missing and cannot be restored, the documents may become inaccessible in PR.
2. Comparing a review
All the above reasons may apply. If the issue concerns only the comparison document, removing and re-adding the comparison should be fixed. Otherwise, contact Support for help.
3. Returned more than one match
This error usually indicates a server move where the database and document files were uncoordinated. For example, a document added after the database backup may cause duplicate files if a different file format is used.
The safest solution is to delete the problematic document and start again. If data recovery is needed, consult Support for guidance.