From eScan Wiki
(Difference between revisions)
Revision as of 12:13, 24 July 2009 WikiSysop (Talk | contribs) ← Previous diff |
Revision as of 12:14, 24 July 2009 WikiSysop (Talk | contribs) Next diff → |
||
Line 37: | Line 37: | ||
!!FileCount= 0 before Scn of C:\WINDOWS\System32\smss.exe... | !!FileCount= 0 before Scn of C:\WINDOWS\System32\smss.exe... | ||
+ | |||
01 Jul 2009 17:12:35 - !!WSF: Point1 | 01 Jul 2009 17:12:35 - !!WSF: Point1 | ||
+ | |||
01 Jul 2009 17:12:35 - !!WSF: Point2 | 01 Jul 2009 17:12:35 - !!WSF: Point2 | ||
+ | |||
01 Jul 2009 17:12:35 - !!WSF: Point3 | 01 Jul 2009 17:12:35 - !!WSF: Point3 | ||
+ | |||
01 Jul 2009 17:12:35 - !!WSF: Point4 (FDBSUCC) | 01 Jul 2009 17:12:35 - !!WSF: Point4 (FDBSUCC) | ||
Revision as of 12:14, 24 July 2009
|
General |
Knowledgebase |
Support |
On scanning with mwav...it stuck at a point where it said scanning Important System files.
Solution: Execute the mwav with /debug as a parameter.
mwav.exe /debug
in the end of the log you will find entries similiar to the ones below :
01 Jul 2009 17:12:35 - !!WSF: Point1
01 Jul 2009 17:12:35 - !!WSF: Point2
01 Jul 2009 17:12:35 - !!WSF: Point3
01 Jul 2009 17:12:35 - !!WSF: Point4 (FDBSUCC)
In such cases close mwav... Navigate to the following path :
C:\Documents and Settings\All Users\Application Data\MicroWorld\MWAV\MWAVDBX.MDB
rename the database mwavdbx.mdb and rescan again. The scan should work.
The problem arises due to corruption of the mentioned database.
Email us your feedback to solutions@mwti.net