Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

When we try to run any report the popup keeps spinning and will not generate the report. If I make a copy and go through the same settings and submit, then run it generates the report.

ewk.jr

Any ideas?

Find more posts tagged with

Accepted answers

All comments

tony.johnson

Could you check the permissions for C:\ProgramData\SolarWinds\Orion?

ewk.jr

I can. What am I looking for?

tony.johnson

If you can check the folder permissions you may need to amend the permissions of “SolarWinds Orion Application Pool” account for C:\ProgramData\SolarWinds\Orion - add the right to Read, Write and Modify

ewk.jr

just wondering what happened to change this. existing reports worked last month.

vinay.by

Use this to check and repair

https://support.solarwinds.com/SuccessCenter/s/article/Check-permissions-using-the-Orion-Permission-Checker

__PRESENT

ewk.jr

That worked, thank you. I did upgrade but that was a couple of months ago. Any idea why this happens? we did a ha failover recently, is there any way that may have changed permissions?

vinay.by

Honestly I don't have an accurate answer to your query (it depends on what is being enforced on your SW VMs), we were always asked/told to exclude all folders related to SolarWinds from Antivirus / Defender / Security checks / guidelines that the company enforces on the VM's/Servers on which SolarWinds runs.

Yes, HA Failover could be the reason as to why you encountered this issue, probably it was running fine on the Primary poller and when you failed over to the standby poller this might have happened due to permission issues on the folders of your standby poller.

Hope this helps.

ewk.jr

ok, thanks. well, we did a failover to the standby for a bit then back to the primary where these permission issues happened. the failover was last week so we didnt notice anything until we ran a report.