We've got 5 multidimensional cubes and access is granted by AD groups.
There is one role per cube with a "catch-all" role that is listed as "Read all cubes". This is a special role for our reporting team and allows them access to all the cubes. The other cubes are locked down to different AD groups with just access to that cube (read-only).
Unfortunately, the reporting team keep getting kicked off the cubes with an error along the lines of the following:-
"The database does not exist or you do not have access to it".
The simple solution (or so I've found) is to remove the relevant AD group from our "Read all cubes" role and put it back in. That solves the problem temporarily but I'd like to get to the bottom of it.
I've had a look in the msmdsrv.txt (but that only covers part of 2018 and nothing since although logging appears to be switched on) but that doesn't give me anything obvious.
I've had a (brief) look in the windows error logs but I'm not sure what I'm looking for.
Has anyone any ideas as to:-
a) why this is happening?
b) where I can find some more error logs to try and help me get to the bottom of it?
The really odd bit is that, if our reporting team (with access to everything) loses access, so does everyone else.
The solution of removing their AD group andreinserting it seems to solve the problem for everyone.
I'm guessing that it's something along the lines a (potentially) corrupt AD group but I don't want to ask our IT department to create a new one without some proof that it's definitely that causing the issue.
One other thing to note is that, because we have a DEV and PROD environment, we don't deploy the roles with the cubes if we make changes.
We have a job on the PROD server that creates the roles and assigns users and permissions.
That's on a schedule to run every day (which is probably overkill) but it ensures we don't forget to run it if we have to deploy the cube for any reason.
On a side note, is it possible to run a post-deployment script when deploying cubes?
Any help on this would be greatly appreciated.
Please feel free to ask for any pertinent info you may need.