Handler trace back: Exception trace back: Successfully registered the dispatcher in Content Manager. Successfully unregistered the dispatcher from Content Manager. Expecting a BI Bus XML response but got: \n\n SOAP Header element not found in the SOAP response: SOAP fault found. Invalid XPath expression: A configurable object must return a valid subject (extra path information). The handler did not request any properties to be retrieved. "pogo.xml" configuration error. Unable to correctly parse "". Ensure that the file is well formed. Unable to parse SOAP envelope. It does not contain a valid XML document. Unable to open the file . The file contains the following error: . An error occurred while resolving handlers in the service : . The handler requires a name attribute. The handler requires a classname attribute. Unable to instantiate the handler class for the handler . An instance of NoopHandler was created instead. An incorrect handler class named was instantiated for the handler . An instance of NoopHandler was created instead. The dispatcher encountered an error while initializing the log service. The service requires a name attribute. The service requires a class attribute. In the service , unable to instantiate the service class . This service was ignored. In the service , the classname does not implement com.cognos.pogo.pdk.Service. This service was ignored. Unable to register the dispatcher in Content Manager. at this time. Will retry periodically. is not responding. Terminated due to inactivity. Started . Unable to start . Unable to find the following dispatcherStateHandler: . Unable to complete the request. The user does not have the 'canUseServerAdministrationTool' capability. Unable to complete the stop request. The user does not have write capability on this object. Unable to complete the start request. The user does not have write capability on this object. Unable to complete the request. The query to retrieve the 'canUseServerAdministrationTool' capability failed. Dispatcher detected an error. Unable to complete the request. The user does not have the 'canUseSDK' capability.

Start the with pid . Start a because the start count is larger than 0. Start a because the active process count is less than the limit . Shutdown the with pid . Send a stop request to the with pid . Shutdown the with pid because it didn't exit within time limit . Shutdown the with pid due to exceptions from gettting connections Shutdown the with pid due to clean up idle processes or the dispatcher receives a shutdown request. Remove idle processes. The external process with PID failed to register with the System Management Facility for usage tracking. More information and detailed descriptions of the z/OS error codes can be found on the IBM Cognos Support Portal page at http://publib.boulder.ibm.com/infocenter/zos/v1r9/index.jsp?topic=/com.ibm.zos.r9.ieag200/iea2g280108.htm.

The dispatcher port must be a number between 1 and 65536. Dispatcher host not found: Refresh request is missing the select attribute. Failed to retrieve object: Configuration version is out-of-sync: Expecting version: , retrieved version: The dispatcher referred to in the refresh message does not follow the naming convention or the dispatcher does not exist. Please verify your refresh request. Refresh request is missing the version number. The handler responsible for the refresh request not found. The version must be a number.

The object delete count did not return a number. The object update count did not return a number. The object from is of type . Expecting type: The requested object does not exist: . Unable to update Report Server performance data: successful updated Report Server performance data. Unable to determine the active Content Manager. Will retry periodically. Unable to perform an active Content Manager election on the local IP node. For more information, see the dispatcher and Content Manager detailed logs. Ensure that the local Content Manager service is started.

Handling request for URI: Finished handling request for URI: The dispatcher is ready to process requests.

