This is a known bug. I've already opened a case for support. A date for a hotfix is not known
The error occurred after installing the latest MCP. The biggest mistake i could make.
We're still investigating / working on this defect (it's quite a strange one, thoug that makes it a bit interesting).
For any others affected by this, to short-cut things, get yourselves added to defect # 12921.
- Paul Hoffmann
LANDesk EMEA Technical Lead
How do I go about getting myself added to a defect number? This is impacting me.
Same problem with report CSV by mail : empty
LANDesk 9.0 SP2
Just an FYI, I've seen this at several clients. The reports do work if sent to an admin.
... Not in my
I'm admin LANDesk, and all the mails are empty :/
Apparently this is an issue that will be resolve in SP3. For nowthere is a workaround to get the reported emails to be created and sent correctly. The issue is only affecting users that have their scope inherited from a group instead of directly assigned.
1 - Check what users are getting email reports
1a - Open the Schedule report job
1b - Look at the users that should receive the report and take a note of them
2 - Update the users scopes
2a - Open the User Management tool.
2b - Locate one of your users/recipients and open its properties.
2c - Go to Scopes, and for every scope that is inherited, make sure it is selected as well in the Explicit scopes section, then click OK
2d - Repeat the steps 2a, 2b and 2c to all your users.
3 - Right click your reporting task and select 'Start now'.
All should then work as expected!
That worked out great. SP3 is so close now that isn't worth it to change everyone in our organization manually but this workaround helped us to get the email reports for certain key people.
Thanks a lot!
Do you know when SP3 is due out, and is this problem for sure solved in it?
I am having the exact same problem in 9.6 SP1. Please don't tell me this bug is still not resolved....
I actually have a case open with LANDesk regarding this. I'm on 9.5 SP2 and inherited scopes don't show up as parameters under reports. Explicitly assigning the scope to each user fixes this problem.