Can anyone please rectify this issue?
I am getting error, When I restart the service
[Launching a JVM using 'Maximum memory in MB']
Successfully launched a test JVM with the memory setting of '768'. Note that this does not guarantee that the IBM Cognos service will start and run successfully.
To see which JVM options are based on this setting, view ibmcognos_location/bin/bootstrap_<OS>.xml and see your JVM documentation for an explanation of those options.
[Archive Local File System Root]
Since the value is empty, the feature is disabled. There is nothing to test.
[Validate mail server properties.]
[ ERROR ] The mail server cannot be reached.
[Archive Local File System Root]
Since the value is empty, the feature is disabled. There is nothing to test.
[Stop Service]
10:29:11, 'ContentManagerService', 'StopService', 'Success'.
10:29:11, 'IndexSearchService', 'StopService', 'Success'.
10:29:11, 'MetadataService', 'StopService', 'Success'.
10:29:11, 'HumanTaskService', 'StopService', 'Success'.
10:29:11, 'AnnotationService', 'StopService', 'Success'.
10:29:11, 'JobService', 'StopService', 'Success'.
10:29:11, 'Dispatcher', 'Stop', 'Success'.
10:29:11, 'CPS Producer Registration Service', 'StopService', 'Success'.
10:29:11, 'DeliveryService', 'StopService', 'Success'.
10:29:11, 'DimensionManagementService', 'StopService', 'Success'.
10:29:11, 'IndexUpdateService', 'StopService', 'Success'.
10:29:11, 'MonitorService', 'StopService', 'Success'.
10:29:11, 'IndexDataService', 'StopService', 'Success'.
10:29:11, 'AgentService', 'StopService', 'Success'.
10:29:13, 'ReportService', 'StopService', 'Success'.
10:29:13, 'EventService', 'StopService', 'Success'.
10:29:13, 'QLSImportService', 'StopService', 'Success'.
10:29:13, 'QLSService', 'StopService', 'Success'.
10:29:13,
10:29:13, 'SMDService', 'StopService', 'Success'.
10:29:13, 'idVizService', 'StopService', 'Success'.
10:29:13, 'Fragment Server Service', 'StopService', 'Success'.
10:29:13, 'SystemService', 'StopService', 'Success'.
10:29:13, 'idVizServer', 'StopService', 'Success'.
10:29:13, 'QLSBIService', 'StopService', 'Success'.
10:29:13, 'BUX Service', 'StopService', 'Success'.
10:29:13, 'camAsyncAA', 'StopService', 'Success'.
10:29:13, 'GraphicsService', 'StopService', 'Success'.
10:29:16, 'burstDistributionService', 'StopService', 'Success'.
10:29:16, 'QueryService', 'StopService', 'Success'.
10:29:16, 'com.cognos.pogo.reportservice.ProcessFacade', 'pogo', 'Failure'.
DPR-DPR-1035 Dispatcher detected an error.
Failed to send HTTP request or read HTTP response
10:29:16, 'BatchReportService', 'StopService', 'Success'.
10:29:16, 'ContentManagerCacheService', 'StopService', 'Success'.
10:29:16, 'visualisationGalleryService', 'StopService', 'Success'.
10:29:16, 'CacheService', 'StopService', 'Success'.
10:29:16, 'IBM Cognos Enhanced Search Service', 'StopService', 'Success'.
10:29:16, 'relationalMetadataService', 'StopService', 'Success'.
10:29:16, 'PresentationService', 'StopService', 'Success'.
10:29:16, 'RepositoryService', 'StopService', 'Success'.
10:29:16, 'ReportDataService', 'StopService', 'Success'.
10:29:16, 'PDC', 'StopService', 'Success'.
10:29:16, 'SACamSrvc', 'StopService', 'Success'.
10:29:16, 'LogService', 'StopService', 'Success'.
[Start Service]
10:30:26, 'LogService', 'StartService', 'Success'.
10:30:27, CAF-WRN-0010 CAF input validation enabled.
10:30:27, CAF-WRN-0021 CAF Third Party XSS checking disabled.
10:30:56, 'ContentManagerService', 'StartService', 'Success'.
10:30:56, CM-SYS-5160 Content Manager is running in standby mode. The active Content Manager URL is http://ComputerB:9300/p2pd/servlet.
10:30:55, CM-SYS-5242 Background task manager is not running.
10:31:02, 'com.cognos.pogo.contentmanager.coordinator.CMBootstrap', 'pogo', 'Failure'.
DPR-DPR-1035 Dispatcher detected an error.
Failed to send HTTP request or read HTTP response
10:31:02, 'http://computerB:9300/p2pd', 'registerInCM', 'Failure'.
DPR-DPR-1026 Unable to register the dispatcher in Content Manager. computerA:9300/p2pd/servlet at this time. Will retry periodically.
Failed to send HTTP request or read HTTP response
10:31:02, 'com.cognos.pogo.contentmanager.coordinator.BootstrapConfigurePublish', 'pogo', 'Failure'.
DPR-DPR-1035 Dispatcher detected an error.
Failed to send HTTP request or read HTTP response
10:31:02, 'com.cognos.pogo.contentmanager.coordinator.CMBootstrap', 'pogo', 'Failure'.
DPR-DPR-1035 Dispatcher detected an error.
10:31:11, CM-REQ-2378 A request was received to start the negotiation process to determine which Content Manager instance should become active.
10:32:03, CM-REQ-2378 A request was received to start the negotiation process to determine which Content Manager instance should become active.
10:32:54, CM-REQ-2378 A request was received to start the negotiation process to determine which Content Manager instance should become active.
10:33:46, CM-REQ-2378 A request was received to start the negotiation process to determine which Content Manager instance should become active.
10:34:37, CM-REQ-2378 A request was received to start the negotiation process to determine which Content Manager instance should become active.
10:35:29, CM-REQ-2378 A request was received to start the negotiation process to determine which Content Manager instance should become active.
10:36:20, CM-REQ-2378 A request was received to start the negotiation process to determine which Content Manager instance should become active.
10:37:12, CM-REQ-2378 A request was received to start the negotiation process to determine which Content Manager instance should become active.
10:38:03, CM-REQ-2378 A request was received to start the negotiation process to determine which Content Manager instance should become active.
10:38:55, CM-REQ-2378 A request was received to start the negotiation process to determine which Content Manager instance should become active.
10:39:46, CM-REQ-2378 A request was received to start the negotiation process to determine which Content Manager instance should become active.
[Start Service]
[ ERROR ] CFG-ERR-0106 IBM Cognos Configuration did not receive a response from the IBM Cognos service in the time allotted.
Check that IBM Cognos service is available and properly configured.
10:40:38, CM-REQ-2378 A request was received to start the negotiation process to determine which Content Manager instance should become active.
10:41:29, CM-REQ-2378 A request was received to start the negotiation process to determine which Content Manager instance should become active.
Hi
Did you resolve the issue ? If not, from the error it seems like you have two content manager servers A and B. Aso it seems like you have installed the dispatcher component on both of them. Please correct me if i am wrong.
Stop the services on your computer B. Then first try to start the service on computer A.
Also make sure that your configuration should include the URIs of both content manager.
Quote from: sunosoft on 07 Jan 2014 06:27:05 PM
Hi
Did you resolve the issue ? If not, from the error it seems like you have two content manager servers A and B. Aso it seems like you have installed the dispatcher component on both of them. Please correct me if i am wrong.
Stop the services on your computer B. Then first try to start the service on computer A.
Also make sure that your configuration should include the URIs of both content manager.
Is it need to follow the sequence of stop and start the service on both machines cognos configuration?
Thanks,
Simi
@SunoSOft,
After your suggestion and followed your steps to start the server without any issue.
But, in the Computer B logfile, the error has like,
10.10.12.195:9300 14424 2014-01-07 17:01:45.557 -8 na na Timer-24 DISP 5000 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService AnnotationService Success
10.10.12.195:9300 14424 2014-01-07 17:01:45.540 -8 na na Timer-24 DISP 5000 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService IndexSearchService Success
10.10.12.195:9300 14424 2014-01-07 17:01:45.169 -8 Timer-24 EMS 5000 1 Audit.ems.EMS StartService EventService Success
10.10.12.195:9300 14424 2014-01-07 17:01:45.175 -8 na na Timer-24 DISP 5000 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService HumanTaskService Success
10.10.12.195:9300 14424 2014-01-07 17:01:45.178 -8 na na Timer-24 DISP 5000 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService DimensionManagementService Success
10.10.12.195:9300 14424 2014-01-07 17:01:46.768 -8 na na Timer-24 DISP 5000 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService CPS Producer Registration Service Success
10.10.12.195:9300 14424 2014-01-07 17:01:47.319 -8 na na Timer-24 DISP 5000 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.logging.SystemEventLogger Start Dispatcher Success DPR-SYS-6000 The product is ready to use.
10.10.12.195:9300 14424 2014-01-07 17:05:47.734 -8 actionQueue na na 0 Thread-22 DISP 5000 1 Audit.Other.dispatcher.DISP.pogo pogo com.cognos.p2plb.model.NodeHospital Failure <messages><message><messageString>DPR-DPR-1035 Dispatcher detected an error.</messageString></message></messages> Ping of sick dispatcher Computer A(it is a Virtual machine Server):9300/p2pd/servlet/dispatch failed. Error code = caf
Thanks,
Simi
@sunosoft,
This message is form computer A(Virtual Server) logfile,
10.10.9.186:9300 12584 2014-01-07 16:57:07.560 -8 na na Timer-24 DISP 5000 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService AnnotationService Success
10.10.9.186:9300 12584 2014-01-07 16:57:07.560 -8 Timer-24 DLS 5000 1 Audit.ds.DLS StartService DeliveryService Success
10.10.9.186:9300 12584 2014-01-07 16:57:10.168 -8 na na Timer-24 DISP 5000 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService CPS Producer Registration Service Success
10.10.9.186:9300 12584 2014-01-07 17:00:04.241 -8 na na Timer-24 DISP 5000 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.logging.SystemEventLogger Start Dispatcher Success DPR-SYS-6000 The product is ready to use.
10.10.9.186:9300 12584 2014-01-07 17:05:46.978 -8 http-9300-31 caf 2047 1 Audit.dispatcher.caf Request Failure SecureErrorId: 2014-01-07-17:05:46.962-#1 Original Error: DPR-ERR-2084 The current dispatcher received a request from another dispatcher with GUID=A3AE9FC6-48BF-41BB-8979-C381840E6EEC, but could not resolve the GUID. This likely means both dispatchers are running against different content stores and the current one is registered in both. There may be an old/incorrect registration for the current dispatcher in the other content store. Request refused, GUID of source is unknown.
10.10.9.186:9300 12584 2014-01-07 17:05:47.805 -8 http-9300-31 caf 2047 1 Audit.dispatcher.caf Request Failure SecureErrorId: 2014-01-07-17:05:47.805-#2 Original Error: DPR-ERR-2084 The current dispatcher received a request from another dispatcher with GUID=A3AE9FC6-48BF-41BB-8979-C381840E6EEC, but could not resolve the GUID. This likely means both dispatchers are running against different content stores and the current one is registered in both. There may be an old/incorrect registration for the current dispatcher in the other content store. Request refused, GUID of source is unknown.
10.10.9.186:9300 12584 2014-01-07 17:05:57.813 -8 http-9300-3 caf 2047 1 Audit.dispatcher.caf Request Failure SecureErrorId: 2014-01-07-17:05:57.813-#3 Original Error: DPR-ERR-2084 The current dispatcher received a request from another dispatcher with GUID=A3AE9FC6-48BF-41BB-8979-C381840E6EEC, but could not resolve the GUID. This likely means both dispatchers are running against different content stores and the current one is registered in both. There may be an old/incorrect registration for the current dispatcher in the other content store. Request refused, GUID of source is unknown.
10.10.9.186:9300 12584 2014-01-07 17:06:17.797 -8 http-9300-30 caf 2047 1 Audit.dispatcher.caf Request Failure SecureErrorId: 2014-01-07-17:06:17.797-#4 Original Error: DPR-ERR-2084 The current dispatcher received a request from another dispatcher with GUID=A3AE9FC6-48BF-41BB-8979-C381840E6EEC, but could not resolve the GUID. This likely means both dispatchers are running against different content stores and the current one is registered in both. There may be an old/incorrect registration for the current dispatcher in the other content store. Request refused, GUID of source is unknown.
10.10.9.186:9300 12584 2014-01-07 17:06:47.790 -8 http-9300-25 caf 2047 1 Audit.dispatcher.caf Request Failure SecureErrorId: 2014-01-07-17:06:47.790-#5 Original Error: DPR-ERR-2084 The current dispatcher received a request from another dispatcher with GUID=A3AE9FC6-48BF-41BB-8979-C381840E6EEC, but could not resolve the GUID. This likely means both dispatchers are running against different content stores and the current one is registered in both. There may be an old/incorrect registration for the current dispatcher in the other content store. Request refused, GUID of source is unknown.
10.10.9.186:9300 12584 2014-01-07 17:07:17.783 -8 http-9300-2 caf 2047 1 Audit.dispatcher.caf Request Failure SecureErrorId: 2014-01-07-17:07:17.767-#6 Original Error: DPR-ERR-2084 The current dispatcher received a request from another dispatcher with GUID=A3AE9FC6-48BF-41BB-8979-C381840E6EEC, but could not resolve the GUID. This likely means both dispatchers are running against different content stores and the current one is registered in both. There may be an old/incorrect registration for the current dispatcher in the other content store. Request refused, GUID of source is unknown.
10.10.9.186:9300 12584 2014-01-07 17:07:47.761 -8 http-9300-13 caf 2047 1 Audit.dispatcher.caf Request Failure SecureErrorId: 2014-01-07-17:07:47.761-#7 Original Error: DPR-ERR-2084 The current dispatcher received a request from another dispatcher with GUID=A3AE9FC6-48BF-41BB-8979-C381840E6EEC, but could not resolve the GUID. This likely means both dispatchers are running against different content stores and the current one is registered in both. There may be an old/incorrect registration for the current dispatcher in the other content store. Request refused, GUID of source is unknown.
10.10.9.186:9300 12584 2014-01-07 17:08:17.755 -8 http-9300-13 caf 2047 1 Audit.dispatcher.caf Request Failure SecureErrorId: 2014-01-07-17:08:17.755-#8 Original Error: DPR-ERR-2084 The current dispatcher received a request from another dispatcher with GUID=A3AE9FC6-48BF-41BB-8979-C381840E6EEC, but could not resolve the GUID. This likely means both dispatchers are running against different content stores and the current one is registered in both. There may be an old/incorrect registration for the current dispatcher in the other content store. Request refused, GUID of source is unknown.
Can you please rectify this issue.
I am trying to resolve this issue for a week.
Please anyone help me to solve this
Thanks,
Simi
see the error message itself is indicating that you are using different content stores on those machines.
Please check if you are using the same content store database on both the content manager servers.
@sunosoft,
yes, we are using same content store DB on both content manager servers.
Can you please let me know how to rectify this issue.
Thanks,
Simi
Did you check below link ?
http://www-01.ibm.com/support/docview.wss?uid=swg21397588
Seems like it will help you. Let me know how it goes.
Also have look on below link.
http://www.cognoise.com/index.php?topic=6078.0
Yes, I followed the First link.. But, still gettting same issue from Computer 1(Virtual machine server) log file
10.10.9.186:9300 17936 2014-01-08 15:43:58.486 -8 na na Timer-24 DISP 5000 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService AnnotationService Success
10.10.9.186:9300 17936 2014-01-08 15:44:12.263 -8 na na Timer-24 DISP 5000 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.logging.SystemEventLogger Start Dispatcher Success DPR-SYS-6000 The product is ready to use.
10.10.9.186:9300 17936 2014-01-08 15:48:28.737 -8 actionQueue na na 0 Thread-22 DISP 5000 1 Audit.Other.dispatcher.DISP.pogo pogo com.cognos.p2plb.model.NodeHospital Failure <messages><message><messageString>DPR-DPR-1035 Dispatcher detected an error.</messageString></message></messages> Ping of sick dispatcher computer 2:9300/p2pd/servlet/dispatch failed. Error code = Failed to send HTTP request or read HTTP response
If am I anything correctly configure on cognos configuration.
Here is the information how I did on both content manager server configuration.
In Computer 1:
On Cognos Configuration - content manager URI - http://localhost(computer1 name)/p2pd/servlet
on Data Access->content manager-> content store->MS sql server, localhost(computer 1name):1452, username and p/w, db name->CM
In Computer 2:
on cognos configuration - content manager URI - http://computer1 name/p2pd/servlet
http://localhost(computer2 name)/p2pd/servlet
on Data Access->content manager-> content store->MS sql server, computer1 name:1452, username and p/w, db name->CM
So, same content store DB on content manager servers and both machines has FM, webservers, Cognos configuration.
Can you please let me know, anything I have misconfigured.
I know, I am keep on asking same questions in this thread.
Please help me to solve this issue.
Thanks in advance,
Simi