Rank: Newbie
Groups: Registered
Joined: 7/6/2020(UTC) Posts: 8 
|
I get this error in the log when I try to send an PN.
It not an AppStore App.
Ausgeführt auf Server: Steuerelement Aktion von Schaltfläche Schaltfläche1:
Die Aktion Push-Benachrichtigung senden hat die folgenden Push-Benachrichtigungsdaten gesendet:
Server (optional): ''
Zu startende Lösung: ''
Senden an: Themen
Senden an: 'Escalation'
Titel: 'Eskalation'
Body: 'ESKALATIONSFEHLER: IL/IZL Innenlasche [Stanz-/ Materialfehler] ESKALATIONSFEHLER: IGLD Innenglied [falsch (Mischung)]'
Tag/Reduzieren-Schlüssel: ''
Payload
Schlüssel: 'AuftragNr'
Wert: '22884023'
Payload
Schlüssel: 'SAPOrderID'
Wert: '29662'
Das Senden der Push-Benachrichtigung ist mit folgendem Fehlercode fehlgeschlagen: 35.
Meldung: Schwerwiegender Fehler: I/O-Operation an der Datei 'https://fcm.googleapis.com/fcm/send' fehlgeschlagen.
Details:
Systemfehler 10054: An existing connection was forcibly closed by the remote host.
I/O-Fehler 35: schannel: failed to receive handshake, SSL/TLS connection failed
Das Senden der Push-Benachrichtigung ist mit folgendem Fehlercode fehlgeschlagen: 35.
Meldung: Schwerwiegender Fehler: I/O-Operation an der Datei 'https://fcm.googleapis.com/fcm/send' fehlgeschlagen.
Details:
Systemfehler 10054: An existing connection was forcibly closed by the remote host.
I/O-Fehler 35: schannel: failed to receive handshake, SSL/TLS connection failed
Sending push notification to 0 devices in time: 0.33 sec
|
|
|
|
|
|
Rank: Administration
Groups: Registered, Administrators Joined: 9/15/2014(UTC) Posts: 133  Was thanked: 18 time(s) in 18 post(s)
|
Hi!
Seems like your MobileTogether server cannot connect to the push notification server of Firebase (fcm.googleapis.com).
Maybe a firewall,... blocks such connections?
Which OS does your server use?
In case it's some Windows server, can you connect with "tracert fcm.googleapis.com" at the command line?
|
|
|
|
|
|
Rank: Newbie
Groups: Registered
Joined: 7/6/2020(UTC) Posts: 8
|
You're right!
I had a colleague check the firewall before but there was a misunderstanding.
It's okay now.
Thanks.
|
|
|
|
|
|
Rank: Newbie
Groups: Registered
Joined: 7/6/2020(UTC) Posts: 8
|
Now that the firewall settings are working I still have the problem that I cannot send a PN to the supposedly registered devices.
The log says that the device is registered for the receiving PN.
[Ausgeführt auf Server: Steuerelement Aktion von Schaltfläche Schaltfläche6:
Die Aktion Externen Push-Benachrichtigungsschlüssel registrieren hat den folgenden Push-Benachrichtigungsschlüssel gespeichert: 'Escalation']
But when I send the PN I get the message that no PN was sent to any device.
[There are no registered listeners for a push notification sent to external key(s) 'Escalation'
Sending push notification to 0 devices in time: 0.00 sec]
What am I doing wrong or have I forgotten?
|
|
|
|
|
|
Rank: Administration
Groups: Registered, Administrators Joined: 9/15/2014(UTC) Posts: 133 Was thanked: 18 time(s) in 18 post(s)
|
Hello Aiwis,
When sending the PN, please can you specify the "Solution to Start"?
Is it the same solution, which also registered the external key?
|
|
|
|
|
|
Rank: Newbie
Groups: Registered
Joined: 7/6/2020(UTC) Posts: 8
|
I have now entered the solution to be started.
(According to the description this should be optional.)
It is the solution registered with the external key.
Now I get this information.
[Die Aktion Push-Benachrichtigung senden hat die folgenden Push-Benachrichtigungsdaten gesendet:
Server (optional): 'aptvm02'
Zu startende Lösung: '/public/ChainAssemblySegmentLL/ChainAssemblyLL/AssemblyTestLL'
Senden an: Externe Schlüssel
Senden an: 'Escalation'
Titel: 'Eskalation'
Body: 'ESKALATIONSFEHLER: IL/IZL Innenlasche [Stanz-/ Materialfehler]'
Tag/Reduzieren-Schlüssel: ''
Payload
Schlüssel: 'AuftragNr'
Wert: '22884024'
Payload
Schlüssel: 'SAPOrderID'
Wert: '29664'
Push-Benachrichtigungen werden an 1 Android Gerät(e) gesendet.
Sending push notification to 2 devices in time: 0.36 sec
Aktionsausführung abbrechen]
Unfortunately I still cannot find a PN in the receiving solution / device.
|
|
|
|
|
|
Rank: Administration
Groups: Registered, Administrators Joined: 9/15/2014(UTC) Posts: 133 Was thanked: 18 time(s) in 18 post(s)
|
Hi! When sending to external keys, currently the solution must be specified (since different solutions could register the same external key, so this is not quite unique => we should update the UI here) reg. the last "Aktionsausführung abbrechen" - is there no further message? Or anything shown on the sending client (when trying PN for you today, I got a Firebase error once). Are you using the MobileTogether client or did you compile an AppStore app? Please also try to register the ExtKey again - somehow the registration sounds weird (sent to 1 Android device/sent to 2 devices). Would it be possible to look into your solution (e.g. via Support)?
|
|
|
|
|
|
Rank: Newbie
Groups: Registered
Joined: 7/6/2020(UTC) Posts: 8
|
Hello,
sorry if it took me a while to get back to you.
I noticed this morning that after logging in again to the WLAN the messages all arrived.
So the problem must have been the firewall settings.
We adjusted the settings and now everything works.
Thank you for the support, you really make a great piece of software
|
|
|
|
|
|
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
