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

Cognos with sql2005 service not getting started

Started by jayanthhyd, 31 Jan 2011 08:32:08 AM

Previous topic - Next topic

jayanthhyd

Its very urgent tomorrow i need to execute for my client someone please help me... cognos with sql 2005 the service is not starting.. i tested content store it run successfully but while starting services at end it stopping.. the errors are:


19:40:08, 'LogService', 'StartService', 'Success'.
19:40:10, 'ContentManager', 'getActiveContentManager', 'Failure'.
DPR-CMI-4006 Unable to determine the active Content Manager. Will retry periodically.
19:40:10, 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\sqlserver\dbInitLock_mssqlserver.sql".  There is already an object named 'CMSYSPROPS' in the database. Cause: There is already an object named 'CMSYSPROPS' in the database.    Runtime Exception stack trace:  com.jnetdirect.jsql.JSQLException: There is already an object named 'CMSYSPROPS' in the database.     at com.jnetdirect.jsql.JSQLException.makeFromDatabaseError(Unknown Source)     at com.jnetdirect.jsql.IOBuffer.processPackets(Unknown Source)     at com.jnetdirect.jsql.JSQLStatement.f(Unknown Source)     at com.jnetdirect.jsql.JSQLStatement.for(Unknown Source)     at com.jnetdirect.jsql.JSQLStatement.doExecute(Unknown Source)     at com.jnetdirect.jsql.JSQLStatement.execute(Unknown Source)     at com.cognos.cm.dbstore.CMDbStoreFactory.executeScript(CMDbStoreFactory.java:496)     at com.cognos.cm.dbstore.CMDbStoreFactory.executeScript(CMDbStoreFactory.java:334)     at com.cognos.cm.dbstore.CMDbStoreFactory.initContentIndependentBeforeLock(CMDbStoreFactory.java:2135)     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:810) 
19:40:10, 'com.cognos.pogo.contentmanager.coordinator.ActiveCMControl', 'pogo', 'Failure'.
DPR-DPR-1035 Dispatcher detected an error.

19:40:40, 'EventService', 'StopService', 'Success'.
19:40:40, 'EventService', 'StopService', 'Success'.
19:40:39, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.
DPR-DPR-1035 Dispatcher detected an error.

19:40:39, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.
DPR-DPR-1035 Dispatcher detected an error.

19:40:40, 'DeliveryService', 'StopService', 'Success'.
19:40:40, 'DeliveryService', 'StopService', 'Success'.
19:40:40, 'BatchReportService', 'StopService', 'Success'.
19:40:40, 'BatchReportService', 'StopService', 'Success'.
19:40:40, 'SystemService', 'StopService', 'Success'.
19:40:40, 'SystemService', 'StopService', 'Success'.
19:40:39, 'CPS Producer Registration Service', 'StopService', 'Success'.
19:40:39, 'CPS Producer Registration Service', 'StopService', 'Success'.
19:40:40, 'MetadataService', 'StopService', 'Success'.
19:40:40, 'MetadataService', 'StopService', 'Success'.
19:40:40, 'AgentService', 'StopService', 'Success'.
19:40:40, 'AgentService', 'StopService', 'Success'.
19:40:40, 'MonitorService', 'StopService', 'Success'.
19:40:40, 'MonitorService', 'StopService', 'Success'.
19:40:40, 'JobService', 'StopService', 'Success'.
19:40:40, 'JobService', 'StopService', 'Success'.
19:40:40, 'ReportDataService', 'StopService', 'Success'.
19:40:40, 'ReportDataService', 'StopService', 'Success'.
19:40:40, 'ReportService', 'StopService', 'Success'.
19:40:40, 'ReportService', 'StopService', 'Success'.
19:40:40, 'ContentManagerService', 'StopService', 'Success'.
19:40:40, 'ContentManagerService', 'StopService', 'Success'.
19:40:40, 'LogService', 'StopService', 'Success'.
19:40:40, 'LogService', 'StopService', 'Success'.
[ ERROR ] CFG-ERR-0103 Unable to start IBM Cognos 8 service.
Execution of the external process returns an error code value of '-1'.

jayanthhyd

please help me its very urgent.... i tried both mixed authentication both tested successfully but service not starting at the end..

yepperstn

It seems as though the content store was partially initialized.  If this is a new install, I would just clean out the content store DB and let C8 reinitialize fully. 

So, if the was a NEW installation, either drop and recreate the content store DB or use the dbClean_mssqlserver.sql script located in <<install path>>\\configuration\schemas\content\sqlserver

Suraj

Is it a new install or existing Cognos installation that is not starting?
From the error in last line, "Execution of the external process returns an error code value of '-1'.", it looks like the Cognos service is disabled under services.
Go to run and type services.msc.
Check if the Cognos service is disabled. If it is, change to 'Automatic' and start the service.

jayanthhyd

i solved the problem..Steps to resolve this problem:

Steps:

1. Click Start, point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Surface Area Configuration.



2. On the SQL Server 2005 Surface Area Configuration page, click Surface Area Configuration for Services and Connections.



3. On the Surface Area Configuration for Services and Connections page, expand Database Engine, click Remote Connections, click Local and remote connections, click the appropriate protocol to enable for your environment, and then click Apply.

Note: Click OK when you receive the following message:



Changes to Connection Settings will not take effect until you restart the Database Engine service.



4. On the Surface Area Configuration for Services and Connections page, expand Database Engine, click Service, click Stop, wait until the MSSQLSERVER service stops, and then click Start to restart the MSSQLSERVER service.


Many one facing this problem i found this after long search... It will be useful for every1 who facing integration with sql server 2005..

Suraj