Jump to content

EAM Show Eureka log


Recommended Posts

  • 4 weeks later...

same here on 2 servers (command line scanner)

 

Version       : 7.0.6.0
Date          : Wed, 29 Oct 2014 17:27:41 +0100
OS            : Microsoft Windows 2008 R2 (64 bit)
RAD           : BDS 7.0
Dump          : $8B $40 $08 $89 $45 $F8 $33 $C0 $5A $59 $59 $64 $89 $10 $68 $BB $2D $54 $00 $8B $45 $FC $E8 $F1 $DC $FF $FF $C3 $E9 $DF $37 $EC 
Section       : ExceptionHandlerHook
Descr         : 
 
Address       : $00542D98 - [00400000] a2cmd.exe -  -  -  - 0[0]
Module        : a2cmd.exe
Exception     : EAccessViolation
Message       : Access violation at address 00542D98 in module 'a2cmd.exe'. Read of address 414C4F51
Call Stack    : 00 $00542D98 - [00400000] a2cmd.exe 
                01 $00542D98 - [00400000] a2cmd.exe 
 
 
LastAddr      : 
LastModule    : 
LastException : 
LastMessage   : 
Call Stack    : 
 
ActiveObj     : (Non-Delphi exception) External exception C0000005 00000008 00000000
ActiveAddr    : $00000000 - [00000000] a2cmd.exe -  -  -  - 0[0]
Link to comment
Share on other sites

  • 3 weeks later...

Thank you for the log. Can you please check the update logs if an update happened to take place around that time? If it did, can you please give me a list of all components that were updated?

 

General Information:

Update started: 20-Nop-14 3:04:31
Update ended: 20-Nop-14 3:05:11
Time elapsed: 0:00:40

Update successful

Detailed Information:

31 modules, 5554131 bytes

Signatures\BD\emalware.053 (94997 bytes) - updated
Signatures\BD\jpeg.xmd (98885 bytes) - updated
Signatures\BD\e_spyw.i02 (438 bytes) - updated
Signatures\BD\update.txt (348 bytes) - updated
Signatures\BD\emalware.000 (385 bytes) - updated
a2framework.dll (367019 bytes) - updated
a2update.dll (658822 bytes) - updated
logging.dll (2013 bytes) - updated
resource.dll (2147 bytes) - updated
a2toast.dll (1248 bytes) - updated
a2start.exe (1507557 bytes) - updated
a2cmd.exe (436055 bytes) - updated
a2service.exe (831543 bytes) - updated
a2guard.exe (595788 bytes) - updated
a2wizard.exe (601969 bytes) - updated
a2hosts.dat (1261 bytes) - updated
fw32.dll (115114 bytes) - updated
fw64.dll (86723 bytes) - updated
fwhelper32.dll (1869 bytes) - updated
fwhelper64.dll (1868 bytes) - updated
fwndis.cat (1834 bytes) - updated
fwtdi32.sys (11789 bytes) - updated
fwtdi64.sys (12375 bytes) - updated
fwwfp32.sys (21116 bytes) - updated
fwwfp64.sys (22357 bytes) - updated
fwwfp732.sys (21133 bytes) - updated
fwwfp764.sys (22374 bytes) - updated
fwndis32.sys (10596 bytes) - updated
fwndis64.sys (11515 bytes) - updated
fwndisxp.sys (11382 bytes) - updated
fwndis_m.cat (1611 bytes) - updated

Link to comment
Share on other sites

Yes, it popped up because there was still one case of this error occurring left when replacing certain components via online update. That was fixed with today's update. Unfortunately we can't replace the component causing the error on update without an update, but it should be an isolated and one-time incident.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...