locked
The COM+ Event System detected an unexpected error RRS feed

  • Question

  • System: self built WHS box, two 500 Gb disks.
    Windows Home Server Console: 6.0.2030.0
    Windows Home Server Backup & Restore: 6.0.2030.0
    Windows Home Server Drive Extender: 6.0.2030.0
    Windows Home Server Remote Access: 6.0.2030.0
    Windows Home Server Storage Manager: 6.0.2030.0
    WHS with powerpack 2
    Steps taken: none, see below.

    Recently (I would say after the .net 3.5 SP 1 upgrade) I experienced the following problem. After logging in to WHS, when I try closing the WHS console to access the desktop or when accessing folders using Advanced Admin Console (just clicking on My Computer in the Advanced Admin Console triggers it) the remote connection is closed and most of the time the server freezes, requiring a hard reboot to start up again. Access to the share from clients works fine until the server freezes again.

    I know that accessing the server other than through the console is not supported, but I hope someone could give some pointers.

    The application event log shows the following error:

    Event Type: Error
    Event Source: EventSystem
    Event Category: (54)
    Event ID: 4613
    Date:  5/4/2009
    Time:  6:34:10 AM
    User:  N/A
    Computer: SERVER
    Description:
    The COM+ Event System detected an unexpected error from a Win32 API call at line 836 of d:\nt\com\complus\src\events\tier2\notify.cpp.  A call to CreateThread failed with error code 8: "Not enough storage is available to process this command. "  Please contact Microsoft Product Support Services to report this error.

    and then several of these:

    Event Type: Error
    Event Source: VSS
    Event Category: None
    Event ID: 8193
    Date:  5/4/2009
    Time:  6:34:10 AM
    User:  N/A
    Computer: SERVER
    Description:
    Volume Shadow Copy Service error: Unexpected error calling routine IEventSystem::Store.  hr = 0x80040206.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 2d 20 43 6f 64 65 3a 20   - Code:
    0008: 57 52 54 57 52 54 49 43   WRTWRTIC
    0010: 30 30 30 30 32 39 34 36   00002946
    0018: 2d 20 43 61 6c 6c 3a 20   - Call:
    0020: 57 52 54 57 52 54 49 43   WRTWRTIC
    0028: 30 30 30 30 32 37 35 31   00002751
    0030: 2d 20 50 49 44 3a 20 20   - PID: 
    0038: 30 30 30 32 33 37 38 30   00023780
    0040: 2d 20 54 49 44 3a 20 20   - TID: 
    0048: 30 30 30 31 36 32 31 36   00016216
    0050: 2d 20 43 4d 44 3a 20 20   - CMD: 
    0058: 43 3a 5c 57 49 4e 44 4f   C:\WINDO
    0060: 57 53 5c 53 79 73 74 65   WS\Syste
    0068: 6d 33 32 5c 76 73 73 76   m32\vssv
    0070: 63 2e 65 78 65 20 20 20   c.exe  
    0078: 2d 20 55 73 65 72 3a 20   - User:
    0080: 4e 54 20 41 55 54 48 4f   NT AUTHO
    0088: 52 49 54 59 5c 53 59 53   RITY\SYS
    0090: 54 45 4d 20 20 20 20 20   TEM    
    0098: 2d 20 53 69 64 3a 20 20   - Sid: 
    00a0: 53 2d 31 2d 35 2d 31 38   S-1-5-18

    and then lots and lots of other errors.

    The system log shows a number of errors, of which some are also DCOM related.


    I have a feeling that something went wrong during .net 3.5 SP1 installation, screwing up my system.

    I think that "rebuilding the COM+ catalog" as described here might be a solution.
    http://support.microsoft.com/default.aspx/kb/315296

    On the other hand,
    1. I am not sure if this is the problem
    2. I can't access folders/registry etc to do this
    3. I don't think it is appropriate to take these kind of steps on a WHS box
    4. Re-installing WHS might be easier.

    Does anyone know what this problem could be and how to possibly solve it without re-installing WHS? Thanks very much.



    Monday, May 4, 2009 8:54 PM

All replies

  • Personally I would start with running chkdsk on all partitions from a command prompt:

    chkdsk D: /f /r 
    chkdsk C:\fs\X /f /r where X is drive letter for mounted volume (find from windows explorer or from dir command from c:\fs in command shell)
    chkdsk C: /f /r

    If you have any third party drivers installed you don't really need (installed after basic WHS install, video chipset, sound) you could try uninstalling them.

    Also please check if you have sufficient (>5%) of free space on all partitions / mounted volumes)

    If this fails to solve the problem I would do a server reinstall. If the problem appears again after server reinstall I expect it's a hardware or driver issue. Concerning the latter, don't use third party drivers unless you really need them.
    Tuesday, May 5, 2009 9:10 AM
    Moderator
  • Thanks, much appreciated.

    I'm now running chkdsk.

    Where you say: "chkdsk C:\fs\X /f /r where X is drive letter for mounted volume", could it be correct that I have only one mounted volume with no drive letter but only the number 4? It appears that the command chkdsk c:\fs\4 /f /r is working.
    Tuesday, May 5, 2009 1:17 PM
  • Yep, it's letter, number or combination of letter and number.
    Tuesday, May 5, 2009 1:33 PM
    Moderator
  • it seems to be two seperate issues.

    1. the disk related problem (chkdsk found some errors, it now remains to be seen if this solves the issue of the errors in the even log)
    2. the version I used of advanced admin console is not compatible with Internet Explorer 8 (see comments @ http://www.whsplus.com/2009/04/07/advanced-admin-console/)

    thanks for the help, and I will check back if there is some remaining problem.
    Tuesday, May 5, 2009 5:39 PM
  • Problem #1 is not solved. The problem still exists that every day, from a certain random time, I continue finding errors in the log. Because a lot of those were VSS related, I stumbled upon this http://mswhs.com/2008/03/27/volume-shadow-services-vss-on-whs/ link.
    I have now turned VSS off for D:\ and will continue to monitor the event log...

    Wednesday, May 6, 2009 8:05 PM