Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Console crashes with Dot Net 2.0 error RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm having a real problem with the Console.  It keeps crashing with the following error:

    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 n3ctrye2kn3c34sgl4zqyrbfte4m13nb, P10 NIL

    It does it almost every time I try to remove a drive, but it happens randomly other times too.  Oddly, if you just leave the console open, it will eventually die even if you don't do anything.

    I tried to reinstall Dot Net 2.0 with the network distributable, but it won't install because WHS has DotNet 2.0 Sp2 installed and the network version is pre-SP1.

    Saturday, August 1, 2009 1:30 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    I had this same problem and was about to give up and do a recovery install. However, I seem to have fixed the problem. Here's what I did:

    1) Log on to the WHS box and go to the Event Viewer
    2) Go to the HomeServer log. I received an error saying the log file was corrupted.
    3) Right click and clear all events from the HomeServer log. Do not save any.
    4) Run the WHS conole. For me, that did the trick and everything worked.
    • Marked as answer by Tom Scales Sunday, August 23, 2009 10:35 PM
    Saturday, August 22, 2009 1:17 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    You should be able to RDP into the server and remove .net SP2. Then try reinstalling .net again.

    Cruise

    P.S. It might cause other problems when/after doing the removal, not sure.
    Saturday, August 1, 2009 2:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm having a real problem with the Console.  It keeps crashing with the following error:

    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 n3ctrye2kn3c34sgl4zqyrbfte4m13nb, P10 NIL

    It does it almost every time I try to remove a drive, but it happens randomly other times too.  Oddly, if you just leave the console open, it will eventually die even if you don't do anything.

    I tried to reinstall Dot Net 2.0 with the network distributable, but it won't install because WHS has DotNet 2.0 Sp2 installed and the network version is pre-SP1.


    Are you having the problem if you open the Console from the server desktop as well?  If so, did you try repairing your .NET 2.0 installation?  (Find .NET 2.0 in Add/Remove programs on your server, click on Click here for support information, then click the Repair button)
    Saturday, August 1, 2009 2:26 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Both good thoughts, neither works.

    If you try to remove it, it says it can't be removed because other programs depend on it.

    If you try to repair it, it wants a file that used to be in the temporary directory (but isn't anymore).

    If you try to install the network distributable for 2.0, it is too old (as SP2 is installed).

    It happens through RDP and on the server itself.

    The backup service keeps dying too.
    Saturday, August 1, 2009 3:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Both good thoughts, neither works.

    If you try to remove it, it says it can't be removed because other programs depend on it.

    If you try to repair it, it wants a file that used to be in the temporary directory (but isn't anymore).

    If you try to install the network distributable for 2.0, it is too old (as SP2 is installed).

    It happens through RDP and on the server itself.

    The backup service keeps dying too.

    In that case, I would try running chkdsk /r on your C partition (in case your hard drive is failing).  Other than that, I think you are down to a Server Reinstallation.
    Saturday, August 1, 2009 6:35 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    It's very unlikely that the .Net Framework on Tom's machine is corrupted. The Event Info he has posted is referring to an application crash of HomeServerConsole.exe which utilizes (--> runs on) the .Net Framework. Reinstalling/repairing the .Net Framework will not help in any way. Tom, you should connect to your WHS box via RDP and have a look in your %qlogs% directory. There you'll find a bunch of HomeServerConsole-Logfiles. Please review the latest ones for errors ("Exceptions") and post the log excerpts here, so we can see which add-in (most likely) is causing the crash.

    Andreas M.
    Monday, August 3, 2009 3:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I had this same problem and was about to give up and do a recovery install. However, I seem to have fixed the problem. Here's what I did:

    1) Log on to the WHS box and go to the Event Viewer
    2) Go to the HomeServer log. I received an error saying the log file was corrupted.
    3) Right click and clear all events from the HomeServer log. Do not save any.
    4) Run the WHS conole. For me, that did the trick and everything worked.
    • Marked as answer by Tom Scales Sunday, August 23, 2009 10:35 PM
    Saturday, August 22, 2009 1:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Amazing.  The problem went away and I couldn't figure out why.

    This was the reason.
    Sunday, August 23, 2009 10:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Did you have any networkconnectivity problems at the time? I'm was getting this error when my lan was down. When it was up again so did the console....I think WHS is trying to connect to the internet for a crl or something
    Friday, November 27, 2009 4:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Brilliant!!!!!!!!!!!!!!!!!!!!!!!!!!

    I cleared the Hoome Server Event log and all is fine1

    Thanks so much.

    Thursday, October 20, 2011 9:59 PM