Ошибка 10149 winrm

  • Remove From My Forums

  • Question

  • Dears,

    One -domain joined- server has Windows Remote Management not working even after running the command WINRM QUICKCONFIG and Enable-PSRemoting many times successfully.. I still can’t connect to this server using WMI commands.

    I checked the event log and found Event ID 10149 The WinRM service is not listening for WS-Management requests.

      — Windows Firewall is turned off and network traffic is opened between my client and all servers.

      — Other servers has WMI working fine and I can manage them.

      — The server is batched with last updates.

      — OS : Windows Server 2012 R2 Datacenter

      — Server role is Hyper-V host

    Please help what can we do to fix this issue..

    Thanks,

    A Seyam

Answers

  • I opened a ticket with Microsoft and the issue is now solved

    As I mentioned before I scanned the port 5985 and I found the server listening for this port on the loopback IP ‘127.0.0.1’ only not on all interfaces as it should.

    • And running the command ‘netsh http show iplisten‘ show the loopback
      IP address in the Listen Address of HTTP:

    IP addresses present in the IP listen list:

    ——————————————-

    127.0.0.1

    So the server was listening for HTTP requests on the loopback interface only

    • So we ran the command ‘netsh http delete iplisten 127.0.0.1‘ to delete
      it. After that we were able to connect to WinRM remotely.

    I’m not sure what may caused this issue but hopefully it may help someone else..

    • Marked as answer by

      Monday, November 16, 2015 9:06 AM

    • Edited by
      A Seyam
      Monday, November 16, 2015 9:06 AM

Источник
  • Remove From My Forums

  • Question

  • Dears,

    One -domain joined- server has Windows Remote Management not working even after running the command WINRM QUICKCONFIG and Enable-PSRemoting many times successfully.. I still can’t connect to this server using WMI commands.

    I checked the event log and found Event ID 10149 The WinRM service is not listening for WS-Management requests.

      — Windows Firewall is turned off and network traffic is opened between my client and all servers.

      — Other servers has WMI working fine and I can manage them.

      — The server is batched with last updates.

      — OS : Windows Server 2012 R2 Datacenter

      — Server role is Hyper-V host

    Please help what can we do to fix this issue..

    Thanks,

    A Seyam

Answers

  • I opened a ticket with Microsoft and the issue is now solved

    As I mentioned before I scanned the port 5985 and I found the server listening for this port on the loopback IP ‘127.0.0.1’ only not on all interfaces as it should.

    • And running the command ‘netsh http show iplisten‘ show the loopback
      IP address in the Listen Address of HTTP:

    IP addresses present in the IP listen list:

    ——————————————-

    127.0.0.1

    So the server was listening for HTTP requests on the loopback interface only

    • So we ran the command ‘netsh http delete iplisten 127.0.0.1‘ to delete
      it. After that we were able to connect to WinRM remotely.

    I’m not sure what may caused this issue but hopefully it may help someone else..

    • Marked as answer by

      Monday, November 16, 2015 9:06 AM

    • Edited by
      A Seyam
      Monday, November 16, 2015 9:06 AM
  • Remove From My Forums

  • Question

  • Dears,

    One -domain joined- server has Windows Remote Management not working even after running the command WINRM QUICKCONFIG and Enable-PSRemoting many times successfully.. I still can’t connect to this server using WMI commands.

    I checked the event log and found Event ID 10149 The WinRM service is not listening for WS-Management requests.

      — Windows Firewall is turned off and network traffic is opened between my client and all servers.

      — Other servers has WMI working fine and I can manage them.

      — The server is batched with last updates.

      — OS : Windows Server 2012 R2 Datacenter

      — Server role is Hyper-V host

    Please help what can we do to fix this issue..

    Thanks,

    A Seyam

Answers

  • I opened a ticket with Microsoft and the issue is now solved

    As I mentioned before I scanned the port 5985 and I found the server listening for this port on the loopback IP ‘127.0.0.1’ only not on all interfaces as it should.

    • And running the command ‘netsh http show iplisten‘ show the loopback
      IP address in the Listen Address of HTTP:

    IP addresses present in the IP listen list:

    ——————————————-

    127.0.0.1

    So the server was listening for HTTP requests on the loopback interface only

    • So we ran the command ‘netsh http delete iplisten 127.0.0.1‘ to delete
      it. After that we were able to connect to WinRM remotely.

    I’m not sure what may caused this issue but hopefully it may help someone else..

    • Marked as answer by

      Monday, November 16, 2015 9:06 AM

    • Edited by
      A Seyam
      Monday, November 16, 2015 9:06 AM
  • Remove From My Forums

  • Question

  • Dears,

    One -domain joined- server has Windows Remote Management not working even after running the command WINRM QUICKCONFIG and Enable-PSRemoting many times successfully.. I still can’t connect to this server using WMI commands.

    I checked the event log and found Event ID 10149 The WinRM service is not listening for WS-Management requests.

      — Windows Firewall is turned off and network traffic is opened between my client and all servers.

      — Other servers has WMI working fine and I can manage them.

      — The server is batched with last updates.

      — OS : Windows Server 2012 R2 Datacenter

      — Server role is Hyper-V host

    Please help what can we do to fix this issue..

    Thanks,

    A Seyam

