none
Server Manager fails.

    Question

  • My server manager fails to work. It was working just fine. No Idea why this happened.

     

    Server 08 is pretty much useless without this app. This is the RTM 08 from my MVLS.

     

    From my event log:

     

    Could not discover the state of the system. An unexpected exception was found:
    System.Runtime.InteropServices.COMException (0x80070543): Cannot open an anonymous level security token. (Exception from HRESULT: 0x80070543)
       at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at Microsoft.Windows.ServerManager.ComponentInstaller.CreateSessionAndPackage(IntPtr& session, IntPtr& package)
       at Microsoft.Windows.ServerManager.ComponentInstaller.InitializeUpdateInfo()
       at Microsoft.Windows.ServerManager.ComponentInstaller.Initialize()
       at Microsoft.Windows.ServerManager.Common.Provider.Initialize(DocumentCollection documents)
       at Microsoft.Windows.ServerManager.ServerManagerModel.InternalRefreshModelResult(Object state)

     

    Any ideas of what to do to address this issue would be great.

    Wednesday, March 12, 2008 3:59 PM

Answers

All replies

  • In the FWIW department this happend due to a software install.

     

    I run Avaya VoIP and the VMPro software causes server manager to stop working. This problem does not resolve itself after uninstall of the software either.

     

    https://support.avaya.com/japple/css/japple?temp.documentID=329708&temp.productID=129487&temp.releaseID=328264&temp.bucketID=108025&PAGE=Document

     

    This is the link to the software that causes the problem.

     

    IMHO if Server 08 allows a CORE service to fail upon install of external software this is a big problem.

     

    Thoughts?

     

    I still have the problem and would love to have Server Manager back Smile I went as far as ripping leftover Avaya entries out of the registry, still with no luck.

     

    *edit** same issue on another server btw.. I imagine any server 2008 touched by this software will break.

    Thursday, March 13, 2008 8:21 PM
  • I have now went as far as doing an "upgrade" I put the 08 iso in and selected an upgrade. Still no Server Manager. Upgrade went through fine, however it did break Client Access Role for exchange and I had to reinstall that but that is another issue..

     

    I confirmed in a VM any server 08 machine this software touches it will break.. this is not good..

     

    Guys Im new to microsoft if this is not the place I should be asking these questions where should I go? Microsoft makes it really tough for SMBs to use their software.

    Monday, March 17, 2008 5:33 PM
  • This really sounds more like an Avaya issue than a Microsoft issue.  Yes, you state that you wouldn't expect Microsoft software to allow something like this to happen, but when one is given administrator privileges, that person now has access to do anything on the system.  And if the software that person now runs is written in a way that it breaks things, well, ...

     

    I would take this up with Avaya to see where they are at with getting their software to run on Windows Server 2008.

     

    tgc
    Tuesday, March 18, 2008 4:10 PM
  • Yea, I hear you. This is a mega bummer to say the least. I tried to install this software on my exchange server. So now no Server Manger on that box Sad

     

    I wonder if there is a way to uninstall/reinstall server manager.

     

    I will see what avaya can do for me..

     

    Thanks

    Wednesday, March 19, 2008 8:57 PM
  • I'm from the Server Manager team. Thank you for reporting these problems!

     

    We're looked at the error message, but without the CBS.log (%windir%\Logs\CBS\CBS.log) and ServerManager.log((%windir%\Logs\ServerManager.log) we can't figure out the cause. If possible, could you please send these log to SMCPE at microsoft.com?

     

    Thank you for your help!

     

    Saturday, March 22, 2008 12:29 AM
  • Thank You! The email has been sent.

    Saturday, March 22, 2008 12:19 PM
  •  

    Im sorry, Can you be more specific as to the email I send this to??  SMCPE will not resolve for me.
    Saturday, March 22, 2008 12:25 PM
  • FWIW, I still cant access the email you mentioned above..

     

    Here is the tail end of my ServerManager.log

     

    6916: 2008-03-24 11:27:53.517 [LoadExtensionAssemblies]   No extension assemblies registered.
    6916: 2008-03-24 11:27:54.203 [OobOptionalComponentInfo]  Loading OCs from registry.
    6916: 2008-03-24 11:27:57.199 [CBS]                       LastModified CBS Time (UTC): 03/17/2008 17:16:33
    6916: 2008-03-24 11:27:57.199 [Provider]                  C:\Windows\system32\ServerManager\Cache\CbsUpdateState.bin does not exist.
    6916: 2008-03-24 11:27:57.199 [CBS]                       IsCacheStillGood: False.
    6916: 2008-03-24 11:27:57.199 [CBS]                       CreateSessionAndPackage: begin
    6916: 2008-03-24 11:27:57.979 [CBS] Error (Id=0) Function: 'CreateSessionAndPackage()->Package_GetProperty' failed: 80070543 (-2147023549)
    6916: 2008-03-24 11:27:58.306 [ExceptionHandler] Error (Id=0) An unexpected exception was found:
    System.Runtime.InteropServices.COMException (0x80070543): Cannot open an anonymous level security token. (Exception from HRESULT: 0x80070543)
       at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at Microsoft.Windows.ServerManager.ComponentInstaller.CreateSessionAndPackage(IntPtr& session, IntPtr& package)
       at Microsoft.Windows.ServerManager.ComponentInstaller.InitializeUpdateInfo()
       at Microsoft.Windows.ServerManager.ComponentInstaller.Initialize()
       at Microsoft.Windows.ServerManager.Common.Provider.Initialize(DocumentCollection documents)
       at Microsoft.Windows.ServerManager.ServerManagerModel.InternalRefreshModelResult(Object state)

    And maybe this might help:

     

    2612: 2008-01-19 06:29:30.719 [Provider]                  DiscoverAndCreate: 'RemoteServerAdminToolsOptionalComponent' is not installed.
    2612: 2008-01-19 06:29:30.719 [Provider]                  DiscoverAndCreate: 'RemovableStorageManagerOptionalComponent' is not installed.
    2612: 2008-01-19 06:29:30.719 [Provider]                  DiscoverAndCreate: 'SimpleMailTransferProtocolOptionalComponent' is not installed.
    2612: 2008-01-19 06:29:30.719 [Provider]                  DiscoverAndCreate: 'SimpleNetworkManagementProtocolServices' is not installed.
    2612: 2008-01-19 06:29:30.719 [Provider]                  DiscoverAndCreate: 'SimpleStorageAreaNetworkManagementOptionalComponent' is not installed.
    2612: 2008-01-19 06:29:30.735 [Provider]                  DiscoverAndCreate: 'SimpleTransportControlProtocolInternetProtocolServicesOptionalComponent' is not installed.
    2612: 2008-01-19 06:29:30.735 [Provider]                  DiscoverAndCreate: 'SubsystemForUnixBasedApplicationsOptionalComponent' is not installed.
    2612: 2008-01-19 06:29:30.735 [Provider]                  DiscoverAndCreate: 'TelnetClientOptionalComponent' is not installed.
    2612: 2008-01-19 06:29:30.735 [Provider]                  DiscoverAndCreate: 'TelnetServerOptionalComponent' is not installed.
    2612: 2008-01-19 06:29:30.735 [Provider]                  DiscoverAndCreate: 'TrivialFileTransferProtocolOptionalComponent' is not installed.
    2612: 2008-01-19 06:29:30.735 [Provider]                  DiscoverAndCreate: 'WindowsInternetNamingServiceOptionalComponent' is not installed.
    2612: 2008-01-19 06:29:30.735 [Provider]                  DiscoverAndCreate: 'WindowsServerBackupOptionalComponent' is not installed.
    2612: 2008-01-19 06:29:30.735 [Provider]                  DiscoverAndCreate: 'WindowsSystemResourceManagerOptionalComponent' is not installed.
    2612: 2008-01-19 06:29:30.750 [Provider]                  DiscoverAndCreate: 'WinFxOptionalComponent' is not installed.
    2612: 2008-01-19 06:29:30.750 [Provider]                  DiscoverAndCreate: 'WirelessClientOptionalComponent' is not installed.
    2612: 2008-01-19 06:29:30.781 [DH-Service]                computer: '.', service: 'MSSQL$Microsoft##SSEE', found?: False
    2612: 2008-01-19 06:29:30.781 [Provider]                  DiscoverAndCreate: 'WYukonOptionalComponent' is not installed.
    2612: 2008-01-19 06:29:30.781 [DISCOVERY] Information (Id=1) ----- Discovery done.
    2612: 2008-01-19 06:35:25.340 [DirectResult] Error (Id=0) System.Runtime.InteropServices.COMException (0x80240041): Retrieving the COM class factory for component with CLSID {BFE18E9C-6D87-4450-B37C-E02F0B373803} failed due to the following error: 80240041.
       at Microsoft.Windows.ServerManager.DirectResult.InitializeAutoUpdatesSettings()
    2612: 2008-01-19 06:35:25.465 [DirectResult] Error (Id=0) System.Runtime.InteropServices.COMException (0x80240041): Retrieving the COM class factory for component with CLSID {BFE18E9C-6D87-4450-B37C-E02F0B373803} failed due to the following error: 80240041.
       at Microsoft.Windows.ServerManager.DirectResult.InitializeAutoUpdatesSettings()

     

    I found some log entries that pointed to files in C:\Windows\System32\ServerManager\Cache I have no files in there...

    I tried adding CBSUpdateInfo & State from another machine.. Refresh worked however reported data from the server I took the files from. Shortly after the files where removed and no longer found. Of course after that back to the same problems.

     

     

     

     

    Monday, March 24, 2008 4:03 PM
  • Hi,

     

    Thank you for sending the  snippet. I'll send this to my developer. Could you please try sending the logs my email?

     

    Thanks,

    -Huong

    Tuesday, March 25, 2008 8:02 PM
  • Hello. I have the same problem. Do You find a way to solv this problem?
    Tuesday, May 13, 2008 12:08 PM
  • Not yet, The server manager team is working on it. They were able to reproduce the problem and found the issue lies in the CBS layer..

     

    It is being worked on by that team now.

     

    Did yours fail due to an avaya install??

    Tuesday, May 13, 2008 1:08 PM
  • No, I did not install avaya. I install a number of another programs and I don’t know after which of them Server manager fails.
    Tuesday, May 13, 2008 3:12 PM
  • I have the same problem here.

    I think it happened after an application installed .NET framework 1.1 on the system.

     

    If there is a solution please inform me too.

     

    Marcel

     

    Wednesday, May 14, 2008 8:59 PM
  •  

    I have the same problem also.  On one machine .Net 1.1 is not installed, on another machine, which was upgraded from Server 2003, .Net 1.1 was installed, but I do not think the Dot Net framework has anything to do with this problem, it seems to be a bug with a process or token security descriptor or elevation in order for the server manager mmc to function.

     

    2 Servers down, anyone find a solution please let us know, I really dont want to do complete reinstalls!

    Wednesday, May 21, 2008 1:16 AM
  •  

    Guys I got an email the other day, sorry for the late response.. This has been escalted and it is being worked on.. Win7 is priority in the Dev cycle now so getting this in seems to have been some trouble (go figure).. From what I can see progress is being made. I hope this helps, I _REALLY_ need this fix as do you guys so lets cross our fingers we will have a solution soon!
    Wednesday, May 21, 2008 2:31 PM
  • I used the Initial Configurations Tasks window, also Server manager window worked fine. Then I stopped using it, since all was working OK and I didn't really need it.

    No idea what I have done in the meantime, but none of the mentioned works any more. The quick launch Server Manager icon now points to %SystemRoot%\system32\CompMgmtLauncher.exe, which just shows the same as XP did when you right clicked My Computer and clicked Manage - Computer Manager console screen.

    When I try launching oobe.exe, the window opens, and after a second it says the program stopped working and needs to close.

    Code Snippet

    Description:
    Stopped working

    Problem signature:
    Problem Event Name: CLR20r3
    Problem Signature 01: oobe.exe
    Problem Signature 02: 6.0.6001.18000
    Problem Signature 03: 47917945
    Problem Signature 04: Microsoft.Windows.ServerManager
    Problem Signature 05: 6.0.0.0
    Problem Signature 06: 4791ad96
    Problem Signature 07: 1f26
    Problem Signature 08: 1e
    Problem Signature 09: System.NullReferenceException
    OS Version: 6.0.6001.2.1.0.256.1
    Locale ID: 1060

    Read our privacy statement:

    http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409


    When I try to start Server Manager, it just opens the Computer Management. When I start mmc.exe and open windows\system32\ServerManager.msc i get this:

    Code Snippet

    Description:
    Stopped working

    Problem signature:
    Problem Event Name: CLR20r3
    Problem Signature 01: mmc.exe
    Problem Signature 02: 6.0.6001.18000
    Problem Signature 03: 47919524
    Problem Signature 04: Microsoft.Windows.ServerManager
    Problem Signature 05: 6.0.0.0
    Problem Signature 06: 4791ad96
    Problem Signature 07: 1f26
    Problem Signature 08: 1e
    Problem Signature 09: System.NullReferenceException
    OS Version: 6.0.6001.2.1.0.256.1
    Locale ID: 1060

    Read our privacy statement:

    http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409


    I googled the whole thing a bit and found someone mentioning it might be Daemon tools. Can't confirm od deny it, i also have it on.
    Wednesday, May 21, 2008 2:59 PM
  • Hello, for me Server Manager is not failing outright, however I am not able to work with roles and features.  I get 3 errors while Server Manager is gathering information.  I have searched for these errors on the web and they have been reported on VISTA as a problem with WindowsUpdate. I even attempted to use some tools suggested, but woul dnot run in the sever.   Also, this is being received on a fresh install.  Any help in resolving woul db great. 

    The errors are

    1424: 2008-05-23 13:33:03.222 [ExceptionHandler] Error (Id=0) An unexpected exception was found:
    System.Runtime.InteropServices.COMException (0x80073712): The component store has been corrupted. (Exception from HRESULT: 0x80073712)
       at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at Microsoft.Windows.ServerManager.ComponentInstaller.Initialize()
       at Microsoft.Windows.ServerManager.Common.Provider.Initialize(DocumentCollection documents)
       at Microsoft.Windows.ServerManager.ServerManagerModel.InternalRefreshModelResult(Object state)

    2720: 2008-05-23 13:33:42.008 [ExceptionHandler] Error (Id=0) An unexpected exception was found:
    System.Runtime.InteropServices.COMException (0x8007370C): An identity contains two definitions for the same attribute. (Exception from HRESULT: 0x8007370C)
       at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at Microsoft.Windows.ServerManager.ComponentInstaller.Initialize()
       at Microsoft.Windows.ServerManager.Common.Provider.Initialize(DocumentCollection documents)
       at Microsoft.Windows.ServerManager.ServerManagerModel.InternalRefreshModelResult(Object state)

     

    1424: 2008-05-23 13:30:20.779 [ExceptionHandler] Error (Id=0) An unexpected exception was found:
    System.Runtime.InteropServices.COMException (0x8007370B): The name of an attribute in an identity is not within the legal range. (Exception from HRESULT: 0x8007370B)
       at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at Microsoft.Windows.ServerManager.ComponentInstaller.Initialize()
       at Microsoft.Windows.ServerManager.Common.Provider.Initialize(DocumentCollection documents)
       at Microsoft.Windows.ServerManager.ServerManagerModel.InternalRefreshModelResult(Object state)

    Friday, May 23, 2008 8:35 PM
  • Hi! I have the same problem too. Do You find a way to solv it?
    Friday, May 23, 2008 9:14 PM
  • Could I change features without Server Manager?
    Tuesday, May 27, 2008 3:55 PM
  • Ok, I got a response in an email. Try it out. I wont be able to test until tomorrow.

     

    The default machine-wide COM authentication level is set to None. This caused the problem. We try changing it back to its default value of Connect (dcomcnfg.exe can be used to make this change) and things appear to work. It appears that the app you installed made this change to the machine configuration. It also changed the default COM impersonation level to Impersonate (from a default value of Identify). While this change had no affect on the current problem, it is an unsecure change to make.

     

    Could you please try the following and see if it fix the problem on your machine:

    1.     From an elevated* cmd window run:

    Dcomcnfg.exe

               

    *Or click through the UAC prompt

    2.     Choose ComponentServices->Computers->My Computer.

    3.     Choose Properties from the context menu.

    4.     Choose the Default Properties tab.

    5.     Select Connect in the Default Authentication Level drop down list if it is set to None. Choose OK, confirm selection in popup and close dcomcnfg.exe.

    6.     If the authentication level is not set to None, don’t change it, since it may have been set by something else (such as an Admin).

     

    7.     While at it, it is better to change the Default Impersonation Level to Identify, if it is set to something else. As mentioned, a setting greater than Identify lowers the COM security on the box.

     

    8.     Of course, these settings may have the effect of breaking the app you installed. If it does, then it is a bug in the app. An app must not require changes to the machine-wide COM security configuration. You may want to contact the vendor of the app.

     

    Wednesday, May 28, 2008 1:35 PM
  • Yes, It`s work!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!  
    Wednesday, May 28, 2008 2:54 PM
  • It didn't work at my server.

    Must the 'Enable Com Internet Services on this computer' be selected?
    If I set the Default Authentication Level on 'None' or on 'Connect' it doesn't work.

    I get the following error in the servermanager log:


    4656: 2008-06-02 19:45:51.797 [CBS]                       LastModified CBS Time (UTC): 06/02/2008 07:04:08
    4656: 2008-06-02 19:45:51.797 [Provider]                  System changed since last refresh: True
    4656: 2008-06-02 19:45:51.797 [CBS]                       LastModified CBS Time (UTC): 06/02/2008 07:04:08
    4656: 2008-06-02 19:45:51.797 [Provider]                  C:\Windows\system32\ServerManager\Cache\CbsUpdateState.bin does not exist.
    4656: 2008-06-02 19:45:51.797 [CBS]                       IsCacheStillGood: False.
    4656: 2008-06-02 19:45:51.797 [CBS]                       CreateSessionAndPackage: begin
    4656: 2008-06-02 19:45:52.109 [CBS] Error (Id=0) Function: 'CreateSessionAndPackage()->Session_OpenPackage' failed: 80070490 (-2147023728)
    4656: 2008-06-02 19:45:52.109 [ExceptionHandler] Error (Id=0) An unexpected exception was found:
    System.Runtime.InteropServices.COMException (0x80070490): Element not found. (Exception from HRESULT: 0x80070490)
       at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at Microsoft.Windows.ServerManager.ComponentInstaller.CreateSessionAndPackage(IntPtr& session, IntPtr& package)
       at Microsoft.Windows.ServerManager.ComponentInstaller.InitializeUpdateInfo()
       at Microsoft.Windows.ServerManager.ComponentInstaller.Initialize()
       at Microsoft.Windows.ServerManager.Common.Provider.Initialize(DocumentCollection documents)
       at Microsoft.Windows.ServerManager.ServerManagerModel.InternalRefreshModelResult(Object state)

    Marcel
    • Edited by Slotb007 Monday, June 02, 2008 5:46 PM Changes content
    Monday, June 02, 2008 5:40 PM
  • hi edmund22,
    u still have the problem with Initial Configurations Tasks window and Server manager?

    ..
    oobe.exe
    nullreferenceexception 
    ...

    i have the same problem. searched for hours , i could'nt solve it.
    have u find a solution ? 
    if so , pls send me , nskeskin X gmail X com ?
    thanks.

    Wednesday, June 18, 2008 1:36 PM
  • Any other solution to this problem ? The solution provided above didn't work for me those settings were already set.
    Sunday, June 22, 2008 2:31 AM
  • Thanks you so much for pushing MS on this issue.  I had the same problem on my Exchange server and was getting frustrated as H$%#.

    Thanks again!
    RCITGUY
    Tuesday, June 24, 2008 4:02 PM
  • Whats the latest news in this issue?

    I have the same problem, only I have not installed anything but the updates from windows update.

    It seems that the problem is not third party software related.

    Thanks
    Monday, August 25, 2008 6:02 PM
  • we are also waiting for some news about this failure.
    With actual windows update it still does not work.

    64bit Windows was always ok - but the 32bit Version simply does not work.
    Wednesday, August 27, 2008 10:39 AM
  • Hello, i have the same problem with a fresh installation of windows server 2008 enterprise (32 bit). If i try to open server manager i have these:

    Description:
      Stopped working

    Problem signature:
      Problem Event Name:    CLR20r3
      Problem Signature 01:    mmc.exe
      Problem Signature 02:    6.0.6001.17051
      Problem Signature 03:    47452dd0
      Problem Signature 04:    Microsoft.Windows.ServerManager
      Problem Signature 05:    6.0.0.0
      Problem Signature 06:    474547fe
      Problem Signature 07:    1ca1
      Problem Signature 08:    3a
      Problem Signature 09:    System.NullReferenceException
      OS Version:    6.0.6001.2.1.0.0.1
      Locale ID:    1040

    Thanks.

    Thursday, August 28, 2008 10:42 AM
  • I've spent my entire day trying to resolve this after installing Microsoft's Windows updates and .net framework on a Windows 2008 64 bit Edition Quad-Core Server. This is absolutely ridiculous! Is Microsoft gonna leave us hanging on this issue? Come on guys.... What's a solution?


    Description:

    Windows Server Initial Configuration Tasks Stopped Working!

    Problem signature:

    Problem Event Name: CLR20r3

    Problem Signature 01: oobe.exe

    Problem Signature 02: 6.0.6001.18000

    Problem Signature 03: 47917945

    Problem Signature 04: Microsoft.Windows.ServerManager

    Problem Signature 05: 6.0.0.0

    Problem Signature 06: 4791ad96

    Problem Signature 07: 1f26

    Problem Signature 08: 1e

    Problem Signature 09: System.NullReferenceException

    OS Version: 6.0.6001.2.1.0.256.1

    Locale ID: 1033

    Read our privacy statement:

    http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

    • Edited by Mike Vail Wednesday, November 12, 2008 1:47 AM
    Wednesday, November 12, 2008 1:46 AM
  • First - I am so sorry about my English

    Have this problem on my 2008 Russian Version after installing Some Security updates
    This fix was helpfull.
    Big Thanks!!!!

    Could you please try the following and see if it fix the problem on your machine:

    1.     From an elevated* cmd window run:

    Dcomcnfg.exe

               

    *Or click through the UAC prompt

    2.     Choose ComponentServices->Computers->My Computer.

    3.     Choose Properties from the context menu.

    4.     Choose the Default Properties tab.

    5.     Select Connect in the Default Authentication Level drop down list if it is set to None. Choose OK, confirm selection in popup and close dcomcnfg.exe.

    6.     If the authentication level is not set to None, don’t change it, since it may have been set by something else (such as an Admin).

     

    7.     While at it, it is better to change the Default Impersonation Level to Identify, if it is set to something else. As mentioned, a setting greater than Identify lowers the COM security on the box.

     

    8.     Of course, these settings may have the effect of breaking the app you installed. If it does, then it is a bug in the app. An app must not require changes to the machine-wide COM security configuration. You may want to contact the vendor of the app.




    Wednesday, November 12, 2008 4:31 PM
  • so??
    microsoft still dont have a solution for it??

    cause this one didn´t work for me...

    either oobe.exe and server manager still not working
    still have a clean instalation of server 2008

    and those steps didnt helped at all
    Thursday, November 27, 2008 5:13 PM
  • Hey all dear friends !

    I found a way for this problem:
    1. Install a fresh SERVER 2008
    2. Before any thing, go to "Add Features" and only add ".Net Frame Work"
    3. Restart your computer.
    4. Add other features, you need, one by one and restart, if needed.
    5. That is all !
    6. After any thing, (in my experience) install SQL server 2008 and it was install .Net 3.5 SP1 successfully.

    My server is in working state now !

    Wednesday, December 03, 2008 10:40 PM
  • This solution doesn't work for me, either.
    I seem to have the same problems on my box and get the same errors. No non-MS apps installed. Cannot use (or see) Roles or Features. I also cannot see any "installed updates" the box is empty, despite doing all the updates. One keeps failing, KB957097, not sure if it's related.

    Any help out there on this issue? Seems a lot of you have the problem, but I don't see any fixes.
    Tuesday, December 16, 2008 4:30 AM
  • Are MS working on this issue now? Seems like a lot of people have the problems but yet no fix. I have tried the proposed solution above, but without luck. Are there any way to start Features without the Server Manager?
    • Proposed as answer by R. Michael Wednesday, May 13, 2009 6:26 PM
    Monday, January 05, 2009 7:40 AM
  • Ok, I see this has had no activity in a while.  I just installed Server 2008.  Went well.  Wne to install Web Server Role and installation fails, over and over....hey MS...you out there?
    -MBowles
    • Proposed as answer by R. Michael Wednesday, May 13, 2009 6:24 PM
    Thursday, April 30, 2009 3:50 PM
  • Disable UAC then reboot.
    Install the Management Console (IIS Management Console and/or IIS 6 Management Console)
    Enable UAC then reboot.

    Wednesday, May 13, 2009 6:31 PM
  • I used the solution proposed by Deathlaw , Default Authentication Level drop down list if it is set to Call.

    And that's worked for me
    Sunday, July 12, 2009 10:29 PM
  • Deathlaw's post worked for me as well.
    Monday, July 13, 2009 5:07 PM
  • Issue described by Deathlaw was present on 2 of 4 cluster nodes.  Default Authentication = Call fixed both.  Thanks a million!

    Thursday, December 31, 2009 9:08 AM
  • Deathlaw's post contains the most common 'fix' for the problem, but for me the instructions don't match what I see on my screen (Windows Server 2008 Standard). I'm logged in as Administrator so for 1. I just click Start, Run. 2. done. 3. is the problem.

    When I right-click on "My Computer" and select "Properties"  I don't see what is described. I see two tabs -- "COM Security" and "MSDTC". If I close and right-click "My Computer" and select "Properties' again, I now see the "Default Properties' tab. When I view it "Enable Distributed COM on this computer" is unchecked and the fields described are greyed out. If I place a check mark in "Enable Distributed COM on this computer" the fields described are no longer grey but there are no options on the drop down list. If I "Apply" "Enable Distributed COM on this computer" remains enabled but there is still no info in the drop down lists. When I exit and come back everything has returned to its previous state (not enabled and greyed out).

    Is there any other way to solve this error regarding Roles and Features showing an Error? Thanks.

    --------------QUOTED SECTION STARTS-----------------
    Please perform the following steps to reset the DCOM authentication and impersonation level to the default:

     

    1.       Click Start, right click the Command Prompt and click Run as administrator. Click Continue if being prompted.

    2.        In the Command Prompt, type the following command and press Enter:

     

    Dcomcnfg.exe

     

     Click to expand Component Services and then expand Computers.

     Right click "My Computer" and click Properties.


    3.        Click on the Default Properties tab.

     In the "Default Authentication Level" drop down list, if it is set to "None", change it to "Connect".

    In the "Default Impersonation Level" drop down list, select "Identify".

     Click Apply and click OK.

    ------------QUOTED SECTION ENDS----------------

    Friday, January 15, 2010 2:37 PM
  • Deathlaw and peterd2001 post it is work fine for me! thanks in bounch.
    Friday, July 16, 2010 1:00 AM
  • Any update on this error, suggestions above do not fix my problem as my dcomconfig is already setup like it should be???????????

    no fix around anywhere for this problem, windows server 2008 is useless , don't understand why microsoft would release something like this with such a serious problem.

    poor quality control

     

    Thursday, August 12, 2010 12:11 PM
  • Pelase try this link n download the hot fix:

    http://www.microsoft.com/downloads/en/details.aspx?FamilyID=ab99342f-5d1a-413d-8319-81da479ab0d7&displaylang=en

     

    Run it and select to uninstall . please wait for a while it take few minutes to complete. Its working with me.

    Now my server manager back to normal. Seem the Microsoft .NET Framework 3.5 service pack 1 caused the server manager component crashed

     

    Good Luck

     

     

     

    Tuesday, October 26, 2010 3:06 AM
  • I tried this suggestion and when I run the .NET Framework 3.5 SP1 Setup, I get the message:

    "You must use the Role Management Tool to install or configure Microsoft .NET Framework 3.5"

    That's my problem The "Role Management Tool" is not working....

     

     

    Tuesday, October 26, 2010 7:47 PM
  • Hi,
     
    Please run the SUR tool, http://support.microsoft.com/kb/947821, and
    post the content of %systemroot%\Logs\CBS\CheckSUR.log file.
     

    -- Mike Burr
    Tuesday, October 26, 2010 7:58 PM
  • i had a similar issue-  a possible fix could be found at:

     

    http://support.microsoft.com/default.aspx?scid=kb;en-US;2461206

     

     

    Here are the steps to fix the issue:

    1. Get the Microsoft Update Readiness Tool from the location: http://support.microsoft.com/kb/947821
    2. Run the Microsoft Update Readiness Tool on the problematic computer.
    3. You open the %Systemroot%\Windows\logs\CBS\Checksur.log file after the scan was completed.
    4. You check corrupt information in the files. Here are some samples:

    (f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.mum  Expected file name Package_for_KB978601_server~31bf3856ad364e35~amd64~~6.0.1.0.mum does not match the actual file name
    (f) CBS MUM Corrupt 0x00000000 servicing\Packages\Package_for_KB979309~31bf3856ad364e35~amd64~~6.0.1.0.mum  Expected file name Package_for_KB979309_server~31bf3856ad364e35~amd64~~6.0.1.0.mum does not match the actual file name

    Or 

    (f) CBS MUM Corrupt 0x800B0100 servicing\Packages\Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.mum servicing\Packages\Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.cat Package manifest cannot be validated by the corresponding catalog
    (f) CBS MUM Corrupt 0x800B0100 servicing\Packages\Package_for_KB979309~31bf3856ad364e35~amd64~~6.0.1.0.mum servicing\Packages\Package_for_KB979309~31bf3856ad364e35~amd64~~6.0.1.0.cat Package manifest cannot be validated by the corresponding catalog

    Or

    (f) CBS MUM Missing 0x00000002 servicing\packages\Package_114_for_KB955839~31bf3856ad364e35~amd64~~6.0.1.0.mum
    (f) CBS MUM Missing 0x00000002 servicing\packages\Package_83_for_KB955839~31bf3856ad364e35~amd64~~6.0.1.0.mum

    Further down you will see:

    Unavailable repair files:
    servicing\packages\Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.mum
    servicing\packages\Package_for_KB979309~31bf3856ad364e35~amd64~~6.0.1.0.mum
    servicing\packages\Package_for_KB978601~31bf3856ad364e35~amd64~~6.0.1.0.cat
    servicing\packages\Package_for_KB979309~31bf3856ad364e35~amd64~~6.0.1.0.cat

    These files need to be copied into: %systemroot\Windows\Servicing\Packages

     1. You first need to gain control over that folder. In order to do this use the following commands:

    takeown /F c:\Windows\Servicing\Packages /D y /R

    Then assign full control using:

    cacls c:\Windows\Servicing\Packages /E /T /C /G "UserName":F

    This will grant you full control over the directory.

    2. Now you need to gather the missing or corrupted files from the checksur log:

    - Download the KB files for the missing files
    servicing\packages\Package_for_ KB978601 ~31bf3856ad364e35~amd64~~6.0.1.0.mum

    - Unpack them using the following command:

    Expand -F:* UpdateKBXXXX.msu x:\DestinationDirectory

    After you expand you will see a UpdateKBXXXX.cab File. Expand it as well:

    Expand -F:* UpdateKBXXXX.CAB x:\DestinationDirectoryCAB

    Inside of this cab you will need to grab 2 files: update.mum and update.cat

    3. Rename the gathered update.mum and update.cab files exactly as they are in the checksur.log:

    Ex.: update.mum for KB978601 will be Package_for_ KB978601 ~31bf3856ad364e35~amd64~~6.0.1.0.mum
    Do the same for for all the other missing/corrupt files and place them into the directory specified in checksur.log (/servicing/packages)


    After these steps the problem should be fixed. No reboot required.

    Note: If the ServerManager is not working even after doing these steps, run the Update Readiness Tool again and double check the steps described above.

    Monday, November 22, 2010 5:59 AM
  • I've ran the Microsoft Update Readiness Tool multiple times and all of the times the check has come back with No errors detected however the ServerManager.log continues to state that the CBSUpdateState.bin file does not exist and the ServerManager\cache folder is empty.
    Monday, November 22, 2010 4:52 PM
  • You'll need to copy this from a similarly configured server or restore
    the server from backup to a state where this file exists.
     

    -- Mike Burr
    Tuesday, November 23, 2010 2:59 AM
  • I tried top copy the CbsUpdateState.bin from another R2 x64 server but I had the same results as "raverz1":  At the point where the Roles or Features display comes back and says "Error", the CbsUpdateState.bin disappears from the ~\Cache folder.

    And, like "Skooterkool", I can't run the .NET 3.5 SP1 uninstall fix that was suggested because I get the "must use the Role Management Tool to install or configure Microsoft .NET Framework 3.5 SP1."

    I tried running SUR but it just sits and spins at the "Searching for updates..." message.

    I tried the suggested fix using PowerShell but that didn't work as it responded with this error:

    • Add-WindowsFeature : Failed to initialize. At line:1 char:19 + Add-WindowsFeature <<<< as-net-framework + CategoryInfo : OperationStopped: (:) [Add-WindowsFeature], COMException + FullyQualifiedErrorId : DiscoveryFailed,Microsoft.Windows.ServerManager.Commands.AddWindowsFeatureCommand

    And the check of my DCom show it was already at the recommend settings of “Default Authentication Level = Connect” and “Default Impersonation Level = Identify”.

    The keys seem to be in the ServerManager.log here:

    • 2772: 2011-01-13 11:24:49.094 [Provider] C:\Windows\system32\ServerManager\Cache\CbsUpdateState.bin does not exist.

    And in the event log entry here:

    • Could not discover the state of the system. An unexpected exception was found:
    • System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed. (Exception from HRESULT: 0x800706BE)

    I'm in a catch-22 here.  Microsoft, are you listening?  This appears to have been an issue (in various forms) going back to March 2008 when this thread originated.  I just built this system last week from an ISO dated to October 2009.

    This may be related or not: Even though Windows Update shows "System is up to date" when I first go in, if I click "Check for updates..." it just sits and spins and never comes back. Yet I have confirmed internet access.

    P.S. I did send the logs and the description of my issue to the smcpe#microsoft.com address.  No response yet but we'll see if there is one.

    Thursday, January 13, 2011 8:44 PM
  • I ended up rebuilding the server from scratch.  Fortunately, this was a new installation so it didn't cost me much.  I definitely noticed a difference in the installation process this time vs. last time at the point where it does the initial updates.  First time it got two, this time it got 45.  I suspect the first time it got an incomplete update that left it in an in-between state so the installer wouldn't work any more.  All the symptoms it was exhibiting (including the ones on this thread) were all related to the installer operation.

    All is working well now.  Sometimes the "nuke-and-repave" option is the solution.

    • Proposed as answer by Moses Hull Friday, February 25, 2011 6:57 PM
    • Unproposed as answer by Moses Hull Friday, February 25, 2011 6:57 PM
    Friday, January 14, 2011 9:01 PM
  • I had install the Avaya software.

    This worked for me.

    1. Using elevated permissions, run Dcomcnfg.exe

    2. In the "Component Services" window, navigate to ComponentServices->Computers->My Computer.

    3. Right-click on "My Computer" and select [Properties] from the context menu.

    4. In the "My Computer Properties" dialog, select the [Default Properties] tab.

    5. Change the "Default Authentication Level" drop to 'Connect'; if it is set to None.

    7. Change the "Default Impersonation Level" to Identify; if it is set to something else.

    8. Press the OK button in the "My Computer Properties" dialog.


    Moses Hull of Alexant Systems
    Friday, February 25, 2011 7:07 PM
  • None of the suggested workaround above worked for me - I have servermanager failing in the GUI as well as from PowerShell - the same null pointer dereference, and WindowsUpdate also fails.

    Anyone? Anyone? Bueller?

     

    Tuesday, March 01, 2011 11:35 PM
  • I also had the same problem with a fresh full installation of Win2008 after running updates from Microsoft. The culprit is the .Net 3.5 SP1. Uninstall it and install the standalone version of .Net 4. Server manager will work fine.
    Saturday, April 09, 2011 11:09 AM
  • THANK YOU!!!!!!!!! That worked perfectly.

    I followed your instructions and put together the steps into a batch file since a had a few servers to repair. See below for syntax: 

    -Steve Signorelli

    Copy below syntax into a batch file named like "Repair-KB2524375.bat" and place it in a directory called "FixForMe" in the C:\ drive. Also download the package from MS and placed it in this directory. 

    ::Take Ownership of packages directory contents

    takeown /F C:\Windows\Servicing\Packages /D y /R

    ::Provide Full control of files for current logged in user - Just manually enter

    cacls c:\Windows\Servicing\Packages /E /T /C /G "DOMAIN\username":F

    ::With downloaded package in current directory expand it

    MD C:\FixForMe\KB2524375

    Expand -F:* Windows6.1-KB2524375-x64.msu C:\FixForMe\KB2524375

    ::Expand the cab files into their own directory. 

    MD C:\FixForMe\KB2524375\KB2524375-CAB

    CD C:\FixForMe\KB2524375

    Expand -F:* Windows6.1-KB2524375-x64.CAB C:\FixForMe\KB2524375\KB2524375-CAB

    ::Isolate the files you need to repair the KB installation

    cd C:\FixForMe\KB2524375\KB2524375-CAB

    MD C:\FixForMe\KB2524375\KB2524375-CAB\NeededFiles

    Move C:\FixForMe\KB2524375\KB2524375-CAB\update.mum C:\FixForMe\KB2524375\KB2524375-CAB\NeededFiles\Package_for_KB2524375~31bf3856ad364e35~amd64~~6.1.1.1.mum

    Move C:\FixForMe\KB2524375\KB2524375-CAB\update.cat C:\FixForMe\KB2524375\KB2524375-CAB\NeededFiles\Package_for_KB2524375~31bf3856ad364e35~amd64~~6.1.1.1.cat

    ::Copy the files to the proper location as referenced by the CBS.log

    XCOPY /-Y C:\FixForMe\KB2524375\KB2524375-CAB\NeededFiles\Package_for_KB2524375~31bf3856ad364e35~amd64~~6.1.1.1.mum C:\Windows\Servicing\Packages\Package_for_KB2524375~31bf3856ad364e35~amd64~~6.1.1.1.mum

    XCOPY /-Y C:\FixForMe\KB2524375\KB2524375-CAB\NeededFiles\Package_for_KB2524375~31bf3856ad364e35~amd64~~6.1.1.1.cat C:\Windows\Servicing\Packages\Package_for_KB2524375~31bf3856ad364e35~amd64~~6.1.1.1.cat

     

     

    Monday, May 09, 2011 5:35 PM
  • Tried everything on this page, no success, clean install of the current iso of the Server 2008 R2 Standard SP1 trial from Microsoft. Install Acronis Backup and Recovery caused the issue, that or windows updates...

     

    I can open add remove programs, .net 4 is listed as 3 separate items, no reference to 3.5 as being installed or updated.

    Tuesday, May 10, 2011 1:26 PM
  • Also the Dcom security solution my settings were already "connect" and "identify".

    I tried the Microsoft Update Readiness Tool from the location: http://support.microsoft.com/kb/947821 and it says its not valid for my operating system. I think I will try to manually uninstall or use the .net cleanup tool to wipe .net from the system.

    Tuesday, May 10, 2011 1:29 PM