Sometime after installing NPM12 RC2 the search voice calls resource failed to produce any calls. The telecom guys do not use this everyday so it was two weeks or so before they brought it to my attention. If I change the Call Time field to the last 30 days it shows calls from May 31 and earlier but no calls since then. I then checked the logs and was able to see the CDR data was being received by the call manager still. This unfortunately coincides with the application of NPM-RC2 and the RC 2 modules, I had previously upgraded to RC1 releases; however that may be just coincidental.
Last night I installed the final release version (4.2.4) hoping that it would resolve this problem. Unfortunately it did not, however I did notice the following error message
it instructed me to restart the module service engine, which I did at least twice and it simply caused the error to repeat each time.
I opened a case with support but was wondering if anyone here had previously run into this message and could give suggestions of things to check while i await a response from support. I am running Solarwinds Diagnostic tool right now to see if it is able to determine anything helpful.
Solved! Go to Solution.
Thanks for the link - fixed the issue for me.
A bit disconcerting however that I haven't had a response from support apart from the auto-generated case opened email... almost at 48 hour mark. Oddly enough, the status of this case is also "not started"!
Support was able to get me some instructions to fix the service not starting issue (described in OP). They were fairly straightforward and easy to follow, and after a server restart completely resolved the service failing to start issue.
However we are still troubleshooting the lack of current call information in the VOIP summary and Call search views.
The fix they gave me was based upon them reviewing my diagnostic log files and finding the exact error that was causing my issue, which may or may not be the exact same cause for yours. So you probably should just run the diagnostic utility and get the diagnostic package ready for them, they responded in less than 1 day after they had my logs.
Plus I imagine they would get super angry with me if I posted support communication in the forums, which may be misleading based upon the root cause of the issue being different. In addition, I would not want to jeopardize my thwack points as i am saving up for some really cool stuff.... and with the recent Venezuelan change in prices at the thwack store, i need them points.... 🙂
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.