Answers

  • I opened a ticket with Microsoft and the issue is now solved

    As I mentioned before I scanned the port 5985 and I found the server listening for this port on the loopback IP ‘127.0.0.1’ only not on all interfaces as it should.

    • And running the command ‘netsh http show iplisten‘ show the loopback
      IP address in the Listen Address of HTTP:

    IP addresses present in the IP listen list:

    ——————————————-

    127.0.0.1

    So the server was listening for HTTP requests on the loopback interface only

    • So we ran the command ‘netsh http delete iplisten 127.0.0.1‘ to delete
      it. After that we were able to connect to WinRM remotely.

    I’m not sure what may caused this issue but hopefully it may help someone else..

    • Marked as answer by

      Monday, November 16, 2015 9:06 AM

    • Edited by
      A Seyam
      Monday, November 16, 2015 9:06 AM

You might see either or both of these errors in your Event Viewer:

Log Name: System  Source: Microsoft-Windows-WinRM
Event ID: 10149    Level: Warning  Keywords: Classic

Description: The WinRM service is not listening for WS-Management requests.
User Action If you did not intentionally stop the service, use the following command to see the WinRM configuration: winrm enumerate winrm/config/listener

or

Log Name: System Source: Microsoft-Windows-WinRM
Event ID: 10155

Description: The WSMan service failed to read configuration of the following plugin:
Microsoft.ServerManager.
The WS-Management service cannot process the request. Configuration for plugin: “Microsoft.ServerManager” is corrupted. This plugin needs to be reconfigured or deleted. Use the following command to delete a plugin configuration

winrm delete http://schemas.microsoft.com/wbem/wsman/1/config/plugin?Name=xyz

Or use the following command to restore default plugin configuration. Note that all external plugins will be unregistered during this restore operation.

winrm invoke Restore http://schemas.microsoft.com/wbem/wsman/1/config/plugin @{}.

User Action Make sure this plugin configuration is valid.

Event ID 10155 WSMan service failed to readEvent ID 10149 Windows-WinRM

There are two common causes both with easy solutions:

FIX 1 – Add IP Addresses To The Monitor

See if ALL your IP’s are being monitored.  That includes your IPv4 address (or addresses if you have more than 1) AND the loopback 127.0.0.1.

You can do this by just running this command: netsh http show iplist

You can see in my case it was not configured to listen to any IP addresses:

netsh http show iplist WinRM Corrupt or Missing

If you need to add your IP’s just use netsh http add iplisten 127.0.0.1

netsh http add iplisten WinRM Corrupt or Missing

FIX 2 – Correct Registry

The registry entries for WinRM and WSMan should look like:

Registry Entry for Server Manager could not start the task due to the following error Failed to open

If your is empty or missing settings, here are the defaults taken from a fresh Windows Server 2012 R2 install:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMAN]
“StackVersion”=”2.0”

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANAutoRestartList]

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANCertMapping]

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANClient]

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANListener]

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANListener*+HTTP]

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANPlugin]

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANPluginEvent Forwarding Plugin]
“ConfigXML”=””

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANPluginMicrosoft.PowerShell]
“ConfigXML”=” “

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANPluginMicrosoft.PowerShell.Workflow]
“ConfigXML”=” “

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANPluginMicrosoft.PowerShell32]
“ConfigXML”=” “

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANPluginMicrosoft.Windows.ServerManagerWorkflows]
“ConfigXML”=” “

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANPluginSEL Plugin]
“ConfigXML”=” “

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANPluginWMI Provider]
“ConfigXML”=””

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANSafeClientList]
“WSManSafeClientList”=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,01

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANService]
“allow_remote_requests”=dword:00000001

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANWinRS]

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANWinRSCustomRemoteShell]

Note that I copied the setting above from THIS great website.

If you want to know more about WSMan, skim through THIS Microsoft Article

Enjoy!

Источник
  • Remove From My Forums

  • Question

  • Hi,

    I’m diggin into an issue with those two events on a newly installed Dell server. Directly after installation, it keeps logging event 10149:

    The WinRM service is not listening for WS-Management requests.
    User Action
    If you did not intentionally stop the service, use the following command to see the WinRM configuration:
    winrm enumerate winrm/config/listener

    The listener is configured and the service appears to be up and running. Nevertheless, the event is logged on every reboot. After installing the AD roles and promoting it to a DC (new forest, single server, AD&DNS) event 10154 showed up as well.

    I’d followed and tried dozens of solutions which — in general — all should lead to the same result: Granting the network service the right to create the SPNs by himself… Nothing helped. Finally, I’ve added the requested SPNs manually which
    succeeded in that way, that they became listed when querying setspn /l, however event 10154 stayed, as well as 10149 on every reboot.

    I’m running out of ideas. Any clues or solutions for this?

    Best Regards
    Holger

    • Edited by

      Monday, January 26, 2015 1:49 PM

Источник

You might see either or both of these errors in your Event Viewer:

Log Name: System  Source: Microsoft-Windows-WinRM
Event ID: 10149    Level: Warning  Keywords: Classic

Description: The WinRM service is not listening for WS-Management requests.
User Action If you did not intentionally stop the service, use the following command to see the WinRM configuration: winrm enumerate winrm/config/listener

or

Log Name: System Source: Microsoft-Windows-WinRM
Event ID: 10155

Description: The WSMan service failed to read configuration of the following plugin:
Microsoft.ServerManager.
The WS-Management service cannot process the request. Configuration for plugin: “Microsoft.ServerManager” is corrupted. This plugin needs to be reconfigured or deleted. Use the following command to delete a plugin configuration

winrm delete http://schemas.microsoft.com/wbem/wsman/1/config/plugin?Name=xyz

Or use the following command to restore default plugin configuration. Note that all external plugins will be unregistered during this restore operation.

winrm invoke Restore http://schemas.microsoft.com/wbem/wsman/1/config/plugin @{}.

User Action Make sure this plugin configuration is valid.

Event ID 10155 WSMan service failed to readEvent ID 10149 Windows-WinRM

There are two common causes both with easy solutions:

FIX 1 – Add IP Addresses To The Monitor

See if ALL your IP’s are being monitored.  That includes your IPv4 address (or addresses if you have more than 1) AND the loopback 127.0.0.1.

You can do this by just running this command: netsh http show iplist

You can see in my case it was not configured to listen to any IP addresses:

netsh http show iplist WinRM Corrupt or Missing

If you need to add your IP’s just use netsh http add iplisten 127.0.0.1

netsh http add iplisten WinRM Corrupt or Missing

FIX 2 – Correct Registry

The registry entries for WinRM and WSMan should look like:

Registry Entry for Server Manager could not start the task due to the following error Failed to open

If your is empty or missing settings, here are the defaults taken from a fresh Windows Server 2012 R2 install:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMAN]
“StackVersion”=”2.0”

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANAutoRestartList]

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANCertMapping]

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANClient]

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANListener]

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANListener*+HTTP]

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANPlugin]

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANPluginEvent Forwarding Plugin]
“ConfigXML”=””

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANPluginMicrosoft.PowerShell]
“ConfigXML”=” “

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANPluginMicrosoft.PowerShell.Workflow]
“ConfigXML”=” “

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANPluginMicrosoft.PowerShell32]
“ConfigXML”=” “

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANPluginMicrosoft.Windows.ServerManagerWorkflows]
“ConfigXML”=” “

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANPluginSEL Plugin]
“ConfigXML”=” “

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANPluginWMI Provider]
“ConfigXML”=””

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANSafeClientList]
“WSManSafeClientList”=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,01

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANService]
“allow_remote_requests”=dword:00000001

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANWinRS]

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWSMANWinRSCustomRemoteShell]

Note that I copied the setting above from THIS great website.

If you want to know more about WSMan, skim through THIS Microsoft Article

Enjoy!

Источник

The WinRM service is not listening for WS-Management requests.

 User Action
 If you did not intentionally stop the service, use the following command to see the WinRM configuration:

 winrm enumerate winrm/config/listener

Источник

Понравилась статья? Поделить с друзьями:
  • Ошибка 1014 windows 10
  • Ошибка 1013 шкода октавия
  • Ошибка 1013 приора
  • Ошибка 101 гугл
  • Ошибка 101 гранта 8 клапанная