locked
WHS: HomeServerConsole craches due to OperatingSystemName key missing??? RRS feed

  • Question

  • It seems to be an old error as I found something similar here. http://social.microsoft.com/Forums/en-US/whspowerpack3beta/thread/f5f02b58-9640-4323-ba20-e22e966d51db

    I also found this http://social.microsoft.com/Forums/en-US/whssoftware/thread/baf8a725-a69f-495f-8626-6f220c092b9e (But reinstalling .NET 2.0 with all updates???) Any pointers where to begin?

    Its a HP MediSmart Ex470 working fine for years.. Today as I went in - Poff

    In the beginning of my HomeServerConsole.<datetime>.log i find this

     

    [1]100924.195228.5156: Error: OperatingSystemName key does not exist. This is expected during PP1 to PP2 upgrade. System.IO.IOException: The specified registry key does not exist.

       at Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str)

       at Microsoft.Win32.RegistryKey.GetValueKind(String name)

       at Microsoft.HomeServer.Transport.PartnerInfo.GetValue(String key, RegistryValueKind kind, String path)

       at Microsoft.HomeServer.Transport.PartnerInfo.GetPartnerValue(String key, RegistryValueKind kind)

       at Microsoft.HomeServer.Transport.PartnerInfo.StringValue(String key)

       at Microsoft.HomeServer.Transport.PartnerInfo.get_OSVersion()

     

    I also see this in the APP Eventlog.

     

    Event Type: Error
    Event Source: .NET Runtime 2.0 Error Reporting
    Event Category: None
    Event ID: 5000
    Date: 2010-09-24
    Time: 20:28:52
    User: N/A
    Computer: WHS
    Description:

    EventType clr20r3, P1 homeserverconsole.exe, P2 6.0.0.0, P3 4acceb5f, P4 whscommon, P5 6.0.0.0, P6 4accead8, P7 334, P8 1b, P9 system.invalidoperationexception, P10 NIL.

     

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Data:

    0000: 63 00 6c 00 72 00 32 00   c.l.r.2.

    0008: 30 00 72 00 33 00 2c 00   0.r.3.,.

    0010: 20 00 68 00 6f 00 6d 00    .h.o.m.

    0018: 65 00 73 00 65 00 72 00   e.s.e.r.

    0020: 76 00 65 00 72 00 63 00   v.e.r.c.

    0028: 6f 00 6e 00 73 00 6f 00   o.n.s.o.

    0030: 6c 00 65 00 2e 00 65 00   l.e...e.

    0038: 78 00 65 00 2c 00 20 00   x.e.,. .

    0040: 36 00 2e 00 30 00 2e 00   6...0...

    0048: 30 00 2e 00 30 00 2c 00   0...0.,.

    0050: 20 00 34 00 61 00 63 00    .4.a.c.

    0058: 63 00 65 00 62 00 35 00   c.e.b.5.

    0060: 66 00 2c 00 20 00 77 00   f.,. .w.

    0068: 68 00 73 00 63 00 6f 00   h.s.c.o.

    0070: 6d 00 6d 00 6f 00 6e 00   m.m.o.n.

    0078: 2c 00 20 00 36 00 2e 00   ,. .6...

    0080: 30 00 2e 00 30 00 2e 00   0...0...

    0088: 30 00 2c 00 20 00 34 00   0.,. .4.

    0090: 61 00 63 00 63 00 65 00   a.c.c.e.

    0098: 61 00 64 00 38 00 2c 00   a.d.8.,.

    00a0: 20 00 33 00 33 00 34 00    .3.3.4.

    00a8: 2c 00 20 00 31 00 62 00   ,. .1.b.

    00b0: 2c 00 20 00 73 00 79 00   ,. .s.y.

    00b8: 73 00 74 00 65 00 6d 00   s.t.e.m.

    00c0: 2e 00 69 00 6e 00 76 00   ..i.n.v.

    00c8: 61 00 6c 00 69 00 64 00   a.l.i.d.

    00d0: 6f 00 70 00 65 00 72 00   o.p.e.r.

    00d8: 61 00 74 00 69 00 6f 00   a.t.i.o.

    00e0: 6e 00 65 00 78 00 63 00   n.e.x.c.

    00e8: 65 00 70 00 74 00 69 00   e.p.t.i.

    00f0: 6f 00 6e 00 20 00 4e 00   o.n. .N.

    00f8: 49 00 4c 00 0d 00 0a 00   I.L.....


     

    Anyone have a clue or take on this?

    Thanks

     

     

    Case solved. In case anyone find this I managed to repair it by the help of the following article. http://technet.microsoft.com/en-us/library/cc775053(WS.10).aspx

    I ran the following commando lodctr /r at the commando prompt, and I was back on track. Good luck to all of you that have the same error, cheers.

    Friday, September 24, 2010 6:11 PM