Welcome to the new CogKnowHow.com!


If you have trouble logging in, reset your password via the login window
by clicking the 'Forgot Password' link.

DPR-CMI-4006 Unable to determine the active Content Manager


#1

Symptom
CM-SYS-5007 Content Manager build 2.0.1300.0 failed to start! Review the Content Manager log files and then contact your system administrator or customer support.
CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store.
MSG_NOT_FOUND=cmCannotUpgradeInStandByMode
DPR-CMI-4006 Unable to determine the active Content Manager. Will retry periodically.

Problem
Configuration saves successfully but unable to start Cognos 8 service

Cause
Incorrect signon specified for the account used to connect to the content store in Cognos Configuration

Solution
Verify that the correct username and password for the database user account is specified in Cognos Configuration for the content store settings.


#2

Symptom
In Cognos Connection:
CM-SYS-5170 Content manager is unable to clean deleted referenced objects
CM-SYS-5003 Content manager is unable to access the content store. Verify your database connection parameters and then contact your database administrator.
CM-CFG-5065 A content manager configuration error was detected while attempting to execute the content initialization script
DPR-CMI-4006 Unable to determine the active Content Manager. Will retry periodically
DPR-DPR-1035 Dispatcher detected an error

Problem
Unable to start the Cognos 8 Service

Cause
SQL Server was configured to allow only 3 concurrent connections to the instance where the Cognos databases were located.

Solution
Change the setting to allow unlimited concurrent connections to the instance.
Steps:

  1. Open SQL Server Enterprise Manager
  2. Right-mouse click on the SQL Server Registration (computer name) and click on Properties.
  3. Access the Connections tab - Change the Maximum concurrent user connections to 0 for unlimited or a higher number to allow the required connections from Cognos 8.

#3

Symptom
CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store.
CM-CFG-5023 Content Manager is unable to initialize the content store by using the initialization file “C:\Program Files\cognos\c8\configuration\schemas\content\oracle\dbUpgrade4_0111-to-4_0112_oracle.sql”.
ORA-01658: unable to create INITIAL extent for segment in tablespace COGNOS_REPOS
Cause: ORA-01658: unable to create INITIAL extent for segment in tablespace COGNOS_REPOS Runtime Exception stack trace: java.sql.SQLException:
ORA-01658: unable to create INITIAL extent for segment in tablespace COGNOS_REPOS at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134) at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289) at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:582)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1981) at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:1141) at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2149) at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:2032) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2894)
at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:942) at com.cognos.cm.dbstore.CMDbStoreFactory.executeScript(CMDbStoreFactory.java:483) at com.cognos.cm.dbstore.CMDbStoreFactory.executeScript(CMDbStoreFactory.java:321)
at com.cognos.cm.dbstore.CMDbStoreFactory.upgradeDatabase(CMDbStoreFactory.java:849) at com.cognos.cm.dbstore.CMDbStoreFactory.initContentDependent(CMDbStoreFactory.java:2240) at com.cognos.cm.dbstore.CMDbStore.initializeContentDependent(CMDbStore.java:4640)
at com.cognos.cm.server.CMServlet.initializeContentStoreForActive(CMServlet.java:2482) at com.cognos.cm.server.CMServlet.init(CMServlet.java:2140)
at com.cognos.cm.server.ContentManager.start(ContentManager.java:301) at com.cognos.cm.server.ContentManagerLifecycleHandler.start(ContentManagerLifecycleHandler.java:63) at com.cognos.pogo.services.DefaultHandlerService.start(DefaultHandlerService.java:101)
at com.cognos.pogo.services.DispatcherServices.startInititalServices(DispatcherServices.java:416) at com.cognos.pogo.transport.PogoServlet$PogoStartup.run(PogoServlet.java:681) at java.lang.Thread.run(Thread.java:810)
‘ContentManager’, ‘getActiveContentManager’, ‘Failure’.
DPR-CMI-4006 Unable to determine the active Content Manager. Will retry periodically.
‘com.cognos.pogo.contentmanager.coordinator.ActiveCMControl’, ‘pogo’, ‘Failure’.
DPR-DPR-1035 Dispatcher detected an error.

Problem
During upgrade of the contentstore this error appears in the Cognos Configuration Manager

Cause
The Oracle tablespace is full.

Solution
Let the Oracle DBA assign more diskspace to the COGNOS_REPOS tablespace and start Cognos again with the Cognos Configuration Manager