
Hi all,
I'm sure the answer to my question is right infront of me but I can't seem to find it. Hopefully one of you guys on here is less oblivious than me today.
I have spent the past few weeks creating all the various reports for our different teams and they've all been running fine in the Policy reporter application. This morning for the first time when I tried to run my newly created compliance reports in the web browser I got this message on all my reports only.
| Did not search any device configs, no devices were selected. |
Note: All the preconfigured reports that came with the app work just fine.
So under the 'Compliance' tab I hit the 'Update Now' button and this is what I got
(notice the last Update time)
| Last Update Time: |
| 30/11/2008 18:20:58 |
| Policy reports could not be run. Please contact your system administrator. |
Is this a setting that I have missed when building the reports/policies/rules? I have compared the standard reports that are runnning in the web browser against the ones I have created but I cannot find any significant difference.
Thanks for your time
Ciaran
Hi Ciaran,
Do you have any errors in the \Inetpub\Solarwinds\OrionWeb.log file concerning the execution of the policy reports? You might get some additional information about the problem into it.
Thanks,
Yann
Hi Yann,
how are you? I followed the path you provided in your reply but no file exists in that folder with that name. I also done a search and I couldn't find the 'OrionWeb.log file' anywhere on our Cirrus server. I've used this before on the Orion NPM server but a similar file doesn't seem to exist on our Cirrus installation.
If I run the configuration wizard might it remedy this?
I am good thanks :-).
Sorry I was thinking about the Orion NPM webconsole instead of the NCM one.
The log file of the NCM web console should be located there:
${ALLUSERSPROFILE}\Application Data\SolarWinds\Cirrus\Logging\CirrusWeb.log
Let me know if you find something interesting in it.
If I run the configuration wizard might it remedy this?
Not sure, as for the moment the error is quite vague for me.
Hi Yann,
I had a look at the weblog and I didn't see much that would indicate an issue. What I done was @ 08:33 I pressed the 'update now' button under the 'compliance tab'
and @ 08:34 I tried to run some of my own reports. I was hoping that by using this method I would be able to see 2 distinct errors or something over these 2 minutes. I have included the 2 minutes worth of data in an attachment with this reply, maybe you might see something that I didn't recognise?
Unfortunately, I could not find anything that would help in the file you attached...
You should open a ticket at this stage: http://www.solarwinds.com/support/ticket
Thanks,
Yann
Thats ok Yann,
I didn't think there was any errors in that file, that's why I thought it might have been some setting I had changed while setting up NCM. Anyway thanks for your efforts I will open a ticket today on this issue.
Cheers
Ciag, you might try restarting the NCM Polling Service (which also updates our policy cache) to see if that fixes this issue. Also, if you're not on the latest versions (5.1), I would suggest upgrading.
I didn't realise the polling service was linked to the policy cache. I had the polling service disabled as it was using excess amounts of CPU utilisation. when I switched it on the CPU went straight to 100% and just sits between 95% & 100%.
Is there a job that might be running in the background that might be causing this? something that is running because I haven't had the Polling service running in so long?
Can you try disabling node monitoring (File > Settings > Node Monitoring) and then try restarting the polling service?
If that still causes you problems, I'd recommend you update your case (or create a new one) about this problem. The polling service currently handles node monitoring and policy cache updates, but should definitely not be spiking your CPU like you described.
i am seeing this same behavior. I restared the service as specified and still no good.
Hi TimF,
what exactly is the behaviour are you seeing. If it's not being able to view report in web browser what solved the problem for us was to start the polling service in 'services'
Don't worry this will not start node monitoring if you have node monitoring disabled
There was more to this issue for us than just enabling the polling service if you are still running into difficulty let me know
I have the same issue. I restarted the polling service and that has seemed to fix it.
thanks,
pj