Drake

CLI scanner crashes after update

Recommended Posts

Yesterday I runned update and CLI scanner binaries was updated to new version 5.1.0.3. After that each time I run scan with 5.1.0.3 it crashes. When I restore to 5.1.0.2 it works without problems.

Parameters:

a2cmd.exe /f=scanfolder /r /a /n /dq /log=!!Log.txt

EurekaLog 6.0.24

Application:

----------------------------------------------------------

1.1 Start Date : Tue, 5 Jul 2011 14:13:29 +0200

1.2 Name/Description: a2cmd.exe - (Command Line Scanner)

1.3 Version Number : 5.1.0.3

1.4 Parameters : .txt

1.5 Compilation Date: Wed, 29 Jun 2011 17:04:49 +0200

1.6 Up Time : 8 seconds

Exception:

---------------------------------------------------------------------

2.1 Date : Tue, 5 Jul 2011 14:13:37 +0200

2.2 Address : 7C812AF6

2.3 Module Name : kernel32.dll - (Windows NT BASE API Client DLL)

2.4 Module Version: 5.1.2600.5781

2.5 Type : EInOutError

2.6 Message : Unable to create directory.

2.7 ID : D903

2.8 Count : 1

2.9 Status : New

2.10 Note :

User:

-------------------------------------------------------

3.1 ID : Drake

3.2 Name : COMPUTER

3.3 Email : [email protected]

3.4 Company :

3.5 Privileges: SeChangeNotifyPrivilege - ON

SeSecurityPrivilege - OFF

SeBackupPrivilege - OFF

SeRestorePrivilege - OFF

SeSystemtimePrivilege - OFF

SeShutdownPrivilege - OFF

SeRemoteShutdownPrivilege - OFF

SeTakeOwnershipPrivilege - OFF

SeDebugPrivilege - OFF

SeSystemEnvironmentPrivilege - OFF

SeSystemProfilePrivilege - OFF

SeProfileSingleProcessPrivilege - OFF

SeIncreaseBasePriorityPrivilege - OFF

SeLoadDriverPrivilege - ON

SeCreatePagefilePrivilege - OFF

SeIncreaseQuotaPrivilege - OFF

SeUndockPrivilege - ON

SeManageVolumePrivilege - OFF

SeImpersonatePrivilege - ON

SeCreateGlobalPrivilege - ON

Active Controls:

------------------------------------------------

4.1 Form Class : ConsoleWindowClass

4.2 Form Text : C:\WINDOWS\system32\cmd.exe

4.3 Control Class:

4.4 Control Text :

Computer:

-----------------------------------------------------------------------------------------

5.1 Name : COMPUTER-EF98B6

5.2 Total Memory : 1535 Mb

5.3 Free Memory : 509 Mb

5.4 Total Disk : 37,16 Gb

5.5 Free Disk : 1,89 Gb

5.6 System Up Time: 7 hours, 34 minutes, 43 seconds

5.7 Processor : Intel® Pentium® 4 CPU 2.80GHz

5.8 Display Mode : 1024 x 768, 32 bit

5.9 Display DPI : 96

5.10 Video Card : NVIDIA GeForce4 MX 440 with AGP8X (driver 6.14.10.9371 - RAM 64 MB)

5.11 Printer :

Operating System:

------------------------------------

6.1 Type : Microsoft Windows XP

6.2 Build # : 2600

6.3 Update : Service Pack 3

6.4 Language: Serbian (Latin)

6.5 Charset : 204

Network:

---------------------------------------------------------------------

7.1 IP Address: 192.168.001.002 - 192.168.042.001 - 192.168.153.001

7.2 Submask : 255.255.255.000 - 255.255.255.000 - 255.255.255.000

7.3 Gateway : 192.168.001.001 - 000.000.000.000 - 000.000.000.000

7.4 DNS 1 : 192.168.001.001 - 000.000.000.000 - 000.000.000.000

7.5 DNS 2 : 000.000.000.000 - 000.000.000.000 - 000.000.000.000

7.6 DHCP : OFF - OFF - OFF

Any idea what is cause of the problem?

I'm using XP SP3 with KAV 12.0.0.374(a) and CFW 5.5 but I don't think they are problem.

Share this post


Link to post
Share on other sites

Hi Drake, welcome to the forum

I ran the latest CLS v 5.1.0.3 after reading your post using the set of parameters as in your example

There were no crashes. See images below. I had to post the screen output in 2 parts

thumb_1954143CLS_5-1-0_3_part__1.png

thumb_1206035CLS_5-1-0_3_part__2.png

The log file created attached as well.

All test suspects were perfectly deleted (scanned using full EAM afterwards)

The only small question is the strange output as highlighted in the “_part_#2” image … I've never seen that before. At the same time the log file does not contain such “mysterious” output string

I hope that developers can explain the meaning

My regards

p.s. Did you have a prompt for sending crash report to the developers with your e-mail & comments?

Usually you should have the said option. If so, it is better to send the report straight to Emsisoft team

Share this post


Link to post
Share on other sites

Thanks for the reply, Drake

Please try to set output for the log file explicitly as in my example (/log=F:\Log.txt)

It seems like I was able to reproduce the crash now when using "!!Log.txt" as you stated

getting the same

2.6 Message       : Unable to create directory.

Most likely that's a problem

When running my test I copied the parameters string as in your post,... but then edited the last bit automatically :)

My regards

Share this post


Link to post
Share on other sites

It generate error with:

a2cmd.exe /f=scanfolder /r /a /n /dq /log=Log.txt

However I noticed it doesn't crash when I exclude /log switch. I think I'm found what is a problem. New version doesn't consider a2cmd.exe folder as current directory for /log and /l switch or it is trying to create folder with name of file so when I run scan with those parameters:

a2cmd.exe /f=scanfolder /r /a /n /dq /log="%CD%\!!Log.txt"

it works like charm.

Lynx, big thanks. :thumbs:

Regards.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.