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

IBM Cognos Content Store Error

Started by kc9400, 27 May 2015 04:56:15 AM

Previous topic - Next topic

kc9400

Hi all,

I've got a little bit stuck.

I've installed Cognos 10.2.1 64bit on a new windows server 2008 and everything was running ok. I've used the IBM Cognos Content Store and now when I try to start cognos I'm getting an error:

10:18:05, CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store.  CM-SYS-5003 Content Manager is unable to connect to the content store. Verify that the database connection properties in the configuration tool are correct and that when you test the connection, the test is successful. Cause: Connection authentication failure occurred.  Reason: userid or password invalid.



It's a little vague because I don't know where to look as nothing has changed since it was working. I installed it on Friday came back to work on Tuesday and it wouldn't start... any suggestions as to where I can look?


Cheers.


Update:  I've noticed it is mentioning that the username/password is incorrect but I haven't changed this. If I go to services I can start the content manager manually but I still can't get Cognos to launch.
When life gives you lemons, throw them at someone.

kc9400

#1
It appears that when installing fixpack 4 it is doing something to the configuration whereby it ends up breaking the configuration.

The error when trying to start cognos after installing Fixpack 4 is:

3:54:14, CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store.  CM-SYS-5003 Content Manager is unable to connect to the content store. Verify that the database connection properties in the configuration tool are correct and that when you test the connection, the test is successful. Cause: java.net.ConnectException : Error connecting to server localhost on port 1527 with message Connection refused: connect.    Stack trace:  java.sql.SQLNonTransientConnectionException: java.net.ConnectException : Error connecting to server localhost on port 1527 with message Connection refused: connect.     at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source)     at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)     at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)     at java.sql.DriverManager.getConnection(DriverManager.java:582)     at java.sql.DriverManager.getConnection(DriverManager.java:226)     at com.cognos.cm.dbstore.CMDbStoreFactory.getJDBCConnection(CMDbStoreFactory.java:1965)     at com.cognos.cm.dbstore.CMDbStoreFactory.getInitialConnection(CMDbStoreFactory.java:1752)     at com.cognos.cm.dbstore.CMDbStoreFactory.initContentIndependentBeforeLock(CMDbStoreFactory.java:1985)     at com.cognos.cm.dbstore.CMDbStore.initializeContentIndependentBeforeLock(CMDbStore.java:4370)     at com.cognos.cm.server.CMServlet.initializeContentStoreContentIndependentBeforeLock(CMServlet.java:2122)     at com.cognos.cm.server.CMServlet.init(CMServlet.java:1881)     at com.cognos.cm.server.ContentManager.start(ContentManager.java:436)     at com.cognos.cm.server.ContentManagerLifecycleHandler.start(ContentManagerLifecycleHandler.java:65)     at com.cognos.pogo.services.DefaultHandlerService.start(DefaultHandlerService.java:88)     at com.cognos.pogo.services.DispatcherServices.startInitialService(DispatcherServices.java:418)     at com.cognos.pogo.services.DispatcherServices.startInititalServices(DispatcherServices.java:404)     at com.cognos.pogo.transport.PogoServlet$PogoStartup.run(PogoServlet.java:803)     at com.cognos.pogo.util.threads.SafeThread.safeRun(SafeThread.java:70)     at com.cognos.pogo.util.threads.SafeThread.run(SafeThread.java:61)  Caused by: org.apache.derby.client.am.DisconnectException: java.net.ConnectException : Error connecting to server localhost on port 1527 with message Connection refused: connect.     at org.apache.derby.client.net.NetAgent.<init>(Unknown Source)     at org.apache.derby.client.net.NetConnection.newAgent_(Unknown Source)     at org.apache.derby.client.am.Connection.<init>(Unknown Source)     at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)     at org.apache.derby.client.net.NetConnection40.<init>(Unknown Source)     at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetConnection(Unknown Source)     ... 17 more  Caused by: java.net.ConnectException: Connection refused: connect     at java.net.DualStackPlainSocketImpl.connect0(Native Method)     at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:90)     at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:369)     at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:230)     at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:212)     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:191)     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:403)     at java.net.Socket.connect(Socket.java:642)     at java.net.Socket.connect(Socket.java:589)     at java.net.Socket.<init>(Socket.java:453)     at java.net.Socket.<init>(Socket.java:233)     at javax.net.DefaultSocketFactory.createSocket(SocketFactory.java:4)     at org.apache.derby.client.net.OpenSocketAction.run(Unknown Source)     at java.security.AccessController.doPrivileged(AccessController.java:330)     ... 23 more 
13:54:16, 'ContentManager', 'getActiveContentManager', 'Failure'.
DPR-CMI-4006 Unable to determine the active Content Manager. Will retry periodically.
13:54:16, 'com.cognos.pogo.contentmanager.coordinator.ActiveCMControl', 'pogo', 'Failure'.



[Start Service]
[ ERROR ] CFG-ERR-0103 Unable to start IBM Cognos service.
Execution of the external process returns an error code value of '-1'.

When life gives you lemons, throw them at someone.

kc9400

Good morning,

Well after being unable to work out exactly what was causing the issue I uninstalled Cognos and reinstalled everything again.

Everything is now up and running now without issue.
When life gives you lemons, throw them at someone.