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

Upgrade 8.3 to 8.4 Content Store error

Started by Cogrob, 09 Nov 2010 10:24:18 AM

Previous topic - Next topic

Cogrob

Hi

I am trying to upgrade a Windows server from Cognos 8.3 to 8.4. 

I am using Oracle 10g as the content store and have tried to upgrade the existing content store and create a new content store from scratch.

All required privileges are granted all possible tests have been applied in Cognos Configuration

I have tried in vain for some time now to resolve this problem without success, has anyone any suggestions?

error from Cognos Configuration:
16:08:51, 'LogService', 'StartService', 'Success'.
16:09:54, 'ContentManagerService', 'StartService', 'Failure'.
16:09:54, CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store.  CM-CFG-5015 Content Manager cannot access the configuration file "{File}".; Resource=/WEB-INF/cm/cmMetadata.xml
16:09:56, 'ContentManager', 'getActiveContentManager', 'Failure'.
DPR-CMI-4006 Unable to determine the active Content Manager. Will retry periodically.
16:09:57, 'com.cognos.pogo.contentmanager.coordinator.ActiveCMControl', 'pogo', 'Failure'.
DPR-DPR-1035 Dispatcher detected an error.
Failed to send HTTP request or read HTTP response


error from cogserver.log
172.25.6.106:9305   38160   2010-11-09 16:08:51.365   +0               main   LOGSV   6003   1   server.Audit.IPF   StartService   LogService      Success      <parameters><item name="Port"><![CDATA[9397]]></item><item name="Mode"><![CDATA[UDP]]></item><item name="Secure"><![CDATA[FALSE]]></item></parameters>
172.25.6.106:9305   38160   2010-11-09 16:09:54.928   +0   Initialization_SESS   Initialization_REQ         Thread-17   CM   6013   1   Audit.cms.CM   StartService   ContentManagerService      Failure      CM-SYS-5007 Content Manager build 8.4.6013.0 failed to start! Review the Content Manager log files and then contact your system administrator or customer support.
172.25.6.106:9305   38160   2010-11-09 16:09:54.850   +0   Initialization_SESS   Initialization_REQ         Thread-17   CM   6013   1   Audit.cms.CM   UpgradeDetails   ContentManagerService      Info      CM-UPG-2012 The Content Manager database schema upgrade started.
172.25.6.106:9305   38160   2010-11-09 16:09:54.928   +0   Initialization_SESS   Initialization_REQ         Thread-17   CM   6013   1   Audit.cms.CM   StartService         Warning      CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store.  CM-CFG-5015 Content Manager cannot access the configuration file "{File}".; Resource=/WEB-INF/cm/cmMetadata.xml
172.25.6.106:9305   38160   2010-11-09 16:09:56.147   +0   pogoStartup   na   na   0   Thread-17   DISP   6009   1   Audit.Other.dispatcher.DISP.com.cognos.pogo.contentmanager.coordinator.CMBootstrap   getActiveContentManager   ContentManager      Failure   <messages><message><messageString>DPR-CMI-4006 Unable to determine the active Content Manager. Will retry periodically.</messageString></message></messages>   
172.25.6.106:9305   38160   2010-11-09 16:09:57.115   +0   pogoStartup   na   na   0   Thread-17   DISP   6009   1   Audit.Other.dispatcher.DISP.pogo   pogo   com.cognos.pogo.contentmanager.coordinator.ActiveCMControl      Failure   <messages><message><messageString>DPR-DPR-1035 Dispatcher detected an error.</messageString></message><message><messageString>Failed to send HTTP request or read HTTP response</messageString></message></messages>   DPR-CMI-4007 A request to perform an active content manager election failed.Failed to send HTTP request or read HTTP response com.cognos.pogo.bibus.CommandExecutionException: Failed to send HTTP request or read HTTP response    at com.cognos.pogo.bibus.BIBusCommand.execute(BIBusCommand.java:307)    at com.cognos.pogo.contentmanager.StandbyContentManagerElectionCommand.executeIfLocal(StandbyContentManagerElectionCommand.java:67)    at com.cognos.pogo.contentmanager.coordinator.ActiveCMControl.sendElectCommand(ActiveCMControl.java:246)    at com.cognos.pogo.contentmanager.coordinator.ActiveCMControl.startTimer(ActiveCMControl.java:193)    at com.cognos.pogo.contentmanager.coordinator.ActiveCMControl.startupFindCM(ActiveCMControl.java:156)    at com.cognos.pogo.contentmanager.coordinator.RuntimeInfoPublishHandler.start(RuntimeInfoPublishHandler.java:135)    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:810) Caused by: java.io.IOException: Failed to send HTTP request or read HTTP response    at com.cognos.pogo.http.ServerConnection.executeMethod(ServerConnection.java:782)    at com.cognos.pogo.http.ServerConnection.sendRequest(ServerConnection.java:224)    at com.cognos.pogo.bibus.BIBusCommand.execute(BIBusCommand.java:245)    ... 9 more

Cogrob

I should add that the OS is windows 2003 and that I stopped the 8.3 services before trying to start the 8.4 services

Robert

cognostechie

Quote from: Cogrob on 09 Nov 2010 10:24:18 AM
CM-UPG-2012 The Content Manager database schema upgrade started.

Why does it say that? You said you created a new schema for 8.4 Content Store, correct ?
Did you create a brand new schema and test the connection  for Content Store ot using the 8.3 Content Store in 8.4 ?

By the way, you only need to shut down the service for 8.3 if you have not changed the port nos for 8.4.


Cogrob

I tried using the 8.3 schema and also tried a new schema, both gave similar problems.

I have uninstalled all 8.3 cognos and 8.4 on the server and reinstalled 8.4.

I created the 8.4 schema from scratch and it now works, I'm currently importing a .zip of the 8.3 content store exported from the 8.3 service.

I'm convinced the 8.4 was corrupt some how, (a recently departed colleague installed it some time ago), possibly uninstalling 8.3 was an overkill but it is still installed on another server if I need it.

Robert