Unable to run the report

[Gnani]

Hi cognos gurus,

Admin, User groups and Manager role are in cognos directory. Members exist in all groups and role. I have given access to Admin, User groups and Manager role. Members from Admin, User groups are able to run the reports but members from Manager role are not able to run the report. When run the report getting below error.

""QE-DEF-0356  Framework Manager has denied access to this model for this user. Please contact your security administrator.
DPR-ERR-2082 An error has occurred. Please contact your administrator. The complete error has been logged by CAF with SecureErrorID:2010-09-14-16:25:50.562-#5 ""

Can any one send suggestions here.

Thanks in adv
Gnani

[MFGF]

It sounds to me like Package Security has been applied in Framework Manager before the package was last published.  If you open the source model for the package in FM and look at the security defined on the package, I'd be willing to bet that the Manager role has been denied access.

Regards,

MF.

[Gnani]

Hi MFGF,
Yes....Manager role was denied access.
But later on i have given access to Manager role and republished the package. But still getting the same error.


Gnani..

[MFGF]

When you republished the package, did you have 'Model versioning' enabled by any chance?  If so, it will publish a new version of the package xml to the content store but leave the old version intact.  Any existing reports written against the old version will continue to use the old package definition until you open the reports in a studio and save them, at which point they will link to the new package version instead.

Could this be the problem?

Regards,

MF.

[Gnani]

Hi MF,
Thanks a lot...........
I have been struggling with issue for 3 days. It got solved with ur answer.
***U R GENIUS IN COGNOS***
I posted in many forums but no answer...
Again Thank You very much for ur solution....



Cheers,
Gnani..

[MFGF]

We're here to help!  :)

Glad you managed to get the problem sorted.  If you don't want to open each report in a studio, the alternative is to republish the package without Model Versioning enabled, and this will replace the package definition.

Thanks for getting back to us with an update - we really appreciate it!!  ;D

Regards,

MF.