The dispatcher did not initialize. Unable to execute request because the dispatcher or provider has been stopped. Unable to execute the request because there were no connections to the process available within the configured time limit. Unable to write a request. Unable to read a response. Unable to write a response to the client. The dispatcher received an invalid refresh request. The request did not contain a required element or attribute named . The dispatcher is unable to process a refresh message. The dispatcher is unable to process the request. The request is directed to an unknown service name: . The request action "" is unknown. Unable to load balance the request because no nodes in the cluster are available, or no nodes are configured for the service: . The SOAP request is malformed. Unable to logout. Unable to retrieve the data requested from Content Manager. The object "" can not be found in Content Manager or the data property is empty. There is no cluster named configured. The dispatcher may not have finished initialization. There are no nodes configured or available to process requests for the provider named . There is no mapping to a provider for requests aimed at . Unable to load the IBM Cognos WSDL. Please check your configuration. Parameter 'path' is missing in configuration file of the temporary file cleanup service. Cleanup path does not exist. Bad regular expression for file names: Execute failed, program name: Bad response code from child process: Unable to start or connect to child process. Unable to send stop request to child process. Jaxen/XPath problem. Bad TCP buffer size parameter. Both chunked encoding and content-length were specified. HTTP header was longer than internal buffer size. Chunk size expected but not found. Chunk size too big. HTTP line was longer than internal buffer size. Incorrect content-length header syntax. Unbalanced Mulitpart boundaries. Malformed Multipart message. Incorrect response line. A proper HTTP response was not received. Unable to read from the HTTP connection. Unexpected end of input stream. A dispatcher handler is misconfigured. Failed to initialize handler, need exe_name: Unable to initialize handler, need worker_request_path: Unable to initialize handler: Unable to initialize the Cognos IPF. Unable to load Properties file p2pd_deploy_defaults. IO error occurred while updating configuration. The IBM Cognos cookie is corrupt. The pogo handler configuration is incorrect. The connection pool has been shutdown. The report server handler configuration cannot be parsed. Please check "pogo.xml". The Report Server is not responding. Failed to receive a timely response from an external process with a PID . Ensure that the process with a process ID is started. If the cause of problem cannot be determined, increase the logging level for the target service in the IBM Cognos Administration tool and reproduce the conditions that caused the error. If the problem persists, see the problem determination information on the IBM Cognos Support Portal page at http://www-947.ibm.com/support/entry/portal/Overview/Software/Information_Management/Cognos The asynchronous request is stale. The request cannot be processed. The requested service has been stopped. The request cannot be completed. No response generated. This may be due to an incorrect configuration, a damaged installation, or because the dispatcher did not finish initializing. This servlet can not be accessed directly. The dispatcher encountered an error while servicing a request: . The request is invalid. No SOAPAction or "b_action" parameter is found in the request. A request to authenticate the user in Content Manager failed. An authentication request to Content Manager produced an error. The logon page will appear. The SOAP request is invalid. No operation was found in the SOAP body or the operation name is incorrect. The request failed. Please verify the input parameters and try again. The administration request failed. Please verify the input parameters and try again. The dispatcher cannot service the request at this time. The dispatcher is still initializing. Contact your administrator if this problem persists. The response from Report Server is not well formed. No response envelope is received. The handler threw an exception during services initialization. Unable to process the request because the MetadataService is not installed. Unable to load balance an administration command, most likely due to a failure to connect to the remote dispatcher. See the remote dispatcher detailed logs for more information. Check the health status of the installed system by using the dispatcher diagnostics URIs. There are no report output versions available for this report. The service did not stop within a reasonable amount of time. Unable to retrieve the requested format sample. No locale information was found in the user preferences Unable to load balance a request with absolute affinity, most likely due to a failure to connect to the remote dispatcher. See the remote dispatcher detailed logs for more information. Check the health status of the installed system by using the dispatcher diagnostics URIs. Unable to retrieve all startup configuration parameters. Error propagating notify command to: Failed to forward the request because the associated external process with PID is unavailable, either because the process is shutting down, or this was an absolute affinity request and the requested process does not exist anymore. For more information, enable the dispatcher and the external process detailed logs, and reproduce the conditions that caused the error. Unable to proceed with the request. The mandatory header "conversationContext" is missing from the request. Firewall Security Rejection. Your request was rejected by the security firewall. Firewall Security Error. A security firewall error occurred. Error status: Firewall Security Configuration Error. A security firewall configuration error occurred. Error status: An error has occurred. Please contact your administrator. The complete error has been logged by CAF with SecureErrorID: The current dispatcher received a ping request from another dispatcher that recognizes the current one by a different GUID. This likely means the current dispatcher is registered in more than one content store. The current dispatcher will reply with a fault. The current dispatcher received a request from another dispatcher with GUID=, 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 timed out. Unable to find active CM. Unable to process the request because the encoding '' is not supported. The request has exceeded the execution time limit. It will be cancelled. The requested Server Group '' does not exist. The request cannot be processed because it is malformed. It is missing the element "conversationContext/id" that is mandatory in affine requests. The request cannot be processed because it is malformed. It is missing the element "conversationContext/nodeId" that is mandatory in affine requests. The request cannot be processed because it is malformed. The element "conversationContext/processId" is missing or contains an invalid value. This element is mandatory in affine requests. The request cannot be processed because it is malformed. The element "conversationContext/affinityStrength" is missing or contains an invalid value. This element is mandatory in affine requests. The response from reportService does not contain a getMapPreviewResponse element. The response from report server contains an empty getMapPreviewResponse element. Exception occurred processing the map preview image data. Malformed map preview request. getMapPreview is missing from URL or has no value. This service cannot be stopped. A reporter instance must be associated with this handler for it to be marked as not startable. The service failed to start: . The service failed to stop: . Your request was invalid. Please contact your administrator. The cancel request succeeded. The cancel request failed. The report was not found. The dispatcher was unable to communicate with the Report Server with pid . Diagnostic files may have been generated, please check the "bin" directory. URL SOAP Encoding is not valid. The User Capabilities Cache cookie cannot be decoded. The User Capabilities Cache cookie cannot be encoded. The request has been cancelled. The request cannot be processed because it refers to non-existent conversation. The request cannot be processed because it is an absolute affinity request but does not specify a conversation. The contentManagerCacheService is disabled. The report has exceeded the size limit. Please contact your administrator to increase the limit. Maximum hop count exceeded. Please contact your administrator. Hop count maximum limit is

en/ Error - IBM Cognos IBM Cognos An error has occurred. Help Please try again or contact your administrator. OK CAF rejection details are available in the log. Please contact your administrator.

Communication failed while attempting to forward the request to the dispatcher. Ensure that IBM Cognos is running. Cannot forward the request to dispatcher even after retrying. Cannot resend request because the request was not saved. The request cannot be forwarded. No configured dispatchers are currently running. Communication failed while attempting to forward the request to the dispatcher. This may be due to dispatcher failover: Please try again.

The product is ready to use. The product is shutting down.

Hello World!