Hi all,
I republished a Query Studio 'package' and all of a sudden when I go into a query stored in the publich folder I'm getting "You don't have access to this model." and I'm the %#$## admin!
What did I do?Ã, I'm afraid that come Monday morning other users are going to want to kick off queries and won't be able to.
It's been a really crappy day and this just finishes it nicely.Ã, If anyone has any ideas please post.Ã, I'll be checking in over the weekend.Ã,Â
Thanks.Ã, Ã, I believe there is a bottle of wine at home with my name on it. On Monday there just might be a chopping block with my name on it... :(
Sue
Hi Sue,
Sounds like you're having a bad day! :)
Sorry if I'm asking the obvious (but it never hurts to check!)
1. Did you change anything in the package permissions in Framework Manager before you republished? (in FM, right-click the package and use the 'Edit Package Access' option to check you have access to the package). If in doubt, allocate access to the 'everyone' role from the Cognos namespace and republish the package to see if it fixes the problem - if so then you can backtrack to what the security really should be set at.
2. What are the permissions on the package folder for the published package in Public folders? Do you have at least traverse, read and execute privileges granted (and not denied for another group or role you belong to!)?
Hope that bottle of wine has gone by now! It's late on Sunday here in the UK, but I guess you have another few good drinking hours before the end of the weekend on your side of the pond, so there may yet be time for another? ;)
Good luck!
MF.
Yep - Friday was an exceedingly bad day. Never did get to that bottle of wine though. :-(
Monday can only be better.
I did not change anything in the package security in FM. "Everyone" from the Cognos namespace has access. Permissions on the package are limited to IT support and Query users, both having Read, Execute and Traverse. I've added my personal account with full access and nothing changed.
The queries can be run, they just can't be opened in Query Studio to be modified.
Here's hoping for some Monday magic!
Sue
Hmmm - a strange error, then.
Could you try adding you personal account into the package security in FM too (just to see if it's something to do with the 'everyone' role)?
MF.
what about Report Studio. Are you finding the same errors there as well
NKT
Hi all - thanks for all of the suggestions. I finally logged a case over the weekend and talked to support on Monday.
I found out that this is a bug in anything below MR3. There is a hot fix for it, or there is MR3. I've been advised to skip the hot fix and got straight to MR3 since both require a full install anyway.
I was able to easily replicate the problem in development by republishing the query package a couple of times. The access gets screwed up somewhere and any query model built on that package just cannot be modified. It can be run and new queries can be created but old ones cannot be modified. It will continue to happen with query packages until the fix is applied and then the problem magically goes away.
So heads up to anyone who is still at MR1 or MR2.
Sue
Thanks Sue - the feedback on this is much appreciated! Glad you got to the bottom of it! :)
MF