Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Settings button in console not working RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    When I open the console via the WHS system tray icon on a client machine or on the server and select the settings tab, the console closes.  The event log records;

    Event Type: Error
    Event Source: .NET Runtime 2.0 Error Reporting
    Event Category: None
    Event ID: 5000
    Date:  26/06/2009
    Time:  14:52:42
    User:  N/A
    Computer: SERVER
    Description:
    EventType clr20r3, P1 homeserverconsole.exe, P2 6.0.0.0, P3 49ed39c1, P4 whscommon, P5 6.0.0.0, P6 49b73949, P7 334, P8 1b, P9 system.argumentnullexception, 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 39 00 65 00    .4.9.e.
    0058: 64 00 33 00 39 00 63 00   d.3.9.c.
    0060: 31 00 2c 00 20 00 77 00   1.,. .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: 39 00 62 00 37 00 33 00   9.b.7.3.
    0098: 39 00 34 00 39 00 2c 00   9.4.9.,.
    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 61 00 72 00 67 00   ..a.r.g.
    00c8: 75 00 6d 00 65 00 6e 00   u.m.e.n.
    00d0: 74 00 6e 00 75 00 6c 00   t.n.u.l.
    00d8: 6c 00 65 00 78 00 63 00   l.e.x.c.
    00e0: 65 00 70 00 74 00 69 00   e.p.t.i.
    00e8: 6f 00 6e 00 20 00 4e 00   o.n. .N.
    00f0: 49 00 4c 00 0d 00 0a 00   I.L.....

    Anyone have a solution please.

    Friday, June 26, 2009 3:25 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote
    It's possible that uninstalling whiist did something unexpected (i.e. somehow damaged the console). I'm not sure what it might have done, however. I don't use whiist myself, and don't have a test environment I could easily experiment with (it will take me a few hours to set one up).

    Probably, though, the only supported solution is going to be a server reinstallation. See this FAQ post for a sketchy description of the process.
    I'm not on the WHS team, I just post a lot. :)
    Saturday, June 27, 2009 4:45 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Did you recently install/remove software on your client?
    Any idea when it started?
    Friday, June 26, 2009 4:38 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Rather than looking at the client, look at the server. Did you install any add-ins recently? Uninstall any add-ins? Install or uninstall software via Remote Desktop? Change any settings in Windows Home Server or an add-in?
    I'm not on the WHS team, I just post a lot. :)
    Friday, June 26, 2009 4:59 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have tried accessing the Settings, while sat at the server directly and the same thing, the console screen just quits with not messages, but when I look in the event log I get the error reported above.

    I have removed whiist recently, but thats about the last time I could get in to the settings tab to do anything.
    Saturday, June 27, 2009 2:56 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    It's possible that uninstalling whiist did something unexpected (i.e. somehow damaged the console). I'm not sure what it might have done, however. I don't use whiist myself, and don't have a test environment I could easily experiment with (it will take me a few hours to set one up).

    Probably, though, the only supported solution is going to be a server reinstallation. See this FAQ post for a sketchy description of the process.
    I'm not on the WHS team, I just post a lot. :)
    Saturday, June 27, 2009 4:45 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for the advice Ken, I'm going to bite the bullet and do a re-install the server. I'll let you know how I get on.

    Steve.
    Tuesday, June 30, 2009 12:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Just to close tis thread, I've managed to do a re-install and it worked a treat.  Thought that this would cause me all sorts of problems, but in reality it wasn't to painful.

    Thanks for everyone help.

    Steve.
    Saturday, August 1, 2009 11:41 AM