Can't list installed roles and features on Windows Server 2012 R2

I have two domain controllers and a single application server running SCOM stood up in a recently built domain/forest. I am attempting to view what roles and features are currently installed on each using an account with enterprise admin privileges and I'm getting an error. The Server Manager console shows a 'Manageability' issue of "Online - Cannot get role and feature data". When I try to run the 'Add Roles and Features Wizard' I get the message of "The request to list features available on the specified server failed". When I attempt to run 'Get-WindowsFeature' from powershell, I get the following:

PS C:\windows\system32> Get-WindowsFeature Get-WindowsFeature : The request to list features available on the specified server failed.
A DISM session could not be opened.
The request is not supported. Error: 0x80070005 At line:1 char:1
+ Get-WindowsFeature
+ ~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (@{Vhd=; Credent...Name=localhost}:PSObject) [Get-WindowsFeature], Dep
    + FullyQualifiedErrorId : DISMAPI_Error__Failed_Opening_Dism_Session,Microsoft.Windows.ServerManager.Commands.GetW

Open in new window

The logs for 'ServerManager-DeploymentProvider' doesn't list any helpful information - The four error events I'm getting are 107, 113, 1315, 1537.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Nagendra Pratap SinghDesktop Applications SpecialistCommented:
Try logging in with another admin account. This account may have some restrictions.


Server Manager cannot get role and feature inventory data from the target server. The user might not have access rights to role and feature data on the target server, or the data might not be readable. To grant role and feature inventory data access rights to standard (non-Administrator) users, administrators should run the Enable-ServerManagerStandardUserRemoting cmdlet on the target server. For more information about how to use this cmdlet (and disable standard user management access when it is no longer needed), see the cmdlet Help topic for Enable-ServerManagerStandardUserRemoting.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Lionel MMSmall Business IT ConsultantCommented:
This sounds like more than a permissions issue--sounds like your "catalog" of features is corrupted. Check out this link for an explanation and suggestions and run this command
dism /online /cleanup-image /restorehealth
This issue is usually caused by a corruption in the Component Based Servicing Subsystem (DCOM).  It is generally related to incorrect permissions.  In order to solve it, you will want to change the Default Authentication level to "connect".

1. Open the Component Services management console


2. Browse to the location Component Services --> Computers --> MyComputer.


3. Right-click on the MyComputer branch and select '[b]Properties[/b]'.


4. Go to Default properties Tab and make sure that default authentication level is set to '[b]Connect[/b]' and Default Impersonation level is set to '[b]Identify[/b]'.

Capture.JPGMicrosoft has a TID that discuss this issue further:
An error message occurs when you click Roles under the Server Manager console in Windows Server 2008
kj_syenceAuthor Commented:
All good recommendations, but my problem dealt with host intrusion software. I still gave out points for those that provided a solution. Thanks!
Mike HowardCommented:
Also check available drive space on system drive.  In my case I had about 130 archived security log files (at 300M each) choking the drive.  Moved them off and was able to start management from remote system.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.