14:49:32, ' Logservice ', ' startservice ', ' Success '.
14:49:40, ' Contentmanager ', ' Getactivecontentmanager ', ' Failure '.
DPR-CMI-4006 cannot determine the active Content Manager. Please retry periodically.
14:49:40, ' Com.cognos.pogo.contentmanager.coordinator.ActiveCMControl ', ' pogo ', ' Failure '.
The DPR-DPR-1035 Scheduler detected an error.
14:49:40, a content Manager configuration error was detected when cm-cfg-5063 was connected to the contents repository. cm-cfg-5063 A Content Manager configuration error is detected while connecting to the content store. cause:cm-cfg-5137 content Manager is unable to complete the initialization of the content store. For more information, review the log file. Before you restart content Manager, your may need to recreate the content store database or clean it using Dbclean_*.sql. runtime Exception stack trace: cm-cfg-5137 Content Manager was unable to complete the initialization of The content store. For more information, review the log file. Before you restart content Manager, your may need to recreate the content store database or clean it using Dbclean_*.sql. at Com.cognos.cm.dbstore.CMDbStoreFactory.initContentIndependentBeforeLock (cmdbstorefactory.java:2126) at Com.cognos.cm.dbstore.CMDbStore.initializeContentIndependentBeforeLock (cmdbstore.java:4596) at Com.cognos.cm.server.CMServlet.initializeCoNtentstorecontentindependentbeforelock (cmservlet.java:2321) at Com.cognos.cm.server.CMServlet.init ( cmservlet.java:2046) at Com.cognos.cm.server.ContentManager.start (contentmanager.java:314) at Com.cognos.cm.server.ContentManagerLifecycleHandler.start (contentmanagerlifecyclehandler.java:73) at Com.cognos.pogo.services.DefaultHandlerService.start (defaulthandlerservice.java:111) at Com.cognos.pogo.services.DispatcherServices.startInititalServices (dispatcherservices.java:426) at Com.cognos.pogo.transport.pogoservlet$pogostartup.run (pogoservlet.java:688) at Java.lang.Thread.run ( thread.java:736)
14:50:08, ' CPS Producer registration Service ', ' stopservice ', ' Success '.
14:50:08, ' CPS Producer registration Service ', ' stopservice ', ' Success '.
14:50:08, ' EventService ', ' stopservice ', ' Success '.
14:50:08, ' EventService ', ' stopservice ', ' Success '.
14:50:08, ' Systemservice ', ' stopservice ', ' Success '.
14:50:08, ' Systemservice ', ' stopservice ', ' Success '.
14:50:08, ' Agentservice ', ' stopservice ', ' Success '.
14:50:08, ' Agentservice ', ' stopservice ', ' Success '.
14:50:08, ' Monitorservice ', ' stopservice ', ' Success '.
14:50:08, ' Monitorservice ', ' stopservice ', ' Success '.
14:50:08, ' Reportdataservice ', ' stopservice ', ' Success '.
14:50:08, ' Reportdataservice ', ' stopservice ', ' Success '.
14:50:08, ' Jobservice ', ' stopservice ', ' Success '.
14:50:08, ' Jobservice ', ' stopservice ', ' Success '.
14:50:08, ' Reportservice ', ' stopservice ', ' Success '.
14:50:08, ' Reportservice ', ' stopservice ', ' Success '.
14:50:08, ' com.cognos.pogo.services.DefaultHandlerService ', ' pogo ', ' Failure '.
The DPR-DPR-1035 Scheduler detected an error.
14:50:08, ' com.cognos.pogo.services.DefaultHandlerService ', ' pogo ', ' Failure '.
The DPR-DPR-1035 Scheduler detected an error.
14:50:08, ' Deliveryservice ', ' stopservice ', ' Success '.
14:50:08, ' Deliveryservice ', ' stopservice ', ' Success '.
14:50:08, ' MetadataService ', ' stopservice ', ' Success '.
14:50:08, ' MetadataService ', ' stopservice ', ' Success '.
14:50:08, ' Batchreportservice ', ' stopservice ', ' Success '.
14:50:08, ' Batchreportservice ', ' stopservice ', ' Success '.
14:50:08, ' Contentmanagerservice ', ' stopservice ', ' Success '.
14:50:08, ' Contentmanagerservice ', ' stopservice ', ' Success '.
14:50:08, ' Logservice ', ' stopservice ', ' Success '.
14:50:08, ' Logservice ', ' stopservice ', ' Success '.
Error An error occurred in Tomcat. Please check the log file "D:/program files (x86)/cognos/c8/logs/tomcat.log".
Error CFG-ERR-0103 cannot start the IBM Cognos 8 service.
An error code that returns a value of "1" after an external process is executed.
The database has been encoded for UTF-8, and the Java_home will be set to the JDK's own to boot properly
