Product:
Cognos BI 10.2.2
Microsoft Windows 2012 R2 server
Microsoft SQL 2014 database
Symptom:
On a new installed Cognos BI 10.2.2 where you have upgraded an old Content store from Cognos BI 10.1.1 you get an error message when you in Cognos connection go to Administer IBM Cognos content and look at Current Activities.
Error message:
SOAPFaultException
CNC-MON-0024 Monitor Service paging error: Invalid column name ‘TENANT_ID’.
com.cognos.portal.fragment.server.SOAPFaultException: CNC-MON-0024 Monitor Service paging error: Invalid column name ‘TENANT_ID’.
at com.cognos.portal.fragment.service.ServiceEnvironment.getBiBusTargetStream(ServiceEnvironment.java:543)
at com.cognos.portal.fragment.service.ServiceEnvironment.getLocalTargetStream(ServiceEnvironment.java:330)
at com.cognos.portal.fragment.Environment.getTargetStream(Environment.java:624)
at com.cognos.portal.fragment.SynchronizedEnvironment.getTargetStream(SynchronizedEnvironment.java:265)
at com.cognos.portal.fragment.SynchronizedEnvironment.getTargetStream(SynchronizedEnvironment.java:265)
at com.cognos.portal.fragment.server.document.DocumentFactoryImpl.createDocument(DocumentFactoryImpl.java:132)
at com.cognos.portal.fragment.server.document.DocumentRequest.runImpl(DocumentRequest.java:80)
at com.cognos.portal.fragment.server.document.RequestExecutor$Request.run(RequestExecutor.java:58)
at com.cognos.portal.thread.DefaultRerunnable.run(DefaultRerunnable.java:65)
at com.cognos.portal.thread.RerunnableThread.run(RerunnableThread.java:109)
<SOAP-ENV:Fault xmlns:SOAP-ENV=”http://schemas.xmlsoap.org/soap/envelope/”><faultcode xmlns=””>soapenv:Server</faultcode><faultstring>CNC-BAL-0503 The Server has failed.</faultstring><detail><detail><ns1:exception xmlns:ns1=”http://developer.cognos.com/schemas/bibus/3/”><ns1:severity>error</ns1:severity><ns1:errorCode>CNC-BAL-0502 Error Number: MSG_MS_PAGING_ERROR
</ns1:errorCode><ns1:message><ns1:messageString>CNC-MON-0024 Monitor Service paging error: Invalid column name ‘TENANT_ID’.</ns1:messageString><ns1:nestingLevel>0</ns1:nestingLevel></ns1:message></ns1:exception></detail></detail></SOAP-ENV:Fault>
at com.cognos.portal.soap.impl.SOAPConnectionImpl.handleFault(SOAPConnectionImpl.java:307)
at com.cognos.portal.soap.impl.SOAPConnectionImpl.readResponse(SOAPConnectionImpl.java:251)
at com.cognos.portal.soap.impl.SOAPConnectionImpl.processResponse(SOAPConnectionImpl.java:210)
at com.cognos.portal.soap.impl.BusConnectionImpl.execute(BusConnectionImpl.java:144)
at com.cognos.portal.fragment.service.ServiceEnvironment.getBiBusTargetStream(ServiceEnvironment.java:515)
at com.cognos.portal.fragment.service.ServiceEnvironment.getLocalTargetStream(ServiceEnvironment.java:330)
at com.cognos.portal.fragment.Environment.getTargetStream(Environment.java:624)
at com.cognos.portal.fragment.SynchronizedEnvironment.getTargetStream(SynchronizedEnvironment.java:265)
at com.cognos.portal.fragment.SynchronizedEnvironment.getTargetStream(SynchronizedEnvironment.java:265)
at com.cognos.portal.fragment.server.document.DocumentFactoryImpl.createDocument(DocumentFactoryImpl.java:132)
at com.cognos.portal.fragment.server.document.DocumentRequest.runImpl(DocumentRequest.java:80)
at com.cognos.portal.fragment.server.document.RequestExecutor$Request.run(RequestExecutor.java:58)
at com.cognos.portal.thread.DefaultRerunnable.run(DefaultRerunnable.java:65)
at com.cognos.portal.thread.RerunnableThread.run(RerunnableThread.java:109)
Root Cause:
<SOAP-ENV:Fault xmlns:SOAP-ENV=”http://schemas.xmlsoap.org/soap/envelope/”><faultcode xmlns=””>soapenv:Server</faultcode><faultstring>CNC-BAL-0503 The Server has failed.</faultstring><detail><detail><ns1:exception xmlns:ns1=”http://developer.cognos.com/schemas/bibus/3/”><ns1:severity>error</ns1:severity><ns1:errorCode>CNC-BAL-0502 Error Number: MSG_MS_PAGING_ERROR
</ns1:errorCode><ns1:message><ns1:messageString>CNC-MON-0024 Monitor Service paging error: Invalid column name ‘TENANT_ID’.</ns1:messageString><ns1:nestingLevel>0</ns1:nestingLevel></ns1:message></ns1:exception></detail></detail></SOAP-ENV:Fault>
at com.cognos.portal.soap.impl.SOAPConnectionImpl.handleFault(SOAPConnectionImpl.java:307)
at com.cognos.portal.soap.impl.SOAPConnectionImpl.readResponse(SOAPConnectionImpl.java:251)
at com.cognos.portal.soap.impl.SOAPConnectionImpl.processResponse(SOAPConnectionImpl.java:210)
at com.cognos.portal.soap.impl.BusConnectionImpl.execute(BusConnectionImpl.java:144)
at com.cognos.portal.fragment.service.ServiceEnvironment.getBiBusTargetStream(ServiceEnvironment.java:515)
at com.cognos.portal.fragment.service.ServiceEnvironment.getLocalTargetStream(ServiceEnvironment.java:330)
at com.cognos.portal.fragment.Environment.getTargetStream(Environment.java:624)
at com.cognos.portal.fragment.SynchronizedEnvironment.getTargetStream(SynchronizedEnvironment.java:265)
at com.cognos.portal.fragment.SynchronizedEnvironment.getTargetStream(SynchronizedEnvironment.java:265)
at com.cognos.portal.fragment.server.document.DocumentFactoryImpl.createDocument(DocumentFactoryImpl.java:132)
at com.cognos.portal.fragment.server.document.DocumentRequest.runImpl(DocumentRequest.java:80)
at com.cognos.portal.fragment.server.document.RequestExecutor$Request.run(RequestExecutor.java:58)
at com.cognos.portal.thread.DefaultRerunnable.run(DefaultRerunnable.java:65)
at com.cognos.portal.thread.RerunnableThread.run(RerunnableThread.java:109)
Possible Solution:
http://www-01.ibm.com/support/docview.wss?uid=swg22000976
The tables in Content store can be corrupt.
Take a backup of the Database before doing any changes.
Stop the Cognos BI service.
Get the drop table SQL script from folder E:\Program Files\ibm\cognos\c10_64\configuration\schemas\delivery\sqlserver\NC_DROP_MS.sql
Looks like this:
—
— Licensed Materials – Property of IBM
—
— BI and PM: JSM
—
— (c) Copyright IBM Corp. 2003, 2015.
—
— US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
—
——————————————————————————-
— NC_DROP_MS.sql * DO NOT EDIT * Data Store Version: 1032
——————————————————————————-
ALTER TABLE NC_JOBQUEUE
DROP CONSTRAINT PN_JOBQUEUE
ALTER TABLE NC_MESSAGELINE
DROP CONSTRAINT F1N_MESSAGELINE
ALTER TABLE NC_MESSAGELINE_ELEMENT
DROP CONSTRAINT F1N_MESSAGELINE_EL
ALTER TABLE R_MESSAGESTRUCT_TASK
DROP CONSTRAINT F2R_MESSAGESTRUCT_
ALTER TABLE R_MESSAGESTRUCT_TASK
DROP CONSTRAINT F1R_MESSAGESTRUCT_
ALTER TABLE NC_METRICS
DROP CONSTRAINT PN_METRICS
ALTER TABLE R_MSGSTRUCT_RECIPIENT_DELIVINF
DROP CONSTRAINT F3R_MSGSTRUCT_RECI
ALTER TABLE R_MSGSTRUCT_RECIPIENT_DELIVINF
DROP CONSTRAINT F1R_MSGSTRUCT_RECI
ALTER TABLE NC_SDS_INSTANCE
DROP CONSTRAINT PN_SDS_INSTANCE
ALTER TABLE NC_TASKSCHEDULE
DROP CONSTRAINT F1N_TASKSCHEDULE
ALTER TABLE R_TASKSCHEDULE_SCHEDULE
DROP CONSTRAINT F2R_TASKSCHEDULE_S
ALTER TABLE R_TASKSCHEDULE_SCHEDULE
DROP CONSTRAINT F1R_TASKSCHEDULE_S
DROP TABLE NC_CONFIGURATION
DROP TABLE NC_CTMAP
DROP TABLE NC_DB_VERSION
DROP TABLE NC_DELIVERYADDRESS
DROP TABLE NC_EVENTSTATUS
DROP TABLE NC_JMSQUEUE
DROP TABLE NC_JOBQUEUE
DROP TABLE NC_MESSAGELINE
DROP TABLE NC_MESSAGELINE_ELEMENT
DROP TABLE NC_MESSAGESTRUCT
DROP TABLE NC_METRICS
DROP TABLE NC_OBJECTCATALOGUE
DROP TABLE NC_OBJECTID
DROP TABLE NC_PERMISSION
DROP TABLE NC_RECIPIENT
DROP TABLE NC_SCHEDULE
DROP TABLE NC_SCHEDULE_QUEUE
DROP TABLE NC_SDS_INSTANCE
DROP TABLE NC_TASK
DROP TABLE NC_TASKSCHEDULE
DROP TABLE NC_SCHEDULED_EVENT_OVERRIDE
DROP TABLE NC_TASK_HISTORY_DETAIL
DROP TABLE NC_TASK_HISTORY_SUB_INDEX
DROP TABLE NC_TASK_PROPERTY
DROP TABLE NC_TASK_QUEUE
DROP TABLE NC_TSE_STATE_MAP
DROP TABLE NC_TASK_ANCESTOR_STOREIDS
DROP TABLE R_MESSAGESTRUCT_TASK
DROP TABLE R_MSGSTRUCT_RECIPIENT_DELIVINF
DROP TABLE R_NEWSITEMS_NCOBJECTS
DROP TABLE R_TASKSCHEDULE_SCHEDULE
DROP TABLE NC_RESOURCE_LOCK
——————————————————————————-
— END NC_DROP_MS.sql * DO NOT EDIT *
——————————————————————————-
Go to the SQL server and login to Microsoft SQL Server Management Studio.
Paste above script in the Query window.
Execute it on the Content Store database.
This will erase the NC tables and any data therein.
Start the Cognos BI service from Cognos Configuration to recreate the tables.
Test to surf to Cognos Connection.
If this does not help, then create a empty database and setup Cognos BI against that empty content store. Then after you have to export a deployment of all content from Old Cognos BI and import it into the new Cognos BI environment. But you will not get the “my folders” content with you in this deployment case. Then you have to use other methods to move the content.
More information:
http://www-01.ibm.com/support/docview.wss?uid=swg21339406