- Government |
- Customer Portal |
- Partners |
- Contact |
- English
SolarWinds uses cookies on our websites to facilitate and improve your online experience. By continuing to use our website, you consent to our use of cookies. For further details on cookies, please see our cookies policy.
Hide this message
Upcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor
Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.
Register now.
Updated 16th September 2016
Since the Upgrade to NPM 12 / SAM 6.2.4 we are getting multiple copies of the same scheduled report emailed to them, and other reports are not being sent out at all.
This is a known issue with Report Scheduler that are scheduled to run at the same time.
For example, Mike has 3 reports created which are emailed to him by 3 separate schedules. They are all configured to run at 6AM. He will get 3 (or more) of the same report at 6 am, but the other reports will not show up at all or he will receive one but the other reports will not show up at all. .
The logs will reflect that the report jobs started and finished as they should.
Edit the Schedules which have colliding times and reconfigure them so that they are staggered 5 minutes apart from each other to prevent this bug from effecting your enviroment.
This issue is resolved in 2016.2 (shipped with NPM 12.0.1 and SAM 6.3.0)