Hi,

First of all, in case you are using the 2.1.1 version, you should upgrade to 2.1.2 as soon (see release history for more information) and see if it changes something.

Could you clarify what you mean by website admin accounts? Site collection owner or accounts that have full control over the web site?

What exactly do you mean by "adding full control permissions to your users"? By putting them into some group? On which site? Do the sub-sites inherit from parent permissions?

I can't say what's wrong but here is the tests I would surely do:

I would try to confirm that Windows Integrated security works as expected. I would run a non rollup report set up with Windows Integrated security using an account that has access to a subset of the list involved in the report. The report should display the subset data only. For the sake of completeness, I would run the same report again using an account that has full permission to the list.

I would try to see if a user that can't currently run the rollup report is able to execute the rollup report when having enough permissions. To make it simple, I would temporarily set the user accound as a secondary owner for the site collection and will run the rollup report again. That would be really surprising if with such permissions he still can't run the report considering that you seem to have users account that are already able to run it.

If after those previous tests, I still can't really get where things are going wrong, I would try to set up a small sample report in a test site collection with only one subsite and verify that things are working as expected when setting the appropriate permissions.

Let me know.

Regards,

---

Frederic LATOUR
ENESYS

Hi,

We could eliminate the error  so far with installing version 2.1.2!

Thanks.

Hi,

as I told you, with the new version the current rollup problems could be solved. But some other problems occurred with the rest of the reports:

• when trying to access the rest of my reports (=no rollup tag integrated) in my SharePoint application, I got the error message: "Dataset problems when processing...". I did not matter what account I chose for testing purpose - the error remained the same.
• I opened these reports in the report designer client to see what went wrong: but the report designer client had no processing problems.
• then I reopened the same reports in my updated report designer - with the new Enesys version: in this evironment I got the error message: "Query execution failed for dataset xyz. Column "ID" must have the same type within both Datatables for operation "join". Current types are "Int32" and "String". So this seems to be a type compatibility problem that just occurs with the new version.
• The column "ID" is the standard SharePoint column ID of a list. The other ID column is a lookup to this ID-field. 

How could I solve this problem? Is it possible, that the fact, that the reports have been created on a 32-Bit system and deployed to a 64-Bit-System have any influence on this problem? Is there any bug fix to this problem?

My current solution is to simply delete the Join between these two list including all related fields from this dataset. But this not a real solution of the problem, as I could need this join in other datasets in the future.

Hi,

I've found the join-error within the dataset-definition. Sorry. It was no Enesys bug. I could delete the error and now access the report in Sharepoint.

I coincidently detected this error when having installed the new version: the new version seems to have better / more precise error messages when such join errors happen. So I was a little bit confused, about this new message in the updated report designer, as with the prior Enesys version the report designer could not detect the error.