BMT-MDC-0001 Unable to publish

[paulym]

Hello All,

We have upgraded to Cognos 10 and I am getting a BMT-MDC-0001 Unable to publish error when atttempting to publish any packages to Cognos Connection from Framework Manager.

The error appears in the "publish package" process after navigating the entire publish wizard and clicking "Publish".

An package object is placed into Cognos Connection in the desired location.  It, however, does not function/is corrupt.

Any ideas/suggestions?

Thank you

[MFGF]

Are you running the same version of Framework Manager as you are of the BI Server (eg FM 10.1 vs BI 10.1.1)? Does the user ID you log in as from FM have appropriate capabilities to add packages into Cognos Connection?  Has the configuration of FM been checked to make sure it is using appropriate URIs for the C10 server?

Sorry - lots of questions!

MF.

[paulym]

Hello All,

Both the Client version of Framework Manager and BI Server are the same, 10.1.1.

The user ID has been granted System Administrator access with all capabilities and folder accesses.  The client places the "blue" package object in the desired folder location, it just is not usable.

Yes, the URIs for the gateway and dispatcher have been checked.

In Cognos Connection, when opening Report Studio using the new package, I am able to get a little further.  Now recieving:

MQP-ERR-0013

You do not have access to this model. Contact your security administrator

RSV-SRV-0042 Trace back:
RSReportService.cpp(722): MQPException: CCL_CAUGHT: RSReportService::process()
RSReportServiceMethod.cpp(263): MQPException: CCL_RETHROW: RSReportServiceMethod::process(): asynchRunSpecification_Request
RSASyncExecutionThread.cpp(808): MQPException: RSASyncExecutionThread::checkException
RSASyncExecutionThread.cpp(260): MQPException: CCL_CAUGHT: RSASyncExecutionThread::runImpl(): asynchRunSpecification_Request
RSASyncExecutionThread.cpp(864): MQPException: CCL_RETHROW: RSASyncExecutionThread::processCommand(): asynchRunSpecification_Request
RSMetadataService/RSMetadataMgr.cpp(185): MQPException: CCL_RETHROW: RSMetadataMgr::executeRequest()
RSQueryMgr.cpp(1569): MQPException: CCL_RETHROW: RSQueryMgr::executeRsapiCommand
RSQueryMgr.cpp(1559): MQPException: CCL_RETHROW: RSQueryMgr::executeRsapiCommand
RSQueryMgr.cpp(1549): MQPException: CCL_RETHROW: RSQueryMgr::executeRsapiCommand
QFSSession.cpp(1147): MQPException: CCL_RETHROW: QFSSession::ProcessDoRequest()
QFSSession.cpp(1145): MQPException: CCL_CAUGHT: QFSSession::ProcessDoRequest()
QFSSession.cpp(1102): MQPException: CCL_RETHROW: QFSSession::ProcessDoRequest()
QFSSession.cpp(1078): MQPException: CCL_RETHROW: QFSSession::ProcessDoRequest()
QFSConnection.cpp(788): MQPException: CCL_RETHROW: QFSConnection::Execute
QFSQuery.cpp(180): MQPException: CCL_RETHROW: QFSQuery::Execute
MQProviderQuery.cpp(229): MQPException: CCL_RETHROW: MQProviderQuery::MqpExecute
ZbMaProviderGateway.cpp(232): MQPException: CCL_THROW: MQP

[bi4u2]

When you publish the package, the second step on the publish wizard says 'Add Security' there are 2 tabs user access and administrator access. Is there anything other than 'No Security Defined' on these tabs?

[Bon]

I have the same issue.

I go through publishing process when I am updating an existing package, and in the end get this Unable to Publish error message. The package appears in the folder but when I run reports based on it I get this message

QE-DEF-0157          The model or package /content/folder............. does not exist or you are not allowed to use it because of security settings.

But I am an Administrator so I have all privilleges and am supposed to use everything

When I publish the package in new place (not updating a package) it is being published without errors. However, when I tried to copy and replace the old package with the new one I got a different type of error

RSV-SRV-0085          Could not find package capabilities associated with report model ... (path and name of the old version of the model, not the current one)...

I am a bit confused and do not know where to dig.  I suspect the following:

1. Something went wrong with package capabilites as it uses some data forom previous version of the model. Why I don't know

2. Something is wrong with security settings of packages, folders (but I checked -- looks ok)

Has anyone experienced things like this before? Any thoughts would be really appreciated.

Many thanks in advance

[akgusev]

Check the consistence of the folder, where you're going to publish package. Perhaps you have other element (not a Cognos BI package - it could be report or something like that) with the same name as your package name.

[Bon]

I have the same issue.

I go through publishing process when I am updating an existing package, and in the end get this Unable to Publish error message. The package appears in the folder but when I run reports based on it I get this message

QE-DEF-0157          The model or package /content/folder............. does not exist or you are not allowed to use it because of security settings.

But I am an Administrator so I have all privilleges and am supposed to use everything

When I publish the package in new place (not updating a package) it is being published without errors. However, when I tried to copy and replace the old package with the new one I got a different type of error

RSV-SRV-0085          Could not find package capabilities associated with report model ... (path and name of the old version of the model, not the current one)...

I am a bit confused and do not know where to dig.  I suspect the following:

1. Something went wrong with package capabilites as it uses some data forom previous version of the model. Why I don't know

2. Something is wrong with security settings of packages, folders (but I checked -- looks ok)

Has anyone experienced things like this before? Any thoughts would be really appreciated.

Many thanks in advance

Solved in my case by adding Consloidation and Foundation level query subjects which are connected to Presentation level subjects which are in the package. Not sure why it is happening, probably, because consistency of the model is broken and CFM does not like it.