Windows Server 2012 R2 Datacenter Windows Server 2012 R2 Standard Windows Server 2012 R2 Essentials Windows Server 2012 R2 Foundation Windows 8.1 Enterprise Windows 8.1 Pro Windows 8.1 Еще…Меньше
Симптомы
Рассмотрим следующие сценарии:
-
Имеется устройство, которое поддерживает удаленное управление с помощью командлетов представление системы физического компьютера (PCSV).
-
Войдите в систему компьютера под управлением Windows Server 2012 R2 или Windows 8.1 и затем запустить командлет Windows PowerShell Get-PcsvDevice для удаленного управления устройством.
В этом случае появляется сообщение об ошибке, подобное приведенному ниже:
Get-PcsvDevice: WS-Management не удается обработать запрос. Операция не выполнена из-за ошибки HTTP. Ошибка HTTP (12152): сервер вернул ошибочный или нераспознанный ответ.
Решение
Для решения этой проблемы установите набор обновлений 2984006. Для получения дополнительных сведений щелкните следующий номер статьи базы знаний Майкрософт:
2984006 сентября 2014 накопительный пакет обновления для Windows RT 8.1, Windows 8.1 и Windows Server 2012 R2
Статус
Корпорация Майкрософт подтверждает, что это проблема продуктов Майкрософт, перечисленных в разделе «Относится к».
Дополнительные сведения
Дополнительные сведения о PCSV посетите следующий веб-узел корпорации Майкрософт:
Общие сведения о PCSVДополнительные сведения о командлетах PCSV посетите следующий веб-узел корпорации Майкрософт:
Общие сведения о командлетах PCSVДля получения дополнительных сведений о терминологии обновлений программного обеспечения щелкните следующий номер статьи базы знаний Майкрософт:
Описание 824684 Стандартные термины, используемые при описании обновлений программных продуктов Майкрософт
Нужна дополнительная помощь?
Нужны дополнительные параметры?
Изучите преимущества подписки, просмотрите учебные курсы, узнайте, как защитить свое устройство и т. д.
В сообществах можно задавать вопросы и отвечать на них, отправлять отзывы и консультироваться с экспертами разных профилей.
Windows Server 2012 R2 Datacenter Windows Server 2012 R2 Standard Windows Server 2012 R2 Essentials Windows Server 2012 R2 Foundation Windows 8.1 Enterprise Windows 8.1 Pro Windows 8.1 More…Less
Symptoms
Consider the follow scenario:
-
You have a hardware device that supports remote management by using the Physical Computer System View (PCSV) cmdlets.
-
You log on a computer that is running Windows 8.1 or Windows Server 2012 R2, and then you run the Windows PowerShell Get-PcsvDevice cmdlet to remotely manage the hardware device.
In this scenario, you receive an error message that resembles the following:
Get-PcsvDevice: WS-Management cannot process the request. The operation failed because of an HTTP error. The HTTP error (12152) is: The server returned an invalid or unrecognized response.
Resolution
To resolve this issue, install update rollup 2984006. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2984006 September 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.
More Information
For more information about PCSV, go to the following Microsoft website:
General information about the PCSVFor more information about the PCSV cmdlets, go to the following Microsoft website:
General information about the PCSV cmdletsFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Need more help?
Want more options?
Explore subscription benefits, browse training courses, learn how to secure your device, and more.
Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.
I am invoking Ws-Management calls to interact with iDRAC on Dell Server R620.
Since, I am using windows machine, I am invoking windows WinRM commands for this purpose.
Command:
winrm e http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_PhysicalDiskView -u:[username] -p:[password] -r:https:// [drac IP]/wsman -SkipCNCheck -SkipCACheck -encoding:utf-8 -a:basic
So I intermittently receive following errorred response as:
Message = WS-Management cannot process the request. The operation failed because of an HTTP error. The HTTP error (12152) is: The server returned an invalid or unrecognized response .
Error number: -2147023901 0x800703E3
The I/O operation has been aborted because of either a thread exit or an application request.
I have checked wireshark to monitor network and see consistent Frame Check Sequence Incorrect error, but this is intermittent
Has someone experienced something similar.
I have attempted to:
1. Disable Firewall on machine
2. Try multiple machines for same command
I have tested this on a Linux machine serving Cherokee pages and on a Windows 7 / IE10 machine.
Tested using your test scripts: https => post => https. When trying the same thing over http => post => http the browser literaly gave up on me. If you can help me reproduce this incident please reopen this ticket.
The https version did send an ok without problems. My guess is: this has nothing to do with Cherokee, but may have something to do with prototype.js / Ajax, etc. Looking at the Internet Explorer Developer Toolbar, there are some hints as «Ajax not being defined» (while it worked over HTTPS).
My hunch is: something in a virusscanner is causing this. Thus I disabled the virusscanner, and suddenly it worked.
So I tested:
https / https (always works)
http / http (virusscanner on: break, off: works)
http / https results in: «no response text» XMLHttpRequest: Networkerror 0x80070005, Access Denied (My guess this is CORS related).
I have a site using websockets secure (WSS) and works very well in chrome.
Testing in IE and Edge also works however in the browser console I get Network Error 12152 which will also trigger the websocket.addEventListener("error",function(){}) if implemented.
Everything actually works I just get this error which doesnt seem to break anything.
Error is triggered When socket is closed from Browser Side
Headers in EDGE
More Info: Example of the code I use
//connect via wss then
ws.addEventListener("error",function(event){ // this hits when Socket is closed})
ws.addEventListener("open",function(){
ws.addEventListener("message",function(event){
//do stuff
ws.Close()
})
})
To Confirm the problem further
I went to https://www.websocket.org/echo.html in edge the site which has the ability to test websocket connections. I made it connect to my server. which opens the connection without a problem. However in just the same way I have been getting problems with my code. This site also throws an error when I click the disconnect button. See Image Below. Is this a bug in IE/Edge?

My Server isnt disconnecting correctly?
I use the above site with the default destination (Their websocket server) and not mine. There are no errors. But when connecting to mine on disconnect there are errors.
What could be the problem?
Thanks

