Troubleshooting > Identifying Windows Filesystem Access Errors
   
Version 9.1
Identifying Windows Filesystem Access Errors
While profiling the Windows master file table and filesystems, a number of error messages may appear in the MFT.Aptare_File_Inventory.log file. These errors actually may require no follow-up actions. Typically, the errors are legitimate, such as a file being locked for exclusive use. Therefore, some files in the C:\Windows\System32 directory will not be profiled.
Example of a Log Error Message:
Unable To Access File C:\Windows\System32\Boot. Error 2. Skipping!!!
 
The following table lists System Errors with descriptions.
System Error
Description
2
System cannot find the file specified; This error occurs when accessing certain files in: C:\Windows\System32. On a Windows 64-bit OS, access is redirected by the filesystem to a 64-bit directory where the files in question do not exist.
3
System cannot find the path specified; This system error occurs when accessing certain files in: C:\Windows\System32. On a Windows 64-bit OS, access is redirected by the filesystem to a 64-bit directory where the files in question do not exist.
5
Access Denied; The file is accessible only to SYSTEM; for example, C:\Windows\System32\LogFiles\WMI\RtBackup
32
Another process has the file opened in exclusive mode; for example, database files used by the SQL server