You’re offline. This is a read only version of the page.
Announcements
25
Hello everyone,
we encounter a problem using web sockets from within the Field Service Mobile app (downloaded from Microsoft Store).
On some computers we are able to open a web socket connection to a web socket server on the same machine:
const socket = new WebSocket("ws://localhost:9001");
On other computers the connection attempts fail with timeout errors and the web sockets get closed.
We have exactly the same app version isntalled on both machines.
Opening a web socket connection in the Edge browser with the same locally hosted web socket server works fine on all computers.
Information of the computer where it works:
Microsoft Dynamics 365 Field Service app: 2022 release wave 2 enabled App name: Field Service Mobile Organization name: SICK DEV SANDBOX Server version: 9.2.22103.00194 App version: 3.22113.10.0.0 (1,1) Client version: 1.4.4957-2210.3 Session ID: 7009f132-9c4d-44d3-a825-c4fed844ea18 External correlation ID: 5ba6213a-0edb-4c3d-98bb-35a44a3710e2 Time: 2.12.2022 11:02:04 GMT+0100 (Mitteleuropäische Normalzeit) Edge Version: 107.0.1418.62 (Offizielles Build) (64-Bit) --------------
Information of the computer where it does not work (same as above):
Microsoft Dynamics 365 Field Service app: 2022 release wave 2 enabled App name: Field Service Mobile Organization name: SICK DEV Server version: 9.2.22103.00194 App version: 3.22113.10.0.0 (1,1) Client version: 1.4.4957-2210.3 Session ID: ede9a6cd-fc9f-4336-9e11-a15f98bed07c External correlation ID: 97b70327-a80c-4efc-854b-589ee7932260 Time: 12/2/2022 11:11:17 AM GMT+0100 (Central European Standard Time) Edge Version: 107.0.1418.62 (Official build) (64-bit) --------------
Are there some settings in the app that would prevent the socket connection?
Even though the connections work fine in MS Edge, we compared all Edge settings and found no difference there. The problem occurs in both, online and offline mode of the Field Service Mobile app.
Hi RoKon,
It seems to be related to the following details. I hope it helps.
Proxy servers and firewalls. Check if you have a proxy server or firewall that blocks WebSocket access. Try using a different web browser.
stackoverflow.com/.../websocket-connection-to-ws-mydomain-com8084-peer-id-123-failed-error-in-c
stackoverflow.com/.../websocket-connection-to-failed-error-in-connection-establishment-neterr-conn
#1
André Arnaud de Cal...
294,095
Super User 2025 Season 1
#2
Martin Dráb
232,866
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
