none
Weird WHS problems. Console wont run, explorer misbehaving. Related? RRS feed

  • Question

  • I've been running WHS for several years without issue, but had a problem this week.  Ran out of disk space on the C: drive.   I deleted a bunch of .LOG files (mostly IIS logs)  and cleared the TEMP folders and Windows was happy again.

    BUT, the console application won't run anymore, either locally or via remote session.   I get an error in the Application log:

    Event 5000

    Event Typw clr20r2 P1 homeserverconsole.exe P2 6.0.0.0, P3 4acceb5f, P4 mscorlib, L5 2.0.0.0, P6 4be90358, P7 e4, P8 P10, P9 system.security.security, P10 NUL.

     

    So, in trying to diagnose the problem, I was poking around with windows explorer on the console, logged in as Administrator and noticed a second (related/unrelated?) issue:

     When trying to change settings in explorer, I went to the TOOLS, FOLDER OPTIONS, VIEW menu, and tried to enable "Show hidden files and folders" and turn off "Hide extensions for known file types".   After hitting apply and OK, explorer didn't update.  checking the settings again, I saw that they hadn't changed, and repeated attempts couldn't make it work.

    Could this second issue be related in some way to the "security" error I listed above that is keeping the homeserverconsole app from running?    I can not determine if the console issue is related to my cleaning up of log files, or a recent automatic update (that ran out of space maybe) - can't tell because it's been months since I've logged into the box

    If I have to reinstall WHS, any thing i should worry about?  I know I've installed a lot of updates and service packs along the way.  I assume they are all still available on the web - or has Microsoft End-Of-Life'd anything yet?

     

    Thanks for any help or ideas anyone can provide.

    -Tom

     

    Sunday, May 15, 2011 8:57 PM

Answers

  • So, just before I was ready to re-install last night, I had a new idea:  Maybe it's just the admin account that was corrupt.   So I created a new user account, added it to the "Administrators" group and the "Windows home Server Users" and now the console fires up and runs just fine.

     

    End result - back up and running.  No re-install.   If I can figure out where/what the actual corruption/security issue is, I will update this thread.  Otherwise I hope this helps someone else avoid having to do a reinstall.

     

    -Tom

     

    • Marked as answer by -tv- Friday, June 17, 2011 11:28 PM
    Friday, June 17, 2011 11:28 PM

All replies

  • No one has any ideas?

    -Tom

    Thursday, May 26, 2011 1:45 AM
  • Hi,

    can you see any potential related other errors in the Event log?

    Is the Windows Firewall Service started on the server? There was an issue in the past, which caused crashes, if this wasnt the case.

    Best greetings from Germany
    Olaf

    Thursday, May 26, 2011 9:20 AM
    Moderator
  • Olaf,

    No, the windows firewall is not enabled, and there are no other errors in any of the windows logs.  Just the same Application Log error getting generated every time I Try to launch the WHS console, either locally or remotely.

    Saturday, May 28, 2011 12:55 PM
  • As said - a DISABLED Windows firewall service on the server can cause the console to crash.

    So enable that service again.

    Best greetings from Germany

    Olaf

    Saturday, May 28, 2011 1:25 PM
    Moderator
  • Olaf, sorry - I didn't communicate that very well.   The firewall service was started and running.  I had looked at the specific rule set and made sure sure that the Windows Home Server Computer backup and server settings were correct.  so it's not related to the firewall being disabled.

    I'm just going to try a reinstall this weekend.

    I'm going to copy off everything in my shared folders, just in case, then reinstall and repatch and see where that leaves me.

    Thanks for the idea.

    I'll let you know how it turns out.

    -Tom

    Friday, June 3, 2011 4:01 AM
  • So, just before I was ready to re-install last night, I had a new idea:  Maybe it's just the admin account that was corrupt.   So I created a new user account, added it to the "Administrators" group and the "Windows home Server Users" and now the console fires up and runs just fine.

     

    End result - back up and running.  No re-install.   If I can figure out where/what the actual corruption/security issue is, I will update this thread.  Otherwise I hope this helps someone else avoid having to do a reinstall.

     

    -Tom

     

    • Marked as answer by -tv- Friday, June 17, 2011 11:28 PM
    Friday, June 17, 2011 11:28 PM
  • You mean on the server?

    If so, you could try to take your new account and rename or delete the corrupted profile of the real Administrator account (Deletion in Control Panel/System/Advanced/User Profiles/Settings).

    Best greetings from Germany
    Olaf

    Saturday, June 18, 2011 4:53 AM
    Moderator