DPR-ERR-2058 THE DISTPACHER CANNOT SERVICE THE REQUEST AT THIS TIME.

[cognocer]

 >:(  Can somebody help through this error!!!
is frustrating...without much literacy provided by Cognos.

DPR-ERR-2058 The distpacher cannot service the request at this time. The distpacher is still initializing. contact your administrator if this problem persists.

Steps done so far:
1) I have stop the cognos 8 service
2) run the startup.bat file from c8/bin... but is taking forever to finish. 

Is this the best way to fix my error?
Does the startup file really takes that long?

Please help.

[COGNOiSe administrator]

Describe your architecture and configuration, please.

[cognocer]

We SQL server 2000 as the database content store database.

The port number selected is 1433, with database name as cm.

We have our source database seating in SQL Server, with queries for our reports in cognos being done directly to database connections in Report Net.

[COGNOiSe administrator]

Was the server ever in use? How much RAM do you have and how much RAM have you allocated to Cognos 8.

[goose]

cognocer have you resolved this issue?

[cognocer]

NOt just yet... is really giving me a hard problem installing cognos 8 in the same server where Cognos S7 was installed before

Here is the error I get

******************************
Error

[Start Service]

1. 13:03:11, 'LogService', 'StartService', 'Success'.

2. 13:03:17, CM-CFG-5063 A Content Manager configuration error was detected while connecting to the content store.



CM-CFG-5029 Content Manager is unable to determine whether the content store is initialized.



Execute.Connection is closed

3. 13:03:18, 'com.cognos.pogo.contentmanager.coordinator.ActiveCMControl', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



4. 13:03:18, 'com.cognos.pogo.contentmanager.coordinator.ActiveCMControl', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



5. 13:03:18, 'ContentManager', 'getActiveContentManager', 'Failure'.

DPR-CMI-4006 Unable to determine the active Content Manager. Will retry periodically.

6. 13:03:33, 'MonitorService', 'StopService', 'Success'.

7. 13:03:33, 'MonitorService', 'StopService', 'Success'.

8. 13:03:33, 'CPS Producer Registration Service', 'StopService', 'Success'.

9. 13:03:33, 'CPS Producer Registration Service', 'StopService', 'Success'.

10. 13:03:33, 'ContentManagerService', 'StopService', 'Success'.

11. 13:03:33, 'ContentManagerService', 'StopService', 'Success'.

12. 13:03:34, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



13. 13:03:34, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



14. 13:03:34, 'DeliveryService', 'StopService', 'Success'.

15. 13:03:34, 'DeliveryService', 'StopService', 'Success'.

16. 13:03:33, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



17. 13:03:33, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



18. 13:03:34, 'JobService', 'StopService', 'Success'.

19. 13:03:34, 'JobService', 'StopService', 'Success'.

20. 13:03:34, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



21. 13:03:34, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



22. 13:03:34, 'EventService', 'StopService', 'Success'.

23. 13:03:34, 'EventService', 'StopService', 'Success'.

24. 13:03:34, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



25. 13:03:34, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



26. 13:03:34, 'AgentService', 'StopService', 'Success'.

27. 13:03:34, 'AgentService', 'StopService', 'Success'.

28. 13:03:34, 'reportDataService', 'StopService', 'Success'.

29. 13:03:34, 'reportDataService', 'StopService', 'Success'.

30. 13:03:34, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



31. 13:03:34, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



32. 13:03:34, 'BatchReportService', 'StopService', 'Success'.

33. 13:03:34, 'BatchReportService', 'StopService', 'Success'.

34. 13:03:34, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



35. 13:03:34, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



36. 13:03:34, 'ReportService', 'StopService', 'Success'.

37. 13:03:34, 'ReportService', 'StopService', 'Success'.

38. 13:03:34, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



39. 13:03:34, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



40. 13:03:34, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



41. 13:03:34, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



42. 13:03:34, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



43. 13:03:34, 'com.cognos.pogo.services.DefaultHandlerService', 'pogo', 'Failure'.

DPR-DPR-1035 Dispatcher detected an error.



44. 13:03:34, 'LogService', 'StopService', 'Success'.

45. 13:03:34, 'LogService', 'StopService', 'Success'.

46. [ ERROR ] CFG-ERR-0103 Unable to start Cognos 8 service.

Execution of the external process returns an error code value of '-1'.

[goose]

Looks like cognos cannot to your content store database, check your settings in cognos configuration and test the content store settings via the context menu that should give a more consise error.

[kommireddy]

Check whether the collation name for cm in sql server is Latin1_General_CI_AI or not. If not delete the current content store and recreate it with correct collation name. Check for service packs too.

before opening your cognos configuration, delete csk, encryptkeypair, signkeypair folders and Caserial cogstartup.xml, coglocale.xml and cogconfig.prefs files from c8/configuration folder.

Open the cognos configuration and set the URI properties as required.

try to test the content store connection and local configuration before saving and starting the configuration.

It is recommanded to start the cognos8 through service rather than startup.bat script.

[jayanthhyd]

I too getting these errors please help me...
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. 

   AND

DPR-DPR-1035 Dispatcher detected an error.


someone please help me...

[jayanthhyd]

CFG-ERR-0103 Unable to start IBM Cognos 8 service.
Execution of the external process returns an error code value of '-1'.

I changed database of content manager to sql 2005 and i tested it run with out errors but while starting service i am getting this error..

please help me its urgent..

[jayanthhyd]

CFG-ERR-0103 Unable to start IBM Cognos 8 service.
Execution of the external process returns an error code value of '-1'.

someone please resolve this problem...

[Rutulian]

Hi Jayanthhyd,

I can explain some of what's happened so you can avoid it in future.

Your initial errors suggests that there was a Content Store already existing in the database the config was pointed at.  To figure out why the service was trying to overwrite it rather than use it, you'd need to spend some time with Support going through the history of that Content Store - unless it's something you were trying to upgrade, I'd just leave it be.

Changing to SQL 2005 has probably meant you're pointing at a new empty database, so we're most likely dealing with a new problem.

As you're not getting much in the way of errors, the first thing I'd suggest is checking that the Service Account of the Cognos 8 service is a domain account with local admin rights to the server.  This is in Control Panel->Administrative Tools->Services  If that doesn't help, check everything on the install checklist has been done http://publib.boulder.ibm.com/infocenter/c8fpm/v8r4m0/topic/com.ibm.swg.im.cognos.qrc_crn_inst.8.4.1.doc/qrc_crn_inst_id275InstallingandConfiguringIBMCognos8ReportingonOneCo.html#id275InstallingandConfiguringIBMCognos8ReportingonOneComputer

NB: Be aware that if you're using Integrated Authentication for your SQL Server, Cognos Connection will use the user you're logged on to Windows as when performing the test, but when you start the service it will run as the user set for the service.

Kind Regards,
Alexis