locked
.NET Runtime 2.0 Error Reporting RRS feed

  • General discussion

  • I started getting this error on my home built server just about every day since the 11/25 update. Before the update I never had this come up. This one occurred about one hour after a backup completed.

    Event Type: Error
    Event Source: .NET Runtime 2.0 Error Reporting
    Event Category: None
    Event ID: 1000
    Date:  11/29/2008
    Time:  01:36:33 AM
    User:  N/A
    Computer: HOME-SERVER
    Description:
    Faulting application homeserverconsole.exe, version 6.0.1800.0, stamp 48791358, faulting module homeserver.dll, version 6.0.1800.24, stamp 490b2087, debug? 0, fault address 0x0000c995.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 41 00 70 00 70 00 6c 00   A.p.p.l.
    0008: 69 00 63 00 61 00 74 00   i.c.a.t.
    0010: 69 00 6f 00 6e 00 20 00   i.o.n. .
    0018: 46 00 61 00 69 00 6c 00   F.a.i.l.
    0020: 75 00 72 00 65 00 20 00   u.r.e. .
    0028: 20 00 68 00 6f 00 6d 00    .h.o.m.
    0030: 65 00 73 00 65 00 72 00   e.s.e.r.
    0038: 76 00 65 00 72 00 63 00   v.e.r.c.
    0040: 6f 00 6e 00 73 00 6f 00   o.n.s.o.
    0048: 6c 00 65 00 2e 00 65 00   l.e...e.
    0050: 78 00 65 00 20 00 36 00   x.e. .6.
    0058: 2e 00 30 00 2e 00 31 00   ..0...1.
    0060: 38 00 30 00 30 00 2e 00   8.0.0...
    0068: 30 00 20 00 34 00 38 00   0. .4.8.
    0070: 37 00 39 00 31 00 33 00   7.9.1.3.
    0078: 35 00 38 00 20 00 69 00   5.8. .i.
    0080: 6e 00 20 00 68 00 6f 00   n. .h.o.
    0088: 6d 00 65 00 73 00 65 00   m.e.s.e.
    0090: 72 00 76 00 65 00 72 00   r.v.e.r.
    0098: 2e 00 64 00 6c 00 6c 00   ..d.l.l.
    00a0: 20 00 36 00 2e 00 30 00    .6...0.
    00a8: 2e 00 31 00 38 00 30 00   ..1.8.0.
    00b0: 30 00 2e 00 32 00 34 00   0...2.4.
    00b8: 20 00 34 00 39 00 30 00    .4.9.0.
    00c0: 62 00 32 00 30 00 38 00   b.2.0.8.
    00c8: 37 00 20 00 66 00 44 00   7. .f.D.
    00d0: 65 00 62 00 75 00 67 00   e.b.u.g.
    00d8: 20 00 30 00 20 00 61 00    .0. .a.
    00e0: 74 00 20 00 6f 00 66 00   t. .o.f.
    00e8: 66 00 73 00 65 00 74 00   f.s.e.t.
    00f0: 20 00 30 00 30 00 30 00    .0.0.0.
    00f8: 30 00 63 00 39 00 39 00   0.c.9.9.
    0100: 35 00 0d 00 0a 00         5..... 

    Sunday, November 30, 2008 1:51 AM

All replies

  • hi I have the exact same error. i have found out that if I log on to the server via console the error reproduce every day. but if I do not log on after the first error. the error is gone. but as soon I log on it comes back.   HELP please.
    Thursday, December 18, 2008 5:14 AM
  • Did you reboot your server? (Sometimes not all services are started properly after the first reboot following the upgrade installation.) Are there any applications on the server, which are not part of the basic configuration?

    Did you try to uninstall the November Update (KB957825, uninstall via Control Panel locally on the Home Server) and check, if the failure is still there?
    If not, does it remain fixed, if you install the patch again?

    Best greetings from Germany
    Olaf
    Thursday, December 18, 2008 8:09 AM
    Moderator
  • I do not have uninstalled the november update, but is far as i can remember the problem was there before the november update. I have tried to  restart the server, several times. and for the eventviewer, i get no errors at startup. it seems like the .net runime 2.0 error comes out of no where. I have a suspicion that the conector from my client machines is causing the error(I have a vista home premium 32 bit and a 64 bit), but have not found any conection betveen error and clientmachines. addins i have is avast antivirus and perfect disk 2008. it is a very annoying error, but it has nothing to say for the stability to the network shares.

    greetings from north of Norway

    Stig Erik:-)
    Saturday, December 20, 2008 6:51 AM
  • John, Vilmarken,

    Confirming. I have been tracking this error for some time hoping to define reproduction steps for it. I have also seen this error reported by other users. I do not think this has any relation to the november update. The first time I really noticed this error on one of my servers was around mid august (post_PP1?)

    Source: .NET Runtime 2.0 Error Reporting  
    TimeGenerated: 8/30/2008 9:49:17 AM  
    InstanceId: 1000  
    Catagory: (0)  
    CatagoryNumber: 0  
    EntryType: Error  
    Message: Faulting application homeserverconsole.exe, version 6.0.1800.0, stamp 48791358, faulting module homeserver.dll, version 6.0.1800.0, stamp 487913f4, debug? 0, fault address 0x00009825. 


    As far as I can tell this error seems harmless, so no reason to worry about this.

    I think maybe it occurs the first time the WHS console is started after a reboot of the server? Can any of you confirm this?  Could this be some one of the add-ins that causes the error on initialization?

    Hmmm...  maybe it is now time I pursue this in more detail and file a bug-report on connect..
    Theo.


    No home server like Home Server
    Saturday, December 20, 2008 8:37 PM
    Moderator
  • I seem to be getting the same error.  As has been said, it seems to be harmless.  I started noticing it when I'd be using the console and all the sudden it'd disconnect.  If I look in the event log it only disconnected at the exact moment that the error occured.  It's more of an annoyance than anything.
    Wednesday, December 24, 2008 11:53 PM