locked
Can not add roles RRS feed

  • Question

  • Windows Server 2012 R2, I am trying to add the domain services role, I keep getting can not install, server needs a re-boot. I re-boot, when it comes back up the server manager says Online - can not get role or feature data.

    When I try and refresh server manager I get the following error:

    Role and feature refresh failed with the following error: The request to list features available on the specified server failed.

    The operation cannot be completed, because the server that you specified requires a reboot.

    So I restart the server, same message.

    Next Up I go and install all the critical updates, reboot, Same Message.

    Third item I try is DISM /Online /Cleanup-image /Restorehealth which returns:

    Image Version 6.3.9600.17031

    =====100.00%=====

    The restore operation completed successfully. Component store corruption was repaired.

    The Operation Completed Successfully.

    I then check for the PendingFileRenameOperations key, is not their.

    I also check the CurrentRebootAttempts key and it is zero.

    I reboot again, same message in server manager, same error if I try and install the domain services role.

    I run DISM again, same result, check keys, same, reboot again, still no change.

    Am I missing something?  Where should I look to get this re-boot error cleaned up? I need to get the domain service roles installed on this server, any help would be appreciated.

    Curt Winter

    Saturday, February 14, 2015 6:15 AM

All replies

  • Hi,

    Is this set to 0?

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\UpdateExeVolatile.


    Best Regards,

    Jesper Vindum, Denmark

    Systems Administrator

    Help the forum: Monitor(alert) your threads and vote helpful replies or mark them as answer, if it helps solving your problem.

    Saturday, February 14, 2015 12:51 PM
  • Jesper,

    This folder does not exist in the registry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\

    I searched the entire registry for "UpdateExeVolatile" and it was not found.

    Curt Winter

    Thursday, February 19, 2015 3:40 PM
  • Hi,

    Did you install any update before the issue occured?

    Please check the result in %systemroot%\Logs\CBS\CBS.log

    Regards.


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Friday, February 20, 2015 5:51 AM
  • I have installed two sets of windows Critical updates in the middle of this issue without a problem.

    Everytime after the reboot following the update, I tried the Domain roles again, still same message, server needs a reboot.

    Here is the CBS log from the DISM /Online /Cleanup-image /Restorehealth that I ran today:


    2015-02-26 11:51:36, Info                  CBS    SQM: CheckSur: hrStatus: 0x0 [S_OK], download Result: 0x0 [S_OK]
    2015-02-26 11:51:36, Info                  CBS    Count of times corruption detected: 0
    2015-02-26 11:51:36, Info                  CBS    Seconds between initial corruption detections: -1
    2015-02-26 11:51:36, Info                  CBS    Seconds between corruption and repair: -1
    2015-02-26 11:51:37, Info                  CBS    SQM: Upload requested for report: CheckSurSqm, session id: 142858, sample type: Standard
    2015-02-26 11:51:37, Info                  CBS    SQM: Ignoring upload request because the sample type is not enabled: Standard
    2015-02-26 11:51:37, Info                  CBS    Reboot mark cleared
    2015-02-26 11:51:37, Info                  CBS    Winlogon: Deregistering for CreateSession notifications
    2015-02-26 11:51:37, Info                  CBS    Winlogon: Stopping notify server
    2015-02-26 11:51:37, Info                  CBS    Winlogon: Unloading SysNotify DLL
    2015-02-26 11:51:37, Info                  CBS    Exec: Processing complete, session(Corruption Repairing): 30429666_1778736973 [HRESULT = 0x00000000 - S_OK]
    2015-02-26 11:51:37, Info                  CBS    Session: 30429666_1778736973 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
    2015-02-26 11:51:37, Info                  CBS    Session: 30429668_2090079201 initialized by client DISM Package Manager Provider.
    2015-02-26 11:53:37, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
    2015-02-26 11:53:37, Info                  CBS    TiWorker signaled for shutdown, going to exit.
    2015-02-26 11:53:37, Info                  CBS    Ending the TiWorker main loop.
    2015-02-26 11:53:37, Info                  CBS    Ending the TrustedInstaller main loop.
    2015-02-26 11:53:37, Info                  CBS    Starting TiWorker finalization.
    2015-02-26 11:53:37, Info                  CBS    Starting TrustedInstaller finalization.
    2015-02-26 11:53:37, Info                  CBS    Ending TrustedInstaller finalization.
    2015-02-26 11:53:38, Info                  CBS    Ending TiWorker finalization.
    2015-02-26 11:55:15, Info                  CBS    TI: --- Initializing Trusted Installer ---
    2015-02-26 11:55:15, Info                  CBS    TI: Last boot time: 2015-02-25 13:34:37.496
    2015-02-26 11:55:15, Info                  CBS    Starting TrustedInstaller initialization.
    2015-02-26 11:55:15, Info                  CBS    Ending TrustedInstaller initialization.
    2015-02-26 11:55:15, Info                  CBS    Starting the TrustedInstaller main loop.
    2015-02-26 11:55:15, Info                  CBS    TrustedInstaller service starts successfully.
    2015-02-26 11:55:15, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart
    2015-02-26 11:55:15, Info                  CBS    Startup processing thread terminated normally
    2015-02-26 11:55:15, Info                  CBS    Starting TiWorker initialization.
    2015-02-26 11:55:15, Info                  CBS    Ending TiWorker initialization.
    2015-02-26 11:55:15, Info                  CBS    Starting the TiWorker main loop.
    2015-02-26 11:55:15, Info                  CBS    TiWorker starts successfully.
    2015-02-26 11:55:15, Info                  CBS    Universal Time is: 2015-02-26 16:55:15.732
    2015-02-26 11:55:15, Info                  CBS    Loaded Servicing Stack v6.3.9600.17477 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.17477_none_fa2b7d3b9b36c7b4\cbscore.dll
    2015-02-26 11:55:15, Info                  CSI    00000001@2015/2/26:16:55:15.779 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffa25027f59 @0x7ffa25364a14 @0x7ffa2536424b @0x7ff6e824d69a @0x7ff6e824df4f @0x7ffa3c332053)
    2015-02-26 11:55:15, Info                  CBS    Could not load SrClient DLL from path: SrClient.dll.  Continuing without system restore points.
    2015-02-26 11:55:15, Info                  CBS    SQM: Initializing online with Windows opt-in: False
    2015-02-26 11:55:15, Info                  CBS    SQM: Cleaning up report files older than 10 days.
    2015-02-26 11:55:15, Info                  CBS    SQM: Requesting upload of all unsent reports.
    2015-02-26 11:55:15, Info                  CBS    SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
    2015-02-26 11:55:15, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
    2015-02-26 11:55:15, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
    2015-02-26 11:55:15, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
    2015-02-26 11:55:15, Info                  CBS    NonStart: Set pending store consistency check.
    2015-02-26 11:55:15, Info                  CBS    Session: 30429668_4270278432 initialized by client DISM Package Manager Provider.
    2015-02-26 11:55:15, Info                  CBS    Client specifies store corruption detect and repair.
    2015-02-26 11:55:15, Info                  CBS    Exec: Session processing started.  Client: DISM Package Manager Provider, Session(Store Corruption Detect/Repair): 30429668_4270278432
    2015-02-26 11:55:15, Info                  CBS    Reboot mark set
    2015-02-26 11:55:15, Info                  CBS    Winlogon: Registering for CreateSession notifications
    2015-02-26 11:56:04, Info                  CBS    Repr: CBS Store check completes
    2015-02-26 11:56:06, Info                  CSI    00000002 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0xb4f850f9c0
    2015-02-26 11:56:06, Info                  CSI    00000003 Creating NT transaction (seq 1), objectname [6]"(null)"
    2015-02-26 11:56:06, Info                  CSI    00000004 Created NT transaction (seq 1) result 0x00000000, handle @0x3a4
    2015-02-26 11:56:06, Info                  CSI    00000005 Poqexec successfully registered in [ml:26{13},l:24{12}]"SetupExecute"
    2015-02-26 11:56:06, Info                  CSI    00000006@2015/2/26:16:56:06.351 Beginning NT transaction commit...
    2015-02-26 11:56:06, Info                  CSI    00000007@2015/2/26:16:56:06.367 CSI perf trace:
    CSIPERF:TXCOMMIT;17922
    2015-02-26 11:56:06, Info                  CSI    00000008 CSI Store 777246073312 (0x000000b4f779e1e0) initialized
    2015-02-26 11:56:06, Info                  CSI    00000009 StoreCorruptionRepair transaction begun. WcpVersion: [l:78{39}]"6.3.9600.17477 (winblue_r5.141030-1500)".
    2015-02-26 11:56:06, Info                  CSI    0000000a@2015/2/26:16:56:06.382 Starting corruption detection (InnerFlags=5)
    2015-02-26 12:09:04, Info                  CSI    0000000b@2015/2/26:17:09:04.954 Corruption detection complete. numCorruptions = 0, Disp = 1.
    2015-02-26 12:09:04, Info                  CBS    Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
    2015-02-26 12:09:04, Info                  CBS    Repr: CSI Store check completes
    2015-02-26 12:09:04, Info                  CBS    Exec:Only CSI metadata corruption found, Process CSI repair.
    2015-02-26 12:09:04, Info                  CSI    0000000c Creating NT transaction (seq 2), objectname [6]"(null)"
    2015-02-26 12:09:04, Info                  CSI    0000000d Created NT transaction (seq 2) result 0x00000000, handle @0x360
    2015-02-26 12:09:05, Info                  CSI    0000000e@2015/2/26:17:09:05.01 Beginning NT transaction commit...
    2015-02-26 12:09:05, Info                  CSI    0000000f@2015/2/26:17:09:05.141 CSI perf trace:
    CSIPERF:TXCOMMIT;157546
    2015-02-26 12:09:05, Info                  CSI    00000010 StoreCorruptionRepair transaction completed.
    2015-02-26 12:09:05, Info                  CBS    Repr: Finished repairing CSI store.
    2015-02-26 12:09:05, Info                  CBS    Ensure CBS corruption flag is clear
    2015-02-26 12:09:05, Info                  CBS    Ensure WCP corruption flag is clear
    2015-02-26 12:09:05, Info                  CBS    
    =================================
    Checking System Update Readiness.


    Summary:
    Operation: Detect and Repair 
    Operation result: 0x0
    Last Successful Step: Entire operation completes.
    Total Detected Corruption: 0
    CBS Manifest Corruption: 0
    CBS Metadata Corruption: 0
    CSI Manifest Corruption: 0
    CSI Metadata Corruption: 0
    CSI Payload Corruption: 0
    Total Repaired Corruption: 0
    CBS Manifest Repaired: 0
    CSI Manifest Repaired: 0
    CSI Payload Repaired: 0
    CSI Store Metadata refreshed: True

    Total Operation Time: 829 seconds.

    2015-02-26 12:09:05, Info                  CBS    SQM: CheckSur: hrStatus: 0x0 [S_OK], download Result: 0x0 [S_OK]
    2015-02-26 12:09:05, Info                  CBS    Count of times corruption detected: 0
    2015-02-26 12:09:05, Info                  CBS    Seconds between initial corruption detections: -1
    2015-02-26 12:09:05, Info                  CBS    Seconds between corruption and repair: -1
    2015-02-26 12:09:05, Info                  CBS    SQM: Upload requested for report: CheckSurSqm, session id: 142858, sample type: Standard
    2015-02-26 12:09:05, Info                  CBS    SQM: Ignoring upload request because the sample type is not enabled: Standard
    2015-02-26 12:09:06, Info                  CBS    Reboot mark cleared
    2015-02-26 12:09:06, Info                  CBS    Winlogon: Deregistering for CreateSession notifications
    2015-02-26 12:09:06, Info                  CBS    Winlogon: Stopping notify server
    2015-02-26 12:09:06, Info                  CBS    Winlogon: Unloading SysNotify DLL
    2015-02-26 12:09:06, Info                  CBS    Exec: Processing complete, session(Corruption Repairing): 30429668_4270278432 [HRESULT = 0x00000000 - S_OK]
    2015-02-26 12:09:06, Info                  CBS    Session: 30429668_4270278432 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
    2015-02-26 12:09:06, Info                  CBS    Session: 30429670_3989005447 initialized by client DISM Package Manager Provider.


    Thursday, February 26, 2015 5:27 PM
  • Ok tried to do the Role Install from the PowerShell running as Administrator.

    Here is the results:

    PS C:\Users\administrator.MANAGED-PROGRAM> Install-windowsfeature -name AD-Domain-Services –IncludeManagementTools
    Install-windowsfeature : The request to add or remove features on the specified server failed.
    The operation cannot be completed, because the server that you specified requires a restart.
    At line:1 char:1
    + Install-windowsfeature -name AD-Domain-Services –IncludeManagementTools
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : DeviceError: (@{Vhd=; Credent...Name=localhost}:PSObject) [Install-WindowsFeature], Exce
       ption
        + FullyQualifiedErrorId : DISMAPI_Error__Failed_Reboot_Required,Microsoft.Windows.ServerManager.Commands.AddWindow
       sFeatureCommand

    Success Restart Needed Exit Code      Feature Result
    ------- -------------- ---------      --------------
    False   No             Failed         {}


    PS C:\Users\administrator.MANAGED-PROGRAM>

    That was run right after the DISM that said it was fixed and no reboot required .....

    I really need to get thee roles in place, any thoughts besides rebuilding the server?

    Curt Winter

    Microsoft Certified Professional

    Thursday, February 26, 2015 5:39 PM
  • Hi,

    So you could not add any server roles with the same issue?

    Any error in event viewer?

    Regards.


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Monday, March 9, 2015 7:18 AM
  • Vivian,

    I can not add the domain roles, I have not tried other roles, no messages regarding the add roles install in the event log.

    It get about 1/2 to 3/4 of the way through then says server requires a reboot and fails.

    Curt Winter


    Curt Winter

    Monday, March 16, 2015 3:24 PM