Sign in to follow this  
jcdeas

"service Encounters A Problem" Updating Def. File

Recommended Posts

Error report for Ad-Aware 2007 Free: I have encountered the same error two weeks running when updating the definition file. After the "Update complete!" message, I get:

 

"Ad-aware 2007 service has encountered a problem and needs to close"

 

A button on that message provided more details as follows:

 

"Event type: BEX P1: aawservice.exe P2: 7.0.1.6 P3: 46a0b6dc

P4: aawservice.exe P5: 7.0.1.6 P6: 46a0b6dc P7: 00034f18

P8: c0000409 P9: 00000000"

 

Shortly afterwards came the "Error 6000 - closing gracefully" message. On restarting Ad-Aware, all seems to be well, and the status shows "Current version" as 0016.0000; however "Last update" has not been changed to today. The last three entries in the log file are:

 

"20070820 11-00-52 : Checking for updates.

20070820 11-00-57 : Checking for updates succeeded.

20070820 11-01-02 : Started downloading updates."

 

It seems that something goes wrong after the "update complete!" message, but before the log file entry to say that the update is complete, and before the "Last update" entry is changed.

 

My system is Windows XP SP2. Let me know if you need any more information.

 

Regards,

John Deas

Edited by JohnCD

Share this post


Link to post
Share on other sites

This continues to happen with every def. file update; I thought the recent new program versions might have fixed it, but it still happened with 7.0.2.2 this morning updating to def. file 0019. Immediately after the "Update complete" message comes "Ad-aware 2007 service has encountered a problem and needs to close". The details this time were:

 

EventType: BEX

P1: aawservice.exe

P2: 7.0.2.2

P3: 46d6a585

P4: aawservice.exe

P5: 7.0.2.2

P6: 46d6a585

P7: 000358c8

P8: c0000409

P9: 00000000

 

The good news is that the update seems to have happened OK, and scans run OK.

 

I am running Windows XP SP2 and Zonealarm firewall and AV. Let me know if I can give you any more information, or if there is anything I should try next week.

 

Regards,

John Deas

Share this post


Link to post
Share on other sites

Hello John,

 

The incorrect update information issue has been reported several times - the Devs are aware of it and are working on a fix (I updated to 0019.0000 when it came out on 3 Sept, but the date still shows as 22 August).

 

The main point is that the Defs are up-to-date and the scans are working for you :lol:

 

Regards,

 

Spike

Share this post


Link to post
Share on other sites
Sign in to follow this