Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Windows Home Server Console on server won't stay open: Net 2.0 error RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I did a fresh install of WHS (pre PP1) onto a single drive. Added PP1 from a USB thumb drive then connected to the internet for all the updates to include PP2. Added McAfee VirusScan Enterprise v8.5i. Conducted an update for the latest virus scan engine and signatures. Defragged the hard drive and rebooted with the intent of adding my other drives.

    When I log directly onto the server and try to open Home Server Console it quickly pops up and close. It wont stay open. I checked the application log under event viewer and noticed that I recive a Net 2.0 runtime error when I try to open the Console.

    The console was opening with PP1, prior to the updates. Unfortunatly I didnt check to see if it would open with PP2 prior to installing the virus scanner.

    Any ideas? I'm at a loss.

    I would rather not do a fresh reinstall as I connect via a satellite service and its rather expensive.

    Sunday, May 3, 2009 6:50 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    ...

    McAfee VirusScan Enterprise v8.5i.

    ...

    As far as I know, the only McAfee virus software that's designed for use with Windows Home Server is the version that HP supplies with their MediaSmart servers. I don't believe that version is available other than through HP. If that's the source of your issue (I don't see why it would be, but it's the only thing you mention other than updates through the Windows Home Server console), you should try removing it. You may still have to do another server reinstallation, though.
    I'm not on the WHS team, I just post a lot. :)
    Sunday, May 3, 2009 2:10 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Another cause of .NET errors appearing after console crash (although it only happened opening the Settings menu on the console) was a disabled Windows Firewall service on the server in context with the WHS Toolkit installed.
    This behavior is similar enough to point into the same direction as Ken already mentioned, using a non WHS aware security suite on the server.
    Best greetings from Germany
    Olaf
    Sunday, May 3, 2009 5:18 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    ...

    McAfee VirusScan Enterprise v8.5i.

    ...

    As far as I know, the only McAfee virus software that's designed for use with Windows Home Server is the version that HP supplies with their MediaSmart servers. I don't believe that version is available other than through HP. If that's the source of your issue (I don't see why it would be, but it's the only thing you mention other than updates through the Windows Home Server console), you should try removing it. You may still have to do another server reinstallation, though.
    I'm not on the WHS team, I just post a lot. :)
    Sunday, May 3, 2009 2:10 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Another cause of .NET errors appearing after console crash (although it only happened opening the Settings menu on the console) was a disabled Windows Firewall service on the server in context with the WHS Toolkit installed.
    This behavior is similar enough to point into the same direction as Ken already mentioned, using a non WHS aware security suite on the server.
    Best greetings from Germany
    Olaf
    Sunday, May 3, 2009 5:18 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Danke. Let me try that.
    Sunday, May 3, 2009 5:43 PM