Windows Server 2012 R2 DataCenter指定されたサーバーで使用可能な機能をリストする要求は失敗しました

10

サーバーにワイヤレスLANサービスを追加しようとしていますが、しばらく前にいくつかの更新プログラムをインストールしたため、最初に再起動する必要がありました。再起動後、次のエラーが発生しました：

指定されたサーバーで使用可能な機能をリストする要求は失敗しました。

サーバーマネージャー：

ここに画像の説明を入力してください

パワーシェル：

ここに画像の説明を入力してください

私は今どうすればいい？私は、C＃と他のいくつかのプログラミング言語だけのWindows Serverの経験はあまりありません。

— Nobleleader13245
ソース

1

Did you uh...try restarting it again? Windows has a funny way of sneaking in additional updates after a reboot.

— Nathan C

If there's a pending update, or feature install, you cannot install another feature until it restarts.

— Davidw

1

@NathanC I already restarted it 3 times now.... and there are no pending updates.

— Nobleleader13245

Disregard my last comment, it was for another question... I apologize...

— Brad Bouchard

Please check the server manager - there should be a flag that tells you why the server wasn't able to proceed.

— megamorf

0

Is it trying to add prerequisite features and restart first? I had a similar problem adding the WSUS role which was clashing when it also added the Windows Internal Database.

This guy mentions the error, but my solution was different. Instead of changing group policy, I had to actually provide the WID account access to the WID directory:

$WIDService = "MSSQL$MICROSOFT##WID"
$Acl = Get-Acl "D:\WID\Data"
$Acl.SetAccessRule((New-Object System.Security.AccessControl.FileSystemAccessRule($WIDService,"FullControl","Allow")))
Set-Acl "D:\WID\Data" $Acl

This isn't exactly your problem, but the symptom seems the same so it may lead you in the right direction at least.

— xXhRQ8sD2L7Z
ソース

0

I believe that the feature in powershell is named "wireless-networking", so the command would be "add-windowsfeature wireless-networking -restart"

— Mikael Dyreborg Hansen
ソース

0

I have received similarly obtuse messages from Windows before, when trying to install a service that is not supported on Windows Server Core.

If you are running Core edition, then the Wireless LAN service is not supported on core.

— Mark Henderson
ソース

0

I'm pretty sure it's a stuck pending reboot request.

Go to "C:\Windows\WinSxS" and check if there's a pending.xml file. Delete that file and try rebooting again. If you're unable to delete that file, try deleting it offline. If it's a virtual server, simply map its virtual disk somewhere and delete the file that way.

— Makorus
ソース