If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Framework Manager has denied access to this model for this user.

Started by Dargie, 01 Mar 2011 09:05:45 AM

Previous topic - Next topic

Dargie

Hi, I am trying to add new users to see a report using SunOneLdap Access Manager 7.3 with C8.1  however when an existing user logs onto the report they can view and run the latest versions. But the new users cannot.

They have been added to the correct groups with access rights, ive even tried adding more and taking some away, this has not helped.

Below is the full error message we are getting.

thanks for any help

Dargie

RSV-SRV-0042 Trace back: RSReportService.cpp(658): QEException: CCL_CAUGHT: RSReportService::process() RSReportServiceMethod.cpp(168): QEException: CCL_RETHROW: RSReportServiceMethod::process(): asynchWait_Request RSASyncExecutionThread.cpp(520): QEException: RSASyncExecutionThread::checkException RSASyncExecutionThread.cpp(175): QEException: CCL_CAUGHT: RSASyncExecutionThread::run(): asynchRun_Request RSASyncExecutionThread.cpp(570): QEException: CCL_RETHROW: RSASyncExecutionThread::processCommand(): asynchRun_Request Execution/RSRenderExecution.cpp(507): QEException: CCL_RETHROW: RSRenderExecution::execute Execution/RSRenderExecution.cpp(713): QEException: CCL_RETHROW: RSRenderExecution::processActiveDocuments Assembly/RSDocAssemblyDispatch.cpp(229): QEException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssembly Assembly/RSLayoutAssembly.cpp(135): QEException: CCL_RETHROW: RSLayoutAssembly::assemble Assembly/RSDocAssemblyDispatch.cpp(289): QEException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchChildrenAssemblyForward Assembly/RSReportPagesAssembly.cpp(113): QEException: CCL_RETHROW: RSReportPagesAssembly::assemble Assembly/RSDocAssemblyDispatch.cpp(248): QEException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssembly Assembly/RSPageAssembly.cpp(236): QEException: CCL_RETHROW: RSPageAssembly::assemble Assembly/RSDocAssemblyDispatch.cpp(248): QEException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssembly Assembly/RSTableRowAssembly.cpp(115): QEException: CCL_RETHROW: RSTableRowAssembly::assemble Assembly/RSDocAssemblyDispatch.cpp(248): QEException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchAssembly Assembly/RSTableCellAssembly.cpp(94): QEException: CCL_RETHROW: RSTableCellAssembly::assemble Assembly/RSDocAssemblyDispatch.cpp(289): QEException: CCL_RETHROW: RSDocAssemblyDispatch::dispatchChildrenAssemblyForward RSQueryMgr.cpp(787): QEException: CCL_RETHROW: RSQueryMgr::getResultSetIterator RSQueryMgr.cpp(955): QEException: CCL_RETHROW: RSQueryMgr::createIterator RSQueryMgr.cpp(1516): QEException: CCL_RETHROW: RSQueryMgr::executeRsapiCommand QFSSession.cpp(1423): QEException: CCL_RETHROW: QFSSession::ProcessDoRequest() QFSSession.cpp(1421): QEException: CCL_CAUGHT: QFSSession::ProcessDoRequest() QFSSession.cpp(1392): QEException: CCL_RETHROW: QFSSession::ProcessDoRequest() QFSConnection.cpp(731): QEException: CCL_RETHROW: QFSConnection::Execute QFSQuery.cpp(112): QEException: CCL_RETHROW: QFSQuery::Execute v2 Source/QEResourceGateway.cpp(260): QEException: CCL_THROW: QE

AussiePete2011

Hi there,

Can these new users open the Model / package in Query Studio without any errors?
If they can't then check the model to see if object security has been applied and this would require a re-publish.

I realise this link is for 8.4.1 but this type of FM security hasn't change from 8.1 to 8.4.x
http://publib.boulder.ibm.com/infocenter/rentrpt/v1r0m1/index.jsp?topic=/com.ibm.swg.im.cognos.ug_fm.8.4.1.doc/ug_fm_i_SecurityinFrameworkManager.html

If they can access the Model in Query Studio, check to see if they can then create a report and save.
You haven't mentioned if these users are members of the Author role which gives them access to Report Studio but if they are can they access the Model / package in Report Studio without error?

These issues can be hard to track down so just start your investigations looking at what the user can do against the model / package. If they can access the package then the issue could be where the reports are located.  Not sure just yet.

Cheers
Peter B