Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Server manager crashing - Fault Module clr.dll


  • Please log in to reply
4 replies to this topic

#1 David Ashcroft

David Ashcroft

  • Members
  • 169 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:37 PM

Posted 21 October 2014 - 06:40 AM

The Server manager (Windows Server 2012 R2) is crashing. As soon as you try to open Server Manager it crashes instantly with the failing module being clr.dll

This seems to relate to .net framework and after looking for a hotfix it says to contact Microsoft (who have been less than helpful so far).

Things i have tried:

= Installing the hotfix which results in an error about the update not being needed or something else on the server stopping the update.

= Uninstalling .net framework for reinstalling, but to uninstall a service/feature it launches into the server manager, so just results in a crash.

= Tried uninstalling via Powershell, but as soon as you open powershell it also crashes! 

= Tried to use the .Netframework removal tool, which said it worked. Then tried to reinstall .net framework and it said its still on the system, working and up to date...

Resulting error for both powershell and server manager is clr.dll. Basically anything relating to .net framework has stopped working and i need a fix! Thanks! 

You open the Server Manager, it shows launches and then says not responding instantly. 

You can either check for solutions or close. The following error messages is contained with it:

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: ServerManager.exe
  Application Version: 6.3.9600.17238
  Application Timestamp: 53d0b3e7
  Fault Module Name: clr.dll
  Fault Module Version: 4.0.30319.34014
  Fault Module Timestamp: 52e0b86c
  Exception Code: c0000005
  Exception Offset: 000000000000ce8f
  OS Version: 6.3.9600.2.0.0.272.7
  Locale ID: 2057
  Additional Information 1: e47e
  Additional Information 2: e47e97bf41d77858050ec34fa823c414
  Additional Information 3: 84b3
  Additional Information 4: 84b30a42d702b49f087f7920cfdbdea2

I am sure this is related to .Net Framework 4, because my Avast Management console and Powershell have also stopped working and result with the same error when launched. I could be wrong though, but that is my thoughts.... 



BC AdBot (Login to Remove)

 


#2 JohnnyJammer

JohnnyJammer

  • Members
  • 1,117 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:QLD Australia
  • Local time:03:37 AM

Posted 21 October 2014 - 07:58 PM

This is a shot in the dark but open taskmgr, kill off explorer.exe and then run the command servermanager from the File/newtask.

If that doesnt worky ou could try running the sfc /scannow command and see what it finds.



#3 sflatechguy

sflatechguy

  • BC Advisor
  • 2,233 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:37 PM

Posted 21 October 2014 - 11:48 PM

It is related to .NET framework 4. That dll is for the common language runtime, which is basically the engine that runs .NET.

 

You may need to boot into the recovery environment, remove the .NET framework from the command line, and reinstall it there as well.

 

http://msdn.microsoft.com/library/ee942965%28v=VS.100%29.aspx#uninstalling_net_framework

http://msdn.microsoft.com/library/ee942965%28v=VS.100%29.aspx#installing_manually



#4 David Ashcroft

David Ashcroft
  • Topic Starter

  • Members
  • 169 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:37 PM

Posted 22 October 2014 - 09:11 AM

Thanks for the ideas, will try Jonnys later and if nothing then will go for sflatechguy's suggestion.

 

So just for example boot into windows recovery, access command prompt and do it from there?

 

Thanks! 



#5 sflatechguy

sflatechguy

  • BC Advisor
  • 2,233 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:37 PM

Posted 22 October 2014 - 12:56 PM

Yep. Launch the recovery environment, go to the command prompt option, and run the commands from there.

 

http://technet.microsoft.com/en-us/library/hh825173.aspx

http://technet.microsoft.com/en-us/library/hh824837.aspx






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users