Can't send SMS messages from Solarwinds

anitazuri

Hi,

Can anyone please help, I've been back and forth with NotePager Pro (v5) support but getting no where.

The software is installed directly on our Solarwinds server and I can send/receive an SMS message directly from NotePager Pro.  So, the application is talking to the modem and getting the message out.  However, when I try to send a message via Solarwinds using 'Dial Paging or SMS' or 'Execute program' no message is sent/received.

From what I've read, if when you select 'Dial Paging or SMS' 'Page Recipients' you get a list of the recipients then Solarwinds knows about the NotePager Pro software and should work.  I do see the list of recipients and when I trigger a proper alert Solarwinds says the Action was executed successfully

I kind of feel that maybe I'm missing something simple but I've checked everything over so many times, I've also compared setup/settings to our current Live system which is using NotePager Pro version3 and working beautifully.  I've recently built a whole new system ready to go live in two weeks but this could potentially hold things up :-/

If anyone has had any experience in this area I would love your input.

Thanks

Anita Roberts

anitazuri

Thanks for the replies.

I now know the answer to this so thought I'd provide an update just in case anyone else comes across this issue.

I actually got this working by un-installing and re-installing NPP, I then opened the application by right clicking on the desktop icon and selected 'run as administrator'.  At this point SMS messages started to come through which was great!

However when the next on-call person needed to be moved over, they logged on to the server to make the change but the NPP application was not open on the screen so he double clicked the desktop icon which creates a second instance of the processes but also at this point the user profile (not administrator) is a virtualised instance which does not work for the reasons outlined below,  I've had great support from NotePager Pro and the guy who dealt with the issue gave me this explanation:-

Windows Server 2008, 2012 and 2016, as well as Windows 7, 8 and 10, virtualize each Windows user profile. So, what you think of as "HKEY_LOCAL_MACHINE" in the registry is really a user profile virtualized instance of what's contained in HKEY_LOCAL_MACHINE that's actually nested in the HKEY_USERS section of the registry. It's only administrators and programs that are allowed UAC authorization that get to access the 'real' HKEY_LOCAL_MACHINE - and Solarwinds absolutely requires everything to function out of the real registry location.

This can be resolved by creating a 'localdb' setting that will force all user profiles to reference the same local data, a reboot of the server is then required so that Solarwinds can read the new registry variables.  However, this doesn't always work, we are considering moving to PageGate as this can run as a Windows Service which means we could reboot the server and not have to start anything manually which is what we need.