Forum Discussion
Artur Schneider
Sep 20, 2018Copper Contributor
WAC 1808 File Copy errors and powershell disconnecting...
Hi, I have few gateway "WACs" deployed in our however there is some "behind the scenes" security mechanism that prevents me from: 1. Running powershell on a remote computer (it disconnect immedi...
Artur Schneider
Oct 15, 2018Copper Contributor
Jeff Woolslayer I followed troubleshooting guide yet no solution. While in version 1808 I was able to view events on remote machine, version 1809 just throws websocket error (though configuration of the server has not been changed) I pretty much gave up on trying to run powershell from WAC as it dies before it starts and there doesn't seem to be any contstructive feedback nor solution. Any news on that front?
Jeff Woolslayer
Microsoft
Oct 15, 2018The PowerShell tool has the same dependency on websockets as the events tool, so it makes sense that it's not working for you either. The actual managed server configuration doesn't impact Websocket support, it's your network environment. Any device on the network that routes or filters traffic can break websockets. Firewalls, switches, VPNs, etc...
Do you still happen to have the 1808 installer? If you are able to uninstall 1809 and reinstall 1808 to verify and describe the difference experience, we can follow up.
- Artur SchneiderNov 13, 2018Copper Contributor
I did downgrade to version 1808. Unfortunately still get Websocket/powershell not installed or not configured message when trying to access Event Viewer, PowerShell or RDP. Any new developements?
Thank You
- Artur SchneiderNov 13, 2018Copper Contributor
Here's event log entry for the error:
sessionId : 58ef4281-eb8a-453d-80ea-e5d9a0f9ddcc
eventId : Trace
level : Error
sourceName : msft.sme.event-viewer
source : appErrorHandler
timestamp : 1542105315958
message : WebSocket connection errors after retries.
stack : Error: WebSocket connection errors after retries.
at Object.next (https://cwoper02.diehlako.local/modules/msft.sme.event-viewer/main.0cfb0e6e09cf2ed5a19a.bundle.js:1:652382)
at WebSocket.r.onclose [as __zone_symbol__ON_PROPERTYclose] (https://cwoper02.diehlako.local/modules/msft.sme.event-viewer/main.0cfb0e6e09cf2ed5a19a.bundle.js:1:1889168)
at WebSocket.p (https://cwoper02.diehlako.local/modules/msft.sme.event-viewer/main.0cfb0e6e09cf2ed5a19a.bundle.js:1:1332859)
at e.invokeTask (https://cwoper02.diehlako.local/modules/msft.sme.event-viewer/main.0cfb0e6e09cf2ed5a19a.bundle.js:1:1323982)
at Object.onInvokeTask (https://cwoper02.diehlako.local/modules/msft.sme.event-viewer/main.0cfb0e6e09cf2ed5a19a.bundle.js:1:839313)
at e.invokeTask (https://cwoper02.diehlako.local/modules/msft.sme.event-viewer/main.0cfb0e6e09cf2ed5a19a.bundle.js:1:1323903)
at t.runTask (https://cwoper02.diehlako.local/modules/msft.sme.event-viewer/main.0cfb0e6e09cf2ed5a19a.bundle.js:1:1319160)
at t.invokeTask [as invoke] (https://cwoper02.diehlako.local/modules/msft.sme.event-viewer/main.0cfb0e6e09cf2ed5a19a.bundle.js:1:1325092)
at h (https://cwoper02.diehlako.local/modules/msft.sme.event-viewer/main.0cfb0e6e09cf2ed5a19a.bundle.js:1:1337048)
at WebSocket.f (https://cwoper02.diehlako.local/modules/msft.sme.event-viewer/main.0cfb0e6e09cf2ed5a19a.bundle.js:1:1337281)
moreEventData :