Issues installing Message Queuing through server manager in add roles and features Wizard

Of late, we have been seeing errors when installing Message Queuing through server manager in add roles and features Wizard

Issue Statement:

Issues installing Message Queuing through server manager in add roles and features Wizard.

Errors shown:

  1. 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.
  2. Refresh Failed error.

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.”

The error will keep on happening no matter how many times you restart the server.

Additionally you may see the below error in the event viewer.

Event Logs : Failed to schedule Software Protection service for re-start at 2016-06-23T19:57:19Z. Error Code: 0x80070005.

Log Name :   Application

Source:   Microsoft-Windows-Security-SPP

Date:  6/22/2016 8:19:49 AM

Event ID:  16385

Task Category:  None

Level:   Error

Keywords:  Classic

User:  N/A

Computer:   HOEAPP538.upstreamaccts.XOM.com

Description:  Failed to schedule Software Protection service for re-start at 2016-06-23T19:56:49Z. Error Code: 0x80070005.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Microsoft-Windows-Security-SPP" Guid="{E23B33B0-C8C9-472C-A5F9-F2BDFEA0F156}" EventSourceName="Software Protection Platform Service" />

<EventID Qualifiers="49152">16385</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2016-06-22T13:19:49.000000000Z" />

<EventRecordID>34640449</EventRecordID>

<Correlation />

<Execution ProcessID="0" ThreadID="0" />

<Channel>Application</Channel>

<Computer>HOEAPP538.upstreamaccts.XOM.com</Computer>

<Security />

</System>

<EventData>

<Data>0x80070005</Data>

<Data>2016-06-23T19:56:49Z</Data>

</EventData>

</Event>

Cause:

The above issue might happen in the following situations.

  1. There is a chance that the Pending.xml file is corrupt which may lead to this issue.
  2. WMI corruption
  3. The temp folder is flooded with temp files with a huge file sizes.

Resolution:

  1. Rename the Pending.xml file to Pending_Old.xml, Reboot the Server and try the installation again. 
    • Click start and click on Accessories.
    • Right click on command prompt and select run as administrator.
    • At the command prompt type the following command: takeown /f C:\Windows\winsxs\pending.xml
    • Rename c:\windows\winsxs\pending.xml using the following command: Ren c:\windows\winsxs\pending.xml pending_old.xml
Note: 
The pending.xml file has a checkpoint value that tells Windows where the critical transactions end and the non-critical transactions begin.  When the system is starting, it looks into Pending.xml file to check for any pending transactions to continue. When you delete the checkpoint value in the pending.xml, or rename Pending.xml, Windows thinks it has nothing to do and just boots normally.  
 

2. Rebuild WMI,

3. Rename the TEMP folder under c:\windows\ and recreated a new TEMP folder for the refresh failed error and MSMQ installation completed successfully.