Wsman enumeration возникла ошибка код ошибки 2150858770

До сих пор я был почти в тупике с WinRM. Каждый раз, когда я пытаюсь установить какую-либо функцию с помощью диспетчера сервера, он зависает на «Запуск установки». Когда я устанавливаю компонент с помощью PowerShell, он работает нормально, только когда я открываю диспетчер сервера для настройки функции после установки, я получаю сообщение об ошибке «Не удалось открыть пул пространства выполнения». Настройка через PowerShell работает нормально.
WinRM уже настроен для удаленного управления на этом компьютере.
Затем в средстве просмотра событий я получаю эту ошибку, когда пытаюсь сделать что-либо с помощью диспетчера сервера / настройки DirectAccess:

Ошибка операции WSMan CreateShell, код ошибки 2150858770
И это не дает мне никакой информации, кроме этой. Это результат команды winrm get winrm / config: 

PS C:WindowsSystem32WindowsPowerShellv1.0> winrm get winrm/config
Config
    MaxEnvelopeSizekb = 500
    MaxTimeoutms = 60000
    MaxBatchItems = 32000
    MaxProviderRequests = 4294967295
    Client
        NetworkDelayms = 5000
        URLPrefix = wsman
        AllowUnencrypted = false
        Auth
            Basic = true
            Digest = true
            Kerberos = true
            Negotiate = true
            Certificate = true
            CredSSP = false
        DefaultPorts
            HTTP = 5985
            HTTPS = 5986
        TrustedHosts = fs.towerdevs.xyz
    Service
        RootSDDL = O:NSG:BAD:P(A;;GA;;;BA)(A;;GR;;;IU)S:P(AU;FA;GA;;;WD)(AU;SA;GXGW;;;WD)
        MaxConcurrentOperations = 4294967295
        MaxConcurrentOperationsPerUser = 1500
        EnumerationTimeoutms = 240000
        MaxConnections = 300
        MaxPacketRetrievalTimeSeconds = 120
        AllowUnencrypted = false
        Auth
            Basic = false
            Kerberos = true
            Negotiate = true
            Certificate = false
            CredSSP = true
            CbtHardeningLevel = Relaxed
        DefaultPorts
            HTTP = 5985
            HTTPS = 5986
        IPv4Filter = *
        IPv6Filter = *
        EnableCompatibilityHttpListener = false
        EnableCompatibilityHttpsListener = false
        CertificateThumbprint = 80 aa c1 69 11 9d 87 b8  d8 7a 20 b8 ff 76 d2 3ddb dc 7b 7f
        AllowRemoteAccess = true
    Winrs
        AllowRemoteShellAccess = true [Source="GPO"]
        IdleTimeout = 7200000
        MaxConcurrentUsers = 10
        MaxShellRunTime = 2147483647
        MaxProcessesPerShell = 25
        MaxMemoryPerShellMB = 1024
        MaxShellsPerUser = 30

и winrm enumerate winrm / config / listener: 

PS C:WindowsSystem32WindowsPowerShellv1.0> winrm enumerate winrm/config/listener
Listener
    Address = *
    Transport = HTTP
    Port = 5985
    Hostname
    Enabled = true
    URLPrefix = wsman
    CertificateThumbprint
    ListeningOn = 127.0.0.1, 169.254.164.229, 169.254.224.69, 192.168.1.109, ::1, fe80::5efe:169.254.164.229%17, fe80::5
efe:169.254.224.69%18, fe80::d13:6e93:f4dd:e045%12, fe80::84a1:52c5:715:a4e5%15, fe80::fdb7:1050:858e:9139%14

Listener
    Address = *
    Transport = HTTPS
    Port = 5986
    Hostname = fs.towerdevs.xyz
    Enabled = true
    URLPrefix = wsman
    CertificateThumbprint = 80 aa c1 69 11 9d 87 b8  d8 7a 20 b8 ff 76 d2 3ddb dc 7b 7f
    ListeningOn = 127.0.0.1, 169.254.164.229, 169.254.224.69, 192.168.1.109, ::1, fe80::5efe:169.254.164.229%17, fe80::5
efe:169.254.224.69%18, fe80::d13:6e93:f4dd:e045%12, fe80::84a1:52c5:715:a4e5%15, fe80::fdb7:1050:858e:9139%14

Сервер выполняет следующие роли / функции:

Роли:

AD CS (центр сертификации)

AD DS (контроллер домена)

DNS-сервер

Сервер файлов и хранилищ (файловый сервер и службы хранения)

Hyper-V

Удаленный доступ (DirectAccess и VPN)

Веб-сервер (IIS)

Службы развертывания Windows

Функции:

.NET Framework 3.5

.NET Framework 4.5

Bitlocker и сетевая разблокировка

Расширенное хранилище

Управление групповой политикой

Чернила и Службы рукописного ввода

Media Foundation

qWave

CMAK

RSAT

Пользовательские интерфейсы и инфраструктура

Внутренняя база данных Windows

Windows PowerShell

WPAS

Служба беспроводной локальной сети

Поддержка Wow64

И да, я несколько раз пытался сбросить конфигурацию WinRM и перезагрузиться. Если бы кто-нибудь мог помочь, он был бы очень признателен!

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

  • Question

  • We’ve been trying, and failing, to get Solaris Agents deployed from our SCOM server. The configuration is Windows 2008 R2, 1xRMS and 2xMS with SCOM R2 with the relevant updated (CU3, Cross platform, etc)

    However, when I try to deploy, I get this error on the MS:

    • Log Name:      Microsoft-Windows-WinRM/Operational
      Source:        Microsoft-Windows-WinRM
      Date:          13/10/2010 08:50:21
      Event ID:      142
      Task Category: Response handling
      Level:         Error
      Keywords:      Client
      User:          DOMAINOM-Action
      Computer:      SCOMSERVER
      Description:
      WSMan operation Enumeration failed, error code 2150858770
      Event Xml:
      <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
        <System>
          <Provider Name=»Microsoft-Windows-WinRM» Guid=»{A7975C8F-AC13-49F1-87DA-5A984A4AB417}» />
          <EventID>142</EventID>
          <Version>0</Version>
          <Level>2</Level>
          <Task>10</Task>
          <Opcode>2</Opcode>
          <Keywords>0x4000000000000002</Keywords>
          <TimeCreated SystemTime=»2010-10-13T07:50:21.141003800Z» />
          <EventRecordID>421</EventRecordID>
          <Correlation ActivityID=»{00000100-0000-0001-80E2-3FDE4965CB01}» />
          <Execution ProcessID=»2528″ ThreadID=»3032″ />
          <Channel>Microsoft-Windows-WinRM/Operational</Channel>
          <Computer>SCOMSERVER</Computer>
          <Security UserID=»S-1-5-21-3349825476-1904097674-2976221624-85503″ />
        </System>
        <EventData>
          <Data Name=»operationName»>Enumeration</Data>
          <Data Name=»errorCode»>2150858770</Data>
        </EventData>
      </Event>

    However, I cannot find anything anywhere that relates to the error code «2150858770».

    I can ping the Solaris server and it can ping the MS, but I cannot telnet to port 1270 on it in either direction.

    I’m totally stumped and this has taken up a lot of time…. Is there something I’m missing?

    • Moved by

      Wednesday, October 26, 2011 9:00 PM
      move to new forum (From:Cross Platform Solutions for System Center)

Answers

  • Hi,

    I have now resolved this — the Windows firewall wasn’t opened for the ports and the certificates were completely wrong — I found a powershell script that queried the server and reported a more meaningful error message.

    A little tweaking on the affected Solaris server and the problem has been resolved — The main problem was that the certificate name didn’t match what was expected — ironically, this is the message I’ve been getting all along, but repeated web searches returned
    the same suggestion that had no effect.

    Thanks

    James

    • Marked as answer by
      Daniele Muscetta
      Saturday, November 27, 2010 5:16 PM

Источник

I’m just about stumped with WinRM up to this point. Whenever I try to install any feature with the Server Manager, it hangs on «Starting Installation». When I install the feature with PowerShell, it works fine, only when I open up Server Manager to configure the feature after the installation I get a «failed to open the runspace pool» error. Configuring it via PowerShell works fine. Then, when I tried to configure DirectAccess with its Quick Start wizard, it gives me a «could not connect to the destination specified in the request» error.

Running «winrm quickconfig» produces this:

WinRM service is already running on this machine.
WinRM is already set up for remote management on this computer.
Then, in Event Viewer, I get this error when I try to do anything with Server Manager/configuring DirectAccess:

WSMan operation CreateShell failed, error code 2150858770
And it dosen’t give me any information except that. This is the output of winrm get winrm/config:

PS C:WindowsSystem32WindowsPowerShellv1.0> winrm get winrm/config
Config
    MaxEnvelopeSizekb = 500
    MaxTimeoutms = 60000
    MaxBatchItems = 32000
    MaxProviderRequests = 4294967295
    Client
        NetworkDelayms = 5000
        URLPrefix = wsman
        AllowUnencrypted = false
        Auth
            Basic = true
            Digest = true
            Kerberos = true
            Negotiate = true
            Certificate = true
            CredSSP = false
        DefaultPorts
            HTTP = 5985
            HTTPS = 5986
        TrustedHosts = fs.towerdevs.xyz
    Service
        RootSDDL = O:NSG:BAD:P(A;;GA;;;BA)(A;;GR;;;IU)S:P(AU;FA;GA;;;WD)(AU;SA;GXGW;;;WD)
        MaxConcurrentOperations = 4294967295
        MaxConcurrentOperationsPerUser = 1500
        EnumerationTimeoutms = 240000
        MaxConnections = 300
        MaxPacketRetrievalTimeSeconds = 120
        AllowUnencrypted = false
        Auth
            Basic = false
            Kerberos = true
            Negotiate = true
            Certificate = false
            CredSSP = true
            CbtHardeningLevel = Relaxed
        DefaultPorts
            HTTP = 5985
            HTTPS = 5986
        IPv4Filter = *
        IPv6Filter = *
        EnableCompatibilityHttpListener = false
        EnableCompatibilityHttpsListener = false
        CertificateThumbprint = 80 aa c1 69 11 9d 87 b8  d8 7a 20 b8 ff 76 d2 3ddb dc 7b 7f
        AllowRemoteAccess = true
    Winrs
        AllowRemoteShellAccess = true [Source="GPO"]
        IdleTimeout = 7200000
        MaxConcurrentUsers = 10
        MaxShellRunTime = 2147483647
        MaxProcessesPerShell = 25
        MaxMemoryPerShellMB = 1024
        MaxShellsPerUser = 30

And winrm enumerate winrm/config/listener:

PS C:WindowsSystem32WindowsPowerShellv1.0> winrm enumerate winrm/config/listener
Listener
    Address = *
    Transport = HTTP
    Port = 5985
    Hostname
    Enabled = true
    URLPrefix = wsman
    CertificateThumbprint
    ListeningOn = 127.0.0.1, 169.254.164.229, 169.254.224.69, 192.168.1.109, ::1, fe80::5efe:169.254.164.229%17, fe80::5
efe:169.254.224.69%18, fe80::d13:6e93:f4dd:e045%12, fe80::84a1:52c5:715:a4e5%15, fe80::fdb7:1050:858e:9139%14

Listener
    Address = *
    Transport = HTTPS
    Port = 5986
    Hostname = fs.towerdevs.xyz
    Enabled = true
    URLPrefix = wsman
    CertificateThumbprint = 80 aa c1 69 11 9d 87 b8  d8 7a 20 b8 ff 76 d2 3ddb dc 7b 7f
    ListeningOn = 127.0.0.1, 169.254.164.229, 169.254.224.69, 192.168.1.109, ::1, fe80::5efe:169.254.164.229%17, fe80::5
efe:169.254.224.69%18, fe80::d13:6e93:f4dd:e045%12, fe80::84a1:52c5:715:a4e5%15, fe80::fdb7:1050:858e:9139%14

The server runs these roles/features:

Roles:

AD CS (Certification Authority)

AD DS (Domain Controller)

DNS Server

File and Storages Server (File Server & Storage Services)

Hyper-V

Remote Access (DirectAccess and VPN)

Web Server (IIS)

Windows Deployment Services

Features:

.NET Framework 3.5

.NET Framework 4.5

Bitlocker and Network Unlock

Enhanced Storage

Group Policy Management

Ink & Handwriting Services

Media Foundation

qWave

CMAK

RSAT

User Interfaces and Infrastructure

Windows Internal Database

Windows PowerShell

WPAS

Wireless LAN Service

Wow64 Support

And yes, I have tried resetting the WinRM config and rebooting several times. If anyone could help, it would be much appreciated!

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

  • Question

  • We’ve been trying, and failing, to get Solaris Agents deployed from our SCOM server. The configuration is Windows 2008 R2, 1xRMS and 2xMS with SCOM R2 with the relevant updated (CU3, Cross platform, etc)

    However, when I try to deploy, I get this error on the MS:

    • Log Name:      Microsoft-Windows-WinRM/Operational
      Source:        Microsoft-Windows-WinRM
      Date:          13/10/2010 08:50:21
      Event ID:      142
      Task Category: Response handling
      Level:         Error
      Keywords:      Client
      User:          DOMAINOM-Action
      Computer:      SCOMSERVER
      Description:
      WSMan operation Enumeration failed, error code 2150858770
      Event Xml:
      <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
        <System>
          <Provider Name=»Microsoft-Windows-WinRM» Guid=»{A7975C8F-AC13-49F1-87DA-5A984A4AB417}» />
          <EventID>142</EventID>
          <Version>0</Version>
          <Level>2</Level>
          <Task>10</Task>
          <Opcode>2</Opcode>
          <Keywords>0x4000000000000002</Keywords>
          <TimeCreated SystemTime=»2010-10-13T07:50:21.141003800Z» />
          <EventRecordID>421</EventRecordID>
          <Correlation ActivityID=»{00000100-0000-0001-80E2-3FDE4965CB01}» />
          <Execution ProcessID=»2528″ ThreadID=»3032″ />
          <Channel>Microsoft-Windows-WinRM/Operational</Channel>
          <Computer>SCOMSERVER</Computer>
          <Security UserID=»S-1-5-21-3349825476-1904097674-2976221624-85503″ />
        </System>
        <EventData>
          <Data Name=»operationName»>Enumeration</Data>
          <Data Name=»errorCode»>2150858770</Data>
        </EventData>
      </Event>

    However, I cannot find anything anywhere that relates to the error code «2150858770».

    I can ping the Solaris server and it can ping the MS, but I cannot telnet to port 1270 on it in either direction.

    I’m totally stumped and this has taken up a lot of time…. Is there something I’m missing?

    • Moved by

      Wednesday, October 26, 2011 9:00 PM
      move to new forum (From:Cross Platform Solutions for System Center)

Answers

  • Hi,

    I have now resolved this — the Windows firewall wasn’t opened for the ports and the certificates were completely wrong — I found a powershell script that queried the server and reported a more meaningful error message.

    A little tweaking on the affected Solaris server and the problem has been resolved — The main problem was that the certificate name didn’t match what was expected — ironically, this is the message I’ve been getting all along, but repeated web searches returned
    the same suggestion that had no effect.

    Thanks

    James

    • Marked as answer by
      Daniele Muscetta
      Saturday, November 27, 2010 5:16 PM

Источник

I am having a very similar problem to this forum poster:
https://social.technet.microsoft.com/Forums/en-US/4ecb3b43-039a-4c34-9be5-5825bbf82817/microsoftwindowswindows-remote-management-error-id-142?forum=winservergen

I am unable to use administrative powershell to execute Enter-PSSession -ComputerName localhost.

I’ve followed all the usual troubleshooting guides I can find, and have found nothing that has worked thus far.

I am receiving the following error log under Event Viewer > Windows Event Logs > Applications and Services Logs > Microsoft > Windows > Windows Remote Management > Operational

WSMan operation CreateShell failed, error code 2150858770

The full detail of the event log entry below.

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
        <Provider Name="Microsoft-Windows-WinRM" Guid="{A7975C8F-AC13-49F1-87DA-5A984A4AB417}" /> 
        <EventID>142</EventID> 
        <Version>0</Version> 
        <Level>2</Level> 
        <Task>10</Task> 
        <Opcode>2</Opcode> 
        <Keywords>0x4000000000000002</Keywords> 
        <TimeCreated SystemTime="2016-08-17T03:57:00.300178400Z" /> 
        <EventRecordID>54475</EventRecordID> 
        <Correlation ActivityID="{0190BC48-F800-0001-A327-3BC239F8D101}" /> 
        <Execution ProcessID="7116" ThreadID="6424" /> 
        <Channel>Microsoft-Windows-WinRM/Operational</Channel> 
        <Computer>MACHINENAME.mydomain.net.nz</Computer> 
        <Security UserID="S-1-5-21-2875926586-1071052228-4104636349-1151" /> 
    </System>
    <EventData>
        <Data Name="operationName">CreateShell</Data> 
        <Data Name="errorCode">2150858770</Data> 
    </EventData>
</Event>

    

I have followed the Advice of Arthur_Li in the referenced forum post as follows:

Please perform the following steps to check the issue can be fixed.

Create the following Dwords under HKEY_LOCAL_MACHINESystemCurrentControlSetServicesHTTPParameters

  • MaxFieldLength
    • Dword
    • Value 65534 (Decimal)
  • MaxRequestBytes
    • Dword
    • Value 40000 (Decimal)

Reboot the server for the changes to take effect.

This advice appears to have worked for Funkyboogaloo. But it hasn’t resolved the problem I’m having.

I am experiencing this issue on Windows 2008 R2 Service Pack 1 64-bit.

  • Edited by

    Wednesday, August 17, 2016 4:18 AM

Источник

Понравилась статья? Поделить с друзьями:
  • Ws5 ошибка мегафон приложение
  • Wudfusbcciddrv ошибка 11 windows 10
  • Wsl ошибка при выполнении приложения сервера
  • Wow ошибка недостаточно памяти для обработки команды
  • Ws1ci ошибка 106