Hi there
we discovered that for some reason, NPP would not send pages anymore for a few days unless someone is actually logged on to the server.
This is completely new behavior, no update was actually installed on the server, nothing that we think of that could have affected this.

Hi,
We are using NPP and we are trying to send a page alert (received by SolarWinds Trap Viewer - NPM module)
Unfortunately, it looks like the "Dial Paging or SMS service" Action is not listed in the Actions list like if it was not "integrated" by default.
Is this a known thing?

the only one that is listed is the default Email / Page action (which can't, as you know send a page thru TAP)
Could you please advise if this is a NPP issue or SolarWinds? I guess I'm not the first one asking...
cheers

We are on the right track:
Activity log is clean | Activity Monitor window is clean, no more "not found" errors. GUI and SYSTEM instances running in parallel.

I'll touch-base tomorrow is required.
in such case, would you issue a new release to address those issues?
we did so many hacks and tried several adjustments, are they all covered by the 2 last version of npp.exe and nppdialer.exe you posted here?

1. NPP.log looks different since last Delivery Engine Stopped/Started
no more reference to COM3 conflicts.

2. still getting those on a 1 out 2 page sent basis. When this occurs, this is what we get in ACTIVITY MONITOR. Page sent @ 12:36 was successfully sent and modem hung up properly. but before next page goes out, there are a few "Attempting to reset modem" then the "Unable to open COM3 - port in use or doesn't exist" messages:

Yes, I've seen a bunch of those right away in the log.
so just to make sure, I went back to settings reapplied those and did a GET on
Category: connector
Name: close_com_on_hangup
and that returned -1 as expected.

give me sometime, I'll run more test as alerts come in and I'll update you.

update:
to have the GUI working as expected (sharing DB and LOG with SYSTEM instance) I had to remove the shortcut switch /localdb that you suggested to enable originally.

Now, GUI points to ORION used DB and LOG. This seems to be fine.

However, when having both the GUI running while ORION sends pages, this is generating tons of log entries about the COM port being used (npp.log is > 12M after just 5-6 pages). I don't remember having noticed that with previous version:

You rock guys! this worked. just a comment for others:
I had to specify target path with quotes, ie:
"C:\NotePager Pro\npp.exe" /localdb
and just replacing the executables, I didn't have to change/restore DB.
thanks.

Hi
We used to work with NPP 3 until we upgraded to NPP 5.03 on Win2012R2-64b server.
(Our setup is integrated with SolarWinds)
We noticed that because no-one was logged on to the server, NPP didn't fire pages alerts. They got queued until some one actually logged in to the server.
This was not the case in version 3.x, even though it was not set as a service.
Is there a way to address that?
thank you.