i am getting error like below when m trying to open reporting console.
HP NNM iSPI Performance
An error has occurred.
DPR-ERR-2109 The dispatcher cannot service the request at this time. The dispatcher is still initializing. Contact your administrator if this problem persists. Please try again or contact your administrator """
It looks as though the content manager databse is not responding. The content manager is a small apache derby database not to be confused with the sybase IQ database where metrics are stored.
Have reports ever worked on this system? If so, what has changed?
If not then what is preventing content store responding? Any firewalls?
To help debugging I would first stopETL (ETL detects when BI services are not running and will attempt to restart them, this might cause some confusion so best to avoid it now)
I would then if the content store starts properly. The easiest way to do that is to start it via the BI config UI (runBIConfigUI.ovpl or BI Server - Cognos 8 -> IBM Cognos Configuration from windows start menu).
Right Click "Local Configuration" at the root of the tree on the left. Select Stop.
Then in the tree locate Environment -> HP NNM iSPI Performance content database, right click and select Start.
If it starts ok click on the close button on the dialog box.
Locate Environment -> HP NNM iSPI Performance BI Server service -> NNM iSPI Performance BIServer in tree, right click and select start. This can take some time.
If anything fails click on the "details" button snd see if you can determine more about the errors.
Also check derby.log and the cognos bootstrap logs cbs*.log (all in the logs directory)
17:22:47, CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store. CM-CFG-5036 Content Manager failed to connect to the content store. The connection string is "jdbc:derby://localhost:9301/cm". java.security.PrivilegedActionException : Error opening socket to server localhost on port 9301 with message : null Cause: java.security.PrivilegedActionException : Error opening socket to server localhost on port 9301 with message : null Runtime Exception stack trace: org.apache.derby.client.am.DisconnectException: java.security.PrivilegedActionException : Error opening socket to server localhost on port 9301 with message : null 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.jdbc.ClientDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:562) at java.sql.DriverManager.getConnection(DriverManager.java:186) at com.cognos.cm.dbstore.CMDbStoreFactory.getJDBCConnection(CMDbStoreFactory.java:2087) at com.cognos.cm.dbstore.CMDbStoreFactory.getInitialConnection(CMDbStoreFactory.java:1937) at com.cognos.cm.dbstore.CMDbStoreFactory.initContentIndependentBeforeLock(CMDbStoreFactory.java:2111) at com.cognos.cm.dbstore.CMDbStore.initializeContentIndependentBeforeLock(CMDbStore.java:4597) 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:810)
Sorry it is not clear if reporting was installed on 9.0 and also upgraded to 9.10
I guess memory issues could have contributed to the content store becoming corrupted. Have you backed up the content store since installation/upgrade?
The only things in the content store should be report and package specifications (which should not have changed) and any dynamic content you have subsequently created (like scheduled reports, query studio reports etc..) if you have no dynamic content or would be prepared to lose it then it might be worth trying to recreate the content store from scratch - I think this can be done quite simply but would want to test it to make sure that you didn't inadvertently recreate the metrics store (discarding all your metrics data) as well.
What I would definitely do now is to backup the content store if you can. Try running backup.ovpl with the -c option, if it works then the content database is at least usable, if not then error messages may help track down the issue.
In saying all that I still think you should resolve any memory problems in case they are also the root of these other issues.
Before trying my last post there is more that is required - this all works for ErsAdmin but it loses the mapping for NNMi users I'm pretty sure I can find how to add this back again but you may want to hang back until I find how (or if you know how to then you can do it)
DPR-ERR-2109 indicates that the dispatcher cannot service the request . The dispatcher is still initializing. This is caused by lack of resources on your system; did you verify the release notes to make sure that you have appropriate RAM and CPU? This is what I think is causing the DPR-ERR-2109 error.
The dispatcher is still initializing because it cannot access the content store. Accessing the content store is retried periodically so even on a system that is swapping it usually (eventually) comes up and starts to work. However, in the log files posted it shows that there is an unrecoverable error when trying to access information from the content store so the system will never come up.
I think you can actually simulate this issue by removing the contents of (but not the directory for) the content store. Remove all files/directories from contentstore/cm and the system will not try to recreate a fresh content store but obviously fails to find any contentstore tables which will cause the errors seen.
I know this has been a long thread and is a bit confused but those steps aren't exactly that I suggested, you would still need to start the BI Server for the content store to be created (if there is no content store database when BI server starts then it is automatically created at that point - starting the contentstore database just starts the database server, it doesn't create the required content. If you click on the "Details" button you should see messages relating to this)
So, have you started the BI Server? If not then do so.
If that works then you will still need to go through the steps to install the security mappings.
If it still doesn't work can you post errors/logs?
I don't have a system I can repeat this on but I'm pretty sure what I described should recreate a default empty content store. Can you try the steps again? After running stopALL look to see if there are any orphaned processes for derby or cognos. When you remove the contentstore directory make sure it gets deleted. I don't know why your system would react differently.