Cognos Service Request Error
Contents |
Problem(Abstract) When starting the Cognos service within cognos impromptu error Cognos Configuration a DPR-DPR-1035 error will be shown in
Cognos Error Traceback
the Cognos Configuration details section. The error is also logged within the cogserver.log and
Cognos Error Qe-def-0260
the pogo
Cognos Error 'sqlopenresult' Status='-28'
Symptom In Cognos Configuration while starting the Cognos environment: DPR-DPR-1035 Der Dispatcher hat einen Fehler gefunden (German) Cause The Cognos services are misconfigured. There are two Report Service XML files within the services folder:
not receive a response... Technote (troubleshooting) Problem(Abstract) Unable to successfully start a new installation of Cognos 8 when ReportNet 1.1 is running on the same machine. Service appears as started in Control http://www.ibm.com/support/docview.wss?uid=swg21341600 Panel. Symptom Error starting Cognos 8 from Cognos Configuration: [Starting Service] An error occurred within Tomcat. Please check the log file tomcat.log CFG-ERR-0106 Cognos Configuration did not receive a response from the Cognos 8 service in http://www.ibm.com/support/docview.wss?uid=swg21339016 the time allotted. Error attempting to log into the Cognos Connection: DPR-ERR-2008 The dispatcher is unable to process the request. The request is directed to an unknown service name: ext. Cause Both ReportNet 1.1 and cognos error Cognos 8 install by default to use dispatcher Port 9300, Logging port 9362 and Shutdown Port 9399. The default service name will be Cognos Report Net or Cognos 8. If another version of ReportNet or Cognos 8 is running on the same server, and there is an attempt to start another installation with the same values, it will fail because the value(s) is/are already in use. Resolving the problem Ensure cognos service request that the configuration information for the two services contains unique port numbers and service names. By default, the service name will automatically change to reflect the Dispatcher port number if it has been changed from 9300. However, it is useful to gave each installation a meaningful service name, like "ReportNet Content Manager" or "Cognos 8 Application" Steps: Start Cognos Configuration for either installation of Cognos 8 or ReportNet, Stop the service (if running) Go to Environment, and change the port number in the various Dispatcher URI Settings Go to Environment->Cognos 8 Service (or IBM Cognos ReportNet Service) Right-click on the service (Cognos 8 or Cognos ReportNet), and click "Rename". Change the name to something unique. Go to the renamed service, and change the Shutdown Port Number setting. Go to Environment->Logging, and change the Local log server port number setting. Save the changes and restart the service. Related information Cross Reference information Segment Product Component Platform Version Edition Business Analytics Cognos 8 Business Intelligence Install and Config Business Analytics Cognos 8 Business Intelligence Metrics Studio Business Analytics Cognos 8 Business Intelligence Report Studio Business Analytics Cognos ReportNet ReportNet Business Analytics Cognos Series 7 PowerPlay Enterprise Server Historical Number 1029991 Document information More support for: Cognos 8 Business Intelligence Cognos Connection Sof
name: local.xts.run' error message when trying to launch Cognos Reports upgraderep; upgradeinscfg; upadset Technote (troubleshooting) Problem(Abstract) User tries to access Cognos BI (or ReportNet) inside a web browser. User receives an error. Symptom DPR-ERR-2008 The dispatcher is unable to process the request. The request is directed to an unknown service name: local.xts.run. Cause There are several potential causes for this error message: Scenario #1 - The relevant 'Dispatcher' is not active Scenario #2 - The report needs to be upgraded, and the relevant 'Presentation Service' is not active For more details, see separate IBM Technote #1516137 Scenario #3 - Invalid settings inside the content store after a service pack upgrade For more details, see separate IBM Technote #1343009 Scenario #4 - Cognos server was installed using a Windows user account that was not a Windows administrator on the server. For more details, see separate IBM Technote #1344321 Environment Scenario #1: By default, the 'Dispatcher ' service is disabled on a computer where 'Content Manager' is the only component that is installed. This may explain why the dispatcher is disabled, since the person installing the system may have installed the 'Content Manager' component only first, and then (afterwards) installed the other components. Resolving the problem Scenario #1 Launch Cognos Configuration (on the relevant report server), and enable the Dispatcher service. Steps: Launch Cognos Configuration from the start menu Expand 'Local Configuration' - 'Environment' Select 'IBM Cognos Service' On the right hand side, select 'Dispatcher service enabled?' Modify the setting from 'False' to 'True' Click the 'save' icon at the top-left corner Click the 'restart service' icon After the Cognos service has restarted, test. Scenario #2 Either (1) Create a new Report Upgrade task from IBM Cognos Administr