Se connecter
 
AccueilLibrairieFormationTéléchargementsSupport techniqueCommunautésForums
Pour les professionnels de l’informatique >
> 
> 
Server manager crashing

Answered Server manager crashing

  • lundi 23 avril 2012 15:54
     
     
    Connectez-vous pour voter
    0

    Hello all,  After installing my new SCCM 2012 server, and getting it mostly up and running, I've started getting some wierd errors on teh SCCM server, and a few others.  The problem is whenever I open the system manager MMC, (or the oobe, ie.. when the server reboots) the MMC will crash.

    The error is...

    Fault bucket , type 0

    Event Name: CLR20r3

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: oobe.exe

    P2: 6.1.7600.16385

    P3: 4a5ba911

    P4: Microsoft.Windows.ServerManager

    P5: 6.1.0.0

    P6: 4ce7c964

    P7: e87

    P8: 22

    P9: System.UnauthorizedAccess

    P10:

    Attached files:

    These files may be available here:

    C:\Users\administrator.JCHC\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_oobe.exe_4ef2aac4dbe97fdace3132846a9088c65e4a2279_103b2ea8

    Analysis symbol:

    Rechecking for solution: 0

    Report Id: 9d46d822-8d57-11e1-9110-005056890000

    Report Status: 0

    I've been searching everywhere I can for clues on how to resolve it,  Found one suggestion that that mentioned permissions, in GPO's, that didn't fix the error, just made it less obnoxious (instead of crashing and saysing what the error was, the system manaer consolse just crashes ... :-)  )

    Anyone got any suggestions for this one?     it may or may not be related to the installation of the SCCM 2012 server, but the problem did start happening about a day or 2 after I got the server installed.... 


    • Modifié Halidan lundi 23 avril 2012 16:35
    •  
     

Toutes les réponses

  • lundi 23 avril 2012 15:59
     
     
    Connectez-vous pour voter
    0

    Has the system update readiness tool been run without error?

    http://windows.microsoft.com/en-US/windows7/What-is-the-System-Update-Readiness-Tool

    Then check the
    %SYSTEMROOT%\Logs\CBS\CheckSUR.log
    file for errors.

     

     

     

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

     
  • lundi 23 avril 2012 16:34
     
     
    Connectez-vous pour voter
    0
    Thanks for the tip..   downloaded and ran the tool for 2008 R2 (x64) Server.    No errors in the CheckSUR log.   Still getting the system management MMC crash.
     
  • lundi 23 avril 2012 21:43
     
     
    Connectez-vous pour voter
    0

    If it helps..   I've run the SFC- Scannow  command..    no problems reported.

    The update readiness tool .. CheckSUR.log had nothing to report.

    on the plus side.. i figured out how to enable webdav via command line.. --totally unrelated to the MMC crash.. but now SCCM will deploy software...

    MMC (Server Manager) still crashing.   checked all other mmc snap-ins I could find.. all work fine.. just the server manager that has problems.

     
  • mardi 24 avril 2012 07:50
    Modérateur
     
     
    Connectez-vous pour voter
    0

    Hi,

    Please try the following troubleshooting suggestions:

    1. Backup the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole

    2. Delete the following two keys within the OLE if they exist:

    LegacyImpersonationLevel

    LegacyauthenticationLevel

    3. Reboot the server

    4. Logon and open the Server Manager

    If the issue persists, please also test the issue in Clean Boot. For the detailed steps, please refer to the following Microsoft KB article:

    How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

    http://support.microsoft.com/kb/929135

    If the issue persists in Clean Boot, please also try to uninstall SCCM temporarily to check the result.

    Regards,

    Arthur Li

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.

    Arthur Li

    TechNet Community Support

     
  • mardi 24 avril 2012 14:39
     
     
    Connectez-vous pour voter
    0

    Thanks Arthur.   So far I have tried the Registry Key option. 
         the "LegacyImpersonationLevel" was present,  value of "2" I think .   Deleting it and rebooting did not help. .same error.

    Ran a clean boot per the article you mentioned..   still no love..   getting the MMC Crash.

    FYI, if it helps.. this is a virtual  machine (runnign on vmware Esxi 4.1)   Normally I use RDP to log in,   tried using the console option in VCenter..   Still no luck..  but thought I'd rule that out as well.

    I will Try to do the SCCM uninstall.  As I just got it "mostly" working.. I'm not really thrilled about taking it all down, but I guess I'll get some practice at setting it up this way .. right?   Will post back with results when I have some.

     
  • mardi 24 avril 2012 16:47
     
     
    Connectez-vous pour voter
    0

    And here is another update.

    Uninstalled SCCM..   No luck.   started uninstalling everything else..  no luck..

    Decided I had hosed the SCCM Server.. so started building a new VM in the background while I ran in circles with this one..    used the same ISO I downloaded off the MS licensing site that I used for the original server  (2008R2 with SP1).  VM installed fine..   only thing I added was to install the vmware tools, then joined it to my domain.  Gettign the same MMC crash.

    Is it something to do with the ISO I downloaded?    I'm going to try buildign a new VM using an older ISO without SP1 on it.. will post back results on that.  

    At this time I have 2 thoughts..   1. the ISO is somehow corrupted  (hoping this is it)  or 2, the installation of SCCM 2012 somehow hosed my domain in some way ..   (hoping this is NOT the case).

     
  • mardi 24 avril 2012 17:37
     
     
    Connectez-vous pour voter
    0

    Ok..  built a new machine using the old ISO..  (non SP1).  this is the same one I have used for most of my other machines, including my existing domain controllers..  so I'm fairly sure isn't a problem ISO.

    the new  machine installed fine,  I did NOT install vmware tools (just in case)  checked the oobe, and servermanager loaded fine, even restarted the vm a couple times,  and yes... was working fine.  After I joined the new server to the domain,  the oobe and servermanager mmc are instantly crashing.

    Any Ideas?

     
  • mercredi 25 avril 2012 01:41
     
     
    Connectez-vous pour voter
    0

    That's interesting and also nice trouble shooting by the way. I wonder if they might have run across this over here.

    http://social.technet.microsoft.com/Forums/en-us/category/configurationmanager,scinterop,dpm,systemcenter,scmdm,systemcenteroperationsmanager,systemcenteronlineservices,virtualmachinemanager,servicemanager

     

     

     

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

     
  • mercredi 25 avril 2012 14:30
     
     
    Connectez-vous pour voter
    0

    Thanks Dave,   I've been searching everywhere I can for info on this.   To me, the kicker seems to be the P9. entry   "P9: System.UnauthorizedAccess"   I've found several references to similar servermanager issues, but almost none of them reference the same item, even if they have the same event name of CLR20r3.  and the few i have foudn that are somewhat similar, either don't have a fix, or what they used to resolve the issue didn't work....

    I'm partially convinced it's something to do with Active directory at this point, somehow the domain admin account is getting locked out of the servermanager console, yet everything else appears to work fine.  perhaps it is the AD schema extension I tried to do when installign SCCM 2012, perhaps it is something else entirely.

     
  • mercredi 25 avril 2012 20:19
     
     Traitée
    Connectez-vous pour voter
    0

    And now for the current final answer.

    Spent a day on the phone with MS tech support over this issue.  in the end, it seems the problem came down to an issue in the default domain policy gpo.  In  my case, it seems to have had something to do with my having disabled the "guest" account via the gpo setting.   However,  part of the troubleshooting was to remove all gpo's affecting the problem server(s), verify the fix. .then re-enable the gpo's until the problem came back.. (for me, this was the default domain policy gpo).  then we disabled sections of the gpo.. for me it was the "computer" section that caused problems.  Finaly, I had to go through each setting, testign as I went. 

    For some reason, I was able to set the guest account option to "not configured"  get the servermanager to work on teh problem machines,  then when I went back and re-disabled the guest account, the problem was still fixed.

    I'm suspecting a partially corrupted gpo setting, that when i changed that particular setting, corrected the problem, but I may  never know for sure.

    For now, hope this helps someone esle if they ever get to have this much fun as well. 

    • Proposé comme réponse Dave PatrickMVP jeudi 26 avril 2012 01:53
    • Marqué comme réponse Halidan jeudi 26 avril 2012 15:41
    •  
     
  • jeudi 26 avril 2012 01:53
     
     
    Connectez-vous pour voter
    0

    Good to hear its sorted. Also thanks for letting us know the outcome.

     

     

     

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.