parameter boxes are empty

Hi,

I am have a reporting server which connects to a analysis server which connects to a sql server and a db2 server. I am using windows integrated security all the time except for the DB2 connection. That is a fixed username/password.

Reporting server (RS), analysis server (AS) and sql server are all on the same machine.

I created a local group and added the correct users to it.
I gave that group browse rights on the reports so that works correctly.

I created a role in AS and added that group to that role. Gave all read rights to that role.

I created a login for that group on the SQL server and gave that group db_datareader role.

When I connect as an administrator every reports runs fine.

When the test user connects they can browse the reports but the drop down boxes for the parameters are empty.

What goes wrong ?

With regards,

Constantijn Enders

Hi Constantjin

Im having the same problem...

I'm guessing when you say: <<Give all read rights to that role>>
you mean that you are setting the read rights in the cell data tab
when editing your role's security....

If I am correct, try the following:

Uncheck the Combo boxes on the cell data tab
(The one for 'Enable Read Permissions' and 'Enable Read Contingent Permissions')
and see the effect.
User will now be able to see everything.

It seemes that any attempt to set permissions on the cell data tab causes this
problem.

G

|||

Hi,

Unchecking did solve the problem.

I also removed them from SQL server and it works.

So basically what I had to do to give report users rights was
- create a role in AS
- put users/groups in that role
- give that role read rights on the cubes

and that's it.

Thanks for your quick help

Constantijn Enders

Parallel Database Backup

Hi,
We maintain master data in DB1 and transaction data in DB2. now we
wants to take backup of two databases(DB1 and DB2) parallely to avoid
inconsistency.
Thanks in advance
Regards
MahesHThis can't be done unless you were to kick all of your users and processes
off the two databases while you did the backup.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mahesh" <nrkmahesh@.gmail.com> wrote in message
news:1157635305.734572.5440@.m73g2000cwd.googlegroups.com...
> Hi,
> We maintain master data in DB1 and transaction data in DB2. now we
> wants to take backup of two databases(DB1 and DB2) parallely to avoid
> inconsistency.
> Thanks in advance
> Regards
> MahesH
>|||The only way to get transactionally consistent copies of two databases using
full recovery model is by using a transaction mark. A transaction mark
writes a mark into both log files using a distributed transaction so it is
in the same place in both logs. You can then back the databases and logs up
whenever you wish and recover both databases to the transaction mark if
necessary. Note that if you are using full recovery. you should almost
always be able to recover a database to the moment it crashed so this isn't
necessary except for the rare instance where the log file is lost.
Transaction marks are explained here:
http://msdn2.microsoft.com/en-us/library/ms187014.aspx
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Mahesh" <nrkmahesh@.gmail.com> wrote in message
news:1157635305.734572.5440@.m73g2000cwd.googlegroups.com...
> Hi,
> We maintain master data in DB1 and transaction data in DB2. now we
> wants to take backup of two databases(DB1 and DB2) parallely to avoid
> inconsistency.
> Thanks in advance
> Regards
> MahesH
>|||Roger,
Thanks for the good information about Transactional Marks.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:eZzISKp0GHA.2636@.TK2MSFTNGP06.phx.gbl...
> The only way to get transactionally consistent copies of two databases
> using full recovery model is by using a transaction mark. A transaction
> mark writes a mark into both log files using a distributed transaction so
> it is in the same place in both logs. You can then back the databases and
> logs up whenever you wish and recover both databases to the transaction
> mark if necessary. Note that if you are using full recovery. you should
> almost always be able to recover a database to the moment it crashed so
> this isn't necessary except for the rare instance where the log file is
> lost. Transaction marks are explained here:
> http://msdn2.microsoft.com/en-us/library/ms187014.aspx
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Mahesh" <nrkmahesh@.gmail.com> wrote in message
> news:1157635305.734572.5440@.m73g2000cwd.googlegroups.com...
>> Hi,
>> We maintain master data in DB1 and transaction data in DB2. now we
>> wants to take backup of two databases(DB1 and DB2) parallely to avoid
>> inconsistency.
>> Thanks in advance
>> Regards
>> MahesH
>

Parallel Database Backup

Hi,
We maintain master data in DB1 and transaction data in DB2. now we
wants to take backup of two databases(DB1 and DB2) parallely to avoid
inconsistency.
Thanks in advance
Regards
MahesHThis can't be done unless you were to kick all of your users and processes
off the two databases while you did the backup.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mahesh" <nrkmahesh@.gmail.com> wrote in message
news:1157635305.734572.5440@.m73g2000cwd.googlegroups.com...
> Hi,
> We maintain master data in DB1 and transaction data in DB2. now we
> wants to take backup of two databases(DB1 and DB2) parallely to avoid
> inconsistency.
> Thanks in advance
> Regards
> MahesH
>|||The only way to get transactionally consistent copies of two databases using
full recovery model is by using a transaction mark. A transaction mark
writes a mark into both log files using a distributed transaction so it is
in the same place in both logs. You can then back the databases and logs up
whenever you wish and recover both databases to the transaction mark if
necessary. Note that if you are using full recovery. you should almost
always be able to recover a database to the moment it crashed so this isn't
necessary except for the rare instance where the log file is lost.
Transaction marks are explained here:
http://msdn2.microsoft.com/en-us/library/ms187014.aspx
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Mahesh" <nrkmahesh@.gmail.com> wrote in message
news:1157635305.734572.5440@.m73g2000cwd.googlegroups.com...
> Hi,
> We maintain master data in DB1 and transaction data in DB2. now we
> wants to take backup of two databases(DB1 and DB2) parallely to avoid
> inconsistency.
> Thanks in advance
> Regards
> MahesH
>|||Roger,
Thanks for the good information about Transactional Marks.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:eZzISKp0GHA.2636@.TK2MSFTNGP06.phx.gbl...
> The only way to get transactionally consistent copies of two databases
> using full recovery model is by using a transaction mark. A transaction
> mark writes a mark into both log files using a distributed transaction so
> it is in the same place in both logs. You can then back the databases and
> logs up whenever you wish and recover both databases to the transaction
> mark if necessary. Note that if you are using full recovery. you should
> almost always be able to recover a database to the moment it crashed so
> this isn't necessary except for the rare instance where the log file is
> lost. Transaction marks are explained here:
> http://msdn2.microsoft.com/en-us/library/ms187014.aspx
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Mahesh" <nrkmahesh@.gmail.com> wrote in message
> news:1157635305.734572.5440@.m73g2000cwd.googlegroups.com...
>