Dirscan Probe unable to generate MD5 hash

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

The dirscan probe isn't able to generate the MD5 hash for some files.  The following is seen in the logs for these files :

Aug 31 09:45:13:984 [9268] dirscan: * File and directory checking probe 3.19
Aug 31 09:45:13:984 [9268] dirscan: * Nimsoft Corporation
Aug 31 09:45:16:062 [9268] dirscan: port=48008 PID=14468
Aug 31 09:47:32:562 [9268] dirscan: GenMD5 - Cannot open input file C:\Windows\System32\config\SYSTEM
Aug 31 09:47:32:562 [9268] dirscan: _dispatch: callback 'gen_MD5' return non-zero value 1
Aug 31 09:47:32:765 [9268] dirscan: GenMD5 - Cannot open input file C:\Windows\System32\config\RegBack\SYSTEM
Aug 31 09:47:32:765 [9268] dirscan: _dispatch: callback 'gen_MD5' return non-zero value 1
Aug 31 09:47:32:874 [9268] dirscan: GenMD5 - Cannot open input file C:\Windows\System32\config\SAM
Aug 31 09:47:32:874 [9268] dirscan: _dispatch: callback 'gen_MD5' return non-zero value 1
Aug 31 09:47:32:984 [9268] dirscan: GenMD5 - Cannot open input file C:\Windows\System32\config\RegBack\SAM
Aug 31 09:47:32:984 [9268] dirscan: _dispatch: callback 'gen_MD5' return non-zero value 1
Aug 31 09:47:33:109 [9268] dirscan: GenMD5 - Cannot open input file C:\temp\nimbus.txt
Aug 31 09:47:33:109 [9268] dirscan: _dispatch: callback 'gen_MD5' return non-zero value 1
Aug 31 09:47:33:218 [9268] dirscan: ReadCfg - profile (important_system_files)file_0001, no MD5 signature specified for file C:\Windows\System32\config\SYSTEM, generating one
Aug 31 09:47:33:218 [9268] dirscan: GenMD5 - Cannot open input file C:\Windows\System32\config\SYSTEM
Aug 31 09:47:33:218 [9268] dirscan: ReadCfg - profile (important_system_files)file_0003, no MD5 signature specified for file C:\Windows\System32\config\RegBack\SYSTEM, generating one
Aug 31 09:47:33:218 [9268] dirscan: GenMD5 - Cannot open input file C:\Windows\System32\config\RegBack\SYSTEM
Aug 31 09:47:33:218 [9268] dirscan: ReadCfg - profile (important_system_files)file_0004, no MD5 signature specified for file C:\Windows\System32\config\SAM, generating one
Aug 31 09:47:33:218 [9268] dirscan: GenMD5 - Cannot open input file C:\Windows\System32\config\SAM
Aug 31 09:47:33:218 [9268] dirscan: ReadCfg - profile (important_system_files)file_0005, no MD5 signature specified for file C:\Windows\System32\config\RegBack\SAM, generating one
Aug 31 09:47:33:218 [9268] dirscan: GenMD5 - Cannot open input file C:\Windows\System32\config\RegBack\SAM
Aug 31 09:47:34:327 [9668] dirscan: GenMD5 - Cannot open input file C:\Windows\System32\config\SYSTEM
Aug 31 09:47:38:374 [17092] dirscan: GenMD5 - Cannot open input file C:\Windows\System32\config\RegBack\SYSTEM
Aug 31 09:47:40:374 [9608] dirscan: GenMD5 - Cannot open input file C:\Windows\System32\config\SAM

Environment

• Release: 20.4
• dirscan v3.19

Cause

These files are being used by another process preventing the MD5 hash from being created.  

Resolution

If the lock cannot be broken, the hash will not be able to be generated and the file will not be able to be monitored by the dirscan probe.

Given this fact, locked system files are not able to be monitored by the probe.