New ESET server keeps crashing

Discussion in 'Other ESET Home Products' started by Geosoft, Jul 29, 2010.

Thread Status:
Not open for further replies.
  1. Geosoft

    Geosoft Registered Member

    Joined:
    Jan 7, 2009
    Posts:
    270
    Location:
    Toronto, Ontario, Canada
    Just downloaded the 4.0.136 server and it keeps crashing every 10 minutes:

    Event Type: Error
    Event Source: Application Error
    Event Category: (100)
    Event ID: 1000
    Date: 7/29/2010
    Time: 11:55:03 AM
    User: N/A
    Computer: GUARDIAN
    Description:
    Faulting application era.exe, version 4.0.136.0, faulting module era.exe, version 4.0.136.0, fault address 0x0008523d.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 41 70 70 6c 69 63 61 74 Applicat
    0008: 69 6f 6e 20 46 61 69 6c ion Fail
    0010: 75 72 65 20 20 65 72 61 ure era
    0018: 2e 65 78 65 20 34 2e 30 .exe 4.0
    0020: 2e 31 33 36 2e 30 20 69 .136.0 i
    0028: 6e 20 65 72 61 2e 65 78 n era.ex
    0030: 65 20 34 2e 30 2e 31 33 e 4.0.13
    0038: 36 2e 30 20 61 74 20 6f 6.0 at o
    0040: 66 66 73 65 74 20 30 30 ffset 00
    0048: 30 38 35 32 33 64 08523d
     
  2. Geosoft

    Geosoft Registered Member

    Joined:
    Jan 7, 2009
    Posts:
    270
    Location:
    Toronto, Ontario, Canada
    Error message that's probably relational:

    Event Type: Error
    Event Source: Application Error
    Event Category: None
    Event ID: 1001
    Date: 7/29/2010
    Time: 12:34:10 PM
    User: N/A
    Computer: GUARDIAN
    Description:
    Fault bucket 1974945245.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 42 75 63 6b 65 74 3a 20 Bucket:
    0008: 31 39 37 34 39 34 35 32 19749452
    0010: 34 35 0d 0a 45..
     
  3. Geosoft

    Geosoft Registered Member

    Joined:
    Jan 7, 2009
    Posts:
    270
    Location:
    Toronto, Ontario, Canada
    Info from the logs before the server restarts:

    [2010-07-29 12:46:13.703] V2 [4c51b04700bd] [0000136c] <SESSION_ERROR> ReplicationProcessRequest: R2S_GENERATE_MERGED_POLICY: failed, pid=417, ps=Guardian, code 12 (connection 'Gel-store')
    [2010-07-29 12:46:16.469] V2 [4c51b04800be] [0000141c] <SESSION_ERROR> ReplicationProcessRequest: R2S_GENERATE_MERGED_POLICY: failed, pid=417, ps=Guardian, code 12 (connection 'Gll-store')
    [2010-07-29 12:46:25.218] V1 [000000000000] [00000ac4] <INTERNAL_ERROR> ProcessDeledDbData failed, code 32
    [2010-07-29 12:46:46.984] V1 [000000000000] [0000140c] <INTERNAL_ERROR> ProcessDeledDbData failed, code 32
     
  4. jeramy_t

    jeramy_t Registered Member

    Joined:
    Aug 12, 2009
    Posts:
    22
    what version did you upgrade from?
     
  5. Black_Roze

    Black_Roze Registered Member

    Joined:
    Apr 23, 2010
    Posts:
    18
    any body there to answer this problem ?
     
  6. jeramy_t

    jeramy_t Registered Member

    Joined:
    Aug 12, 2009
    Posts:
    22
    from my experience and what other users have reported is if you upgraded from version 3 to version 4, uninstall everything, delete everything and start over. the upgrade process is broken.
     
  7. jimwillsher

    jimwillsher Registered Member

    Joined:
    Mar 4, 2009
    Posts:
    668
    Is that a generalisation? I've upgraded seven servers from v3 to v4, and the only one that caused problems was Win2008. All the 2003 (SBS and standard) upgraded flawlessly.


    Jim
     
  8. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    When an application crashes, be it era.exe or another one, run "procdump -ma %PROCESS%" with the crash message on the screen to generate a dump of the process. Then convey the dump to ESET for perusal or PM me a link to the dump.
     
  9. Echofig

    Echofig Registered Member

    Joined:
    Jun 17, 2009
    Posts:
    10
    I am also having problems with ERA crashing every 10 minutes. I upgraded from v4.0.136 to v4.0.138. I have submitted a support ticket but this in not an acceptable solution. Reply from the ticket follows.

    Hello,

    Did you have these issues with v4.0.136?

    The upgrade only addressed theses issues.

    * Fixed minor problem with re-installation from ERA 3 to ERA 4
    * Number of fixes related to localization

    If you weren't trying to resolve one of those issues please reinstall v4.0.136 you gain nothing by upgrading. If that is that case please uninstall v4.0.138 and reinstall v4.0.136 and let us know if the issue is resolved.

    If it continues then it's an issue with the Just-In-Time debugger.

    Please advise if you have found a solution.
     
  10. Echofig

    Echofig Registered Member

    Joined:
    Jun 17, 2009
    Posts:
    10
    I started looking for something that was set on a ten minute time line and found Notification under Advanced Server Settings. So I opened up Notification Manager and all the rules had red X in them. I clicked on one rule and then went to click another when it said I changed a rules setting do I want to save? I said yes, repeated with all the rules and no more errors in event viewer. After I saved all the rules I found these errors in the era.log file.

    2010-10-25 15:31:00.011] V1 [4cc5e9040105] [000060f8] <NOTIFICATION_ERROR> Illegal nPRMCVirusSignatureDBVersion value! (1681982615) (More than 10% of primary clients with critical protection status)
    [2010-10-25 15:31:00.026] V1 [4cc5e9040105] [000060f8] <NOTIFICATION_ERROR> Illegal nPRMCVirusSignatureDBVersion value! (1681982615) (Primary clients waiting for restart)
    [2010-10-25 15:31:00.042] V1 [4cc5e9040105] [000060f8] <NOTIFICATION_ERROR> Illegal nPRMCVirusSignatureDBVersion value! (1681982615) (Primary clients with a non-cleaned infiltration in computer scan)
    [2010-10-25 15:46:00.020] V1 [4cc5ec880178] [000060f8] <NOTIFICATION_ERROR> Illegal nPRMCVirusSignatureDBVersion value! (1681982615) (More than 10% of primary clients with critical protection status)
    [2010-10-25 15:46:00.036] V1 [4cc5ec880177] [000060f8] <EXCEPTION_ERROR> Exception in SchedulerThread, Code: 0xc0000005 (Access Violation), LastError: 126. If this error hppens more often you can temporary turn on debug logging and send the logs to ESET support for more information.
     
Thread Status:
Not open for further replies.