Several weeks ago my push notifications stopped being delivered. I cannot see why as I haven't made any changes (apart from updating PRTG). Here is the current situation:
PRTG version: 16.4.28.7421 Mobile client: Android v 16.4.1.1
My mobile is registered under the notification contacts.
I did try to remove and re-add the notification contact. I did try to uninstall and re-install the mobile app.
When checking the logs I find this around 2-3 minutes after the notification should've been sent:
Error sending "Push Notification": Unknown error response (Sensor/Source/ID: 2068/2066/1)
I should mention that I am running PRTG through an IIS proxy as described here: https://helpdesk.paessler.com/en/support/solutions/articles/760000635114613-using-windows-iis-as-ssl-proxy-for-prtg#reply-234049
Does anyone have any ideas?
Article Comments
Are there any news on this? One update has come out since then, but that doesn't appear to have fixed this. Any ETA?
Feb, 2017 - Permalink
Hi,
The issue seems to be a little bit more difficult than thought as not all expired trial license are affected. Please give us some more time to analyze the issue. As soon as the issue is fixed, I will write a statement in this topic. :)
Feb, 2017 - Permalink
already update to 17.1.28.1341 on February 15th but this problem still appear. anyone already try to uninstall and reinstall PRTG again without reinput sensor again?
Feb, 2017 - Permalink
Hi,
I'm afraid that it's still not possible to send push notifications with expired trial licenses. We will update the knowledge base article as soon as it is resolved.
Best Felix
Feb, 2017 - Permalink
I have this issue also. I thought in the past the freeware did not show as expired like it does now. I am sad to have upgraded. Can I downgrade till this issue has been resolved? Or maybe PRTG can cut a licenses key that are good for 100 sensors till this is resolved?
Feb, 2017 - Permalink
Dear tubular031
We have isolated the issue preventing freeware versions from sending push notifications and will release an update soon. For now, a preview version is already available. Please change the update channel in your PRTG to get this update.
Once you installed the 17.1.29, please change the update channel back to stable.
Feb, 2017 - Permalink
Just updated to 17.1.29.1359 and still no push notification. Under logs-notifications I see: Error sending "Push Notification": Unknown error response
That is the same response I was getting before the 17.1.29 update
Feb, 2017 - Permalink
Getting the below error under logs after upgrading to preview version.
Error sending "Push Notification": Access violation at address 00000000011A99B5 in module 'PRTG Server.exe'. Read of address 0000000000000000 (Sensor/Source/ID: 2731/0/1)
When tested manually, getting the below error under logs.
Error sending "Push Notification": Unknown error response
Do we need a reboot of the PRTG server?
Feb, 2017 - Permalink
I am sorry, upgraded to the preview version and the problem persists, reboot after the upgrade didn't help.
Logs saying
Error sending "Push Notification": Unknown error response (Sensor/Source/ID: 2276/0/1)
Feb, 2017 - Permalink
Just made the change to 17.1.29 still no push notifications and still the same error in logs. I also changed the license key to a new one but i think it needs re-installation. The trial expired is still there.
Feb, 2017 - Permalink
I have downloaded and installed version 17.1.29 from the Preview channel, unfortunately that version did not fix the problem for me. Now the log shows two errors when PRTG is trying to send Push notifications:
- Error sending Push notification "Unknown error response" (which was the problem all along) - Error sending Push notification "Access violation at address 00DCCC1C in module "PRTG Server.exe" Read of address 0000000.
I will wait for the stable update and install it when it comes out, hopefully this problem will finally be solved.
Feb, 2017 - Permalink
That is correct, I spoke too soon. We plan to relase a fix as preview, but that build is not yet available for download. It should be within the next days.
Feb, 2017 - Permalink
The PRTG preview release 17.1.29.1402 (available now) got that bugfix included.
Feb, 2017 - Permalink
Just installed 17.1.29.1402 and it worked! I was able to send a test push notification and my s7. WOOHOO! Thanks!!
Feb, 2017 - Permalink
Trying to download via preview channel version 17.1.29.1402 but it keeps downloading previous one 17.1.29.1359.
Feb, 2017 - Permalink
I installed yesterday the update, it was available late in the afternoon. Push notifications started working again. The test i made was to send test push notifications . Unfortunately last night i received two emails with errors and no push notifications from my sensors. Checking the log this morning found again the message
Error sending "Push Notification": Access violation at address 00DCCA3B in module 'PRTG Server.exe'. Read of address 00000000 (Sensor/Source/ID: 2206/2181/1)
I tried to send test push notifications and it was sending, but not from my sensors. I deliberately forced a device in error and got the emails to my account but not push notifications. As far as i can remember push notifications were coming before emails.
Now my device is down, i get the email for it but no push notifications.
Feb, 2017 - Permalink
Downloaded and installed version 17.1.29.1402, which solved the problem for me, too.
Feb, 2017 - Permalink
Dear pfournaris
If you get those errors in the next stable release as well, please contact support@paessler.com.
Feb, 2017 - Permalink
Same problem as pfournaris with 17.1.29.1402.
Test push notification works, but real notification gives me:
Error sending "Push Notification": Access violation at address 00DCCA3B in module 'PRTG Server.exe'. Read of address 00000000 (Sensor/Source/ID: 2369/0/1)
Feb, 2017 - Permalink
The "Down message" generates access violation, the "up message" works (V 17.1.29.1402)
Feb, 2017 - Permalink
Hi. I upgraded to 17.2.30.1825 and push notifications to my mobile phone no longer works. I deleted the notification contact that pertains to my phone from the software and removed the PRTG app from my phone. I reinstalled the app on my phone and a new unique token for my phone was added back to the notification contacts in the software. The log file shows this: Error sending "Push Notification": Unauthorized: License is invalid or maintenance expire. [4d37218d-2541-11e7-b96f-8bdb1e3fcecb] Please advise.
Thanks,
Apr, 2017 - Permalink
Dear dbarnett
Please check if you have a (trial) key entered in PRTG. (Setup / License / Update License.) This is necessary because now a freeware version is always an expired trial. You can get a trial key here: https://www.paessler.com/download/prtg-download/prtg
Apr, 2017 - Permalink
Dear dbarnett
Once the trial key expires, PRTG reverts to the 100 sensor freeware. (There are some nagging screens at first, but those will disappear automatically.) That means, it is enough to enter a trial key one time. You don't need to re-enter any key later.
The new approach, in which a freeware is always an expired trial, allows us to simplify the software activation process.
The freeware you get after 30 days, is still a full freeware, eligible to receive software updates.
Apr, 2017 - Permalink
Hi. But will I still be able to utilize the push notification function after the trial key expires?
Apr, 2017 - Permalink
Dear dbarnett
Yes. There was a bug in a previous PRTG version preventing that, but we found and fixed said bug. A PRTG freeware sends you push notifications.
Apr, 2017 - Permalink
Hi Team:
I notice that this error still occurs at version 23.1.82.2175+ should that be the case?
Error sending "Push Notification": No "Push" contact found
Apr, 2023 - Permalink
Hello,
this looks like a valid error message. The user you selected in the notification template, does it have push contact configured? That can be checked if that user logs into PRTG, opening menu Setup / Account Settings / Notification Contacts.
Apr, 2023 - Permalink
Hi there,
If you are using the freeware version with an expired trial, then the push notifications are currently not working. We are about to publish a fix as soon as possible. So please standby till the fix is released. (https://www.paessler.com/prtg/history/stable )
Jan, 2017 - Permalink