DispatcherMessages_en.xml 30 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <!--
  3. Licensed Materials - Property of IBM
  4. IBM Cognos Products: disp
  5. (C) Copyright IBM Corp. 2005 2012
  6. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
  7. -->
  8. <stringTable xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../../win32/msgsdk/CCLMessageFile.xsd">
  9. <component name="DPR" usage="Messages generated by the Dispatcher">
  10. <section name="DPR" usage="This section is for message that are generic Dispatcher messages" type="Messages">
  11. <string id="HANDLER_TRACEBACK">Handler trace back:</string>
  12. <string id="EXCEPTION_STACKTRACE">Exception trace back:</string>
  13. <string id="REGISTRATION_SUCCESS" errorCode="1002">Successfully registered the dispatcher <param name="0"/> in Content Manager.</string>
  14. <string id="UNREGISTRATION_SUCCESS" errorCode="1003">Successfully unregistered the dispatcher <param name="0"/> from Content Manager.</string>
  15. <string id="BIBusCommand.badMIMEType" errorCode="1004">Expecting a BI Bus XML response but got: \n\n</string>
  16. <string id="BIBusCommand.missingHeader" errorCode="1005">SOAP Header element not found in the SOAP response: </string>
  17. <string id="BIBusCommand.soapFaultFound" usage="Indicate that a SOAP fault was in the BIBus response but the Command class is set to not process the error" errorCode="1006">SOAP fault found.</string>
  18. <string id="Move_d_Handler.invalidXPath" errorCode="1007">Invalid XPath expression: <param name="0"/>
  19. </string>
  20. <string id="ConfigurationController.badSubject" errorCode="1009">A configurable object must return a valid subject (extra path information).</string>
  21. <string id="ConfigurationController.badPropertiesRequest" errorCode="1010">The handler did not request any properties to be retrieved.</string>
  22. <string id="Dom4JConfigurator.badConfiguration" errorCode="1011">"pogo.xml" configuration error.</string>
  23. <string id="XMLConfigurator.parseError" errorCode="1012">Unable to correctly parse "<param name="0"/>". Ensure that the file is well formed.</string>
  24. <string id="SOAPEnvelope.badEnvelope" errorCode="1013">Unable to parse SOAP envelope. It does not contain a valid XML document.</string>
  25. <string id="XMLConfigurator.fileNotFound" errorCode="1014">Unable to open the file <param name="0"/>.</string>
  26. <string id="XMLConfigurator.fileError" errorCode="1015">The file <param name="0"/> contains the following error: <param name="1"/>.
  27. </string>
  28. <string id="HandlerReadingService.contextualize" errorCode="1016">An error occurred while resolving handlers in the service <param name="0"/>: <param name="1"/>.
  29. </string>
  30. <string id="HandlerFactory.noName" errorCode="1017">The handler requires a name attribute.</string>
  31. <string id="HandlerFactory.noClass" errorCode="1018">The handler <param name="0"/> requires a classname attribute.</string>
  32. <string id="HandlerFactory.cantInstantiate" errorCode="1019">Unable to instantiate the handler class <param name="1"/> for the handler <param name="0"/>. An instance of NoopHandler was created instead.</string>
  33. <string id="HandlerFactory.notHandler" errorCode="1020">An incorrect handler class named <param name="0"/> was instantiated for the handler <param name="1"/>. An instance of NoopHandler was created instead.</string>
  34. <string id="ConfigStoreServlet.logServiceStart" errorCode="1021">The dispatcher encountered an error while initializing the log service.</string>
  35. <string id="ServiceFactory.noName" errorCode="1022">The service requires a name attribute.</string>
  36. <string id="ServiceFactory.noClass" errorCode="1023">The service <param name="0"/> requires a class attribute.</string>
  37. <string id="ServiceFactory.cantInstantiate" errorCode="1024">In the service <param name="0"/>, unable to instantiate the service class <param name="1"/>. This service was ignored.</string>
  38. <string id="ServiceFactory.notService" errorCode="1025">In the service <param name="0"/>, the classname <param name="1"/> does not implement com.cognos.pogo.pdk.Service. This service was ignored.</string>
  39. <string id="REGISTRATION_FAILURE" type="String" errorCode="1026">Unable to register the dispatcher in Content Manager. <param name="0" type="string"/> at this time. Will retry periodically.</string>
  40. <string id="ProcessManager.notResponding" type="String" errorCode="1027"><param name="0"/> is not responding.</string>
  41. <string id="ProcessManager.inactive" errorCode="1028">Terminated <param name="0"/> due to inactivity.</string>
  42. <string id="ProcessManager.started" errorCode="1029">Started <param name="0"/>.</string>
  43. <string id="ProcessManager.notStarted" errorCode="1037">Unable to start <param name="0"/>.</string>
  44. <string id="dispatcherStateHandlerNotFound" errorCode="1030">Unable to find the following dispatcherStateHandler: <param name="0"/>.</string>
  45. <string id="CapabilitiesCheckHandler.requestNotAllowed" errorCode="1031">Unable to complete the request. The user does not have the 'canUseServerAdministrationTool' capability.</string>
  46. <string id="stopService.requestNotAllowed" errorCode="1032">Unable to complete the stop request. The user does not have write capability on this object.</string>
  47. <string id="startService.requestNotAllowed" errorCode="1033">Unable to complete the start request. The user does not have write capability on this object.</string>
  48. <string id="CapabilitiesCheckHandler.queryFailed" errorCode="1034">Unable to complete the request. The query to retrieve the 'canUseServerAdministrationTool' capability failed.</string>
  49. <string id="Dispatcher.detectedError" errorCode="1035">Dispatcher detected an error.</string>
  50. <string id="CanUseSDKCheckHandler.requestNotAllowed" errorCode="1036">Unable to complete the request. The user does not have the 'canUseSDK' capability.</string>
  51. </section>
  52. <section name="BUS" usage="This section is for logging the start/stop status of Report Server processes" type="Messages">
  53. <string id="BIBus.started">Start the <param name="0"/> with pid <param name="1"/>.</string>
  54. <string id="BIBus.startedDueToStartCount">Start a <param name="0"/> because the start count <param name="1"/> is larger than 0.</string>
  55. <string id="BIBus.startedDueToProcessCount">Start a <param name="0"/> because the active process count <param name="1"/> is less than the limit <param name="2"/>.</string>
  56. <string id="BIBus.stopped">Shutdown the <param name="0"/> with pid <param name="1"/>.</string>
  57. <string id="BIBus.sendStopRequst">Send a stop request to the <param name="0"/> with pid <param name="1"/>.</string>
  58. <string id="BIBus.stoppedDueToTimeLimit">Shutdown the <param name="0"/> with pid <param name="1"/> because it didn't exit within time limit <param name="2"/>.</string>
  59. <string id="BIBus.stopDueToException">Shutdown the <param name="0"/> with pid <param name="1"/> due to exceptions from gettting connections</string>
  60. <string id="BIBus.stopDueToCleanup">Shutdown the <param name="0"/> with pid <param name="1"/> due to clean up idle processes or the dispatcher receives a shutdown request.</string>
  61. <string id="BIBus.removeIdleProcess">Remove <param name="0"/> idle processes.</string>
  62. <string id="BIBus.startedWithstderr" errorCode="1500">The external process <param name="0"/> with PID <param name="1"/> 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.</string>
  63. </section>
  64. <section name="CFG" usage="This section is for messages generate while processing console refresh requests" type="Messages">
  65. <string id="refresh.badPort" errorCode="3000">The dispatcher port must be a number between 1 and 65536.</string>
  66. <string id="refresh.badHost" errorCode="3001">Dispatcher host not found: </string>
  67. <string id="refresh.missingSelectAttribute" errorCode="3004">Refresh request is missing the select attribute.</string>
  68. <string id="refresh.noObject" errorCode="3006">Failed to retrieve object: <param name="0"/>
  69. </string>
  70. <string id="refresh.versionMismatch" errorCode="3008">Configuration version is out-of-sync: Expecting version: <param name="0"/>, retrieved version: <param name="1"/>
  71. </string>
  72. <string id="refresh.badObject" errorCode="3002">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.</string>
  73. <string id="refresh.missingVersion" errorCode="3003">Refresh request is missing the version number.</string>
  74. <string id="refresh.noMatchingHandler" errorCode="3005">The handler responsible for the refresh request not found.</string>
  75. <string id="refresh.versionNaN" errorCode="3007">The version must be a number.</string>
  76. </section>
  77. <section name="CMI" usage="This section is for messages generated while interfacing with Content Manager" type="Messages">
  78. <string id="deleteCommand.NAN" usage="A CM delete request returns a number of objects affected" errorCode="4000">The object delete count did not return a number.</string>
  79. <string id="updateCommand.NAN" usage="A CM update request returns a number of objects affected" errorCode="4001">The object update count did not return a number.</string>
  80. <string id="DispatcherConfiguration.wrongObjectType" errorCode="4002">The object from <param name="0"/> is of type <param name="1"/>. Expecting type: <param name="2"/>
  81. </string>
  82. <string id="DispatcherConfiguration.objectNotFound" errorCode="4003">The requested object does not exist: <param name="0"/>.</string>
  83. <string id="ProcessManager.performanceUpdateFailed" errorCode="4004">Unable to update Report Server performance data: </string>
  84. <string id="ProcessManager.performanceUpdateSucceeded" errorCode="4005">successful updated Report Server performance data.</string>
  85. <string id="NO_ACTIVE_CM" errorCode="4006">Unable to determine the active Content Manager. Will retry periodically.</string>
  86. <string id="electionFailed" errorCode="4007">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.</string>
  87. </section>
  88. <section name="HDL" usage="This section is for mesages generated by the dispatcher handlers">
  89. <string id="ServiceLookupHandler.start">Handling request for URI: <param name="0"/>
  90. </string>
  91. <string id="ServiceLookupHandler.finish">Finished handling request for URI: <param name="0"/>
  92. </string>
  93. <string id="DISPATCHER_ISREADY">The dispatcher is ready to process requests.</string>
  94. </section>
  95. <section name="ERR" usage="This section is Dispatcher error messages" type="Messages">
  96. <string id="ENGINE_NOT_INITIALIZED" type="String" errorCode="2000">The dispatcher did not initialize.</string>
  97. <string id="STOPPED" errorCode="2001">Unable to execute request because the dispatcher or provider has been stopped.</string>
  98. <string id="NO_PROCESS" errorCode="2002">Unable to execute the request because there were no connections to the process available within the configured time limit.</string>
  99. <string id="E_POGO_CHANNEL_SEND_FAILURE" errorCode="2003">Unable to write a request.</string>
  100. <string id="E_POGO_CHANNEL_RECV_FAILURE" errorCode="2004">Unable to read a response.</string>
  101. <string id="E_POGO_RESPONSE_IO_ERROR" errorCode="2005">Unable to write a response to the client.</string>
  102. <string id="E_DISPATCHER_BAD_REFRESH_MISSING_ELEMENT" errorCode="2006">The dispatcher received an invalid refresh request. The request did not contain a required element or attribute named <param name="elementname"/>.</string>
  103. <string id="UNABLE_TO_REFRESH_DISPATCHER_STATUS" errorCode="2007">The dispatcher is unable to process a refresh message.</string>
  104. <string id="UNKNOWN_SERVICE" errorCode="2008">The dispatcher is unable to process the request. The request is directed to an unknown service name: <param name="0"/>.</string>
  105. <string id="UNKNOWN_ACTION" errorCode="2010">The request action "<param name="0"/>" is unknown.</string>
  106. <string id="NO_NODES_TO_FORWARD_TO" type="String" errorCode="2014">Unable to load balance the request because no nodes in the cluster are available, or no nodes are configured for the service: <param name="0" type="string"/>.</string>
  107. <string id="MALFORMED_REQUEST" errorCode="2015">The SOAP request is malformed.</string>
  108. <string id="UNABLE_TO_LOGOFF" errorCode="2016">Unable to logout.</string>
  109. <string id="UNABLE_TO_RETRIEVE_DATA" errorCode="2017">Unable to retrieve the data requested from Content Manager.</string>
  110. <string id="OBJECT_NOT_FOUND" errorCode="2018">The object "<param name="0"/>" can not be found in Content Manager or the data property is empty.</string>
  111. <string id="NO_SUCH_CLUSTER" errorCode="2019">There is no cluster named <param name="0"/> configured. The dispatcher may not have finished initialization.</string>
  112. <string id="NO_CANDIDATES" errorCode="2020">There are no nodes configured or available to process requests for the provider named <param name="0"/>.</string>
  113. <string id="NO_PROVIDER_MAPPING" errorCode="2021">There is no mapping to a provider for requests aimed at <param name="0"/>.</string>
  114. <string id="CANNOT_READ_WSDL" errorCode="2023">Unable to load the IBM Cognos WSDL. Please check your configuration.</string>
  115. <string id="RegexFileCleaner.missingPath" errorCode="2025">Parameter 'path' is missing in configuration file of the temporary file cleanup service.</string>
  116. <string id="RegexFileCleaner.badPath" errorCode="2026">Cleanup path does not exist.</string>
  117. <string id="RegexFileCleaner.badExpression" errorCode="2028">Bad regular expression for file names: </string>
  118. <string id="BibSrvStarter.executeFailed" errorCode="2029">Execute failed, program name: </string>
  119. <string id="BibSrvStarter.badResponse" errorCode="2030">Bad response code from child process: </string>
  120. <string id="BibSrvStarter.childProcessFailed" errorCode="2031">Unable to start or connect to child process.</string>
  121. <string id="BibSrvStarter.childProcessStopFailed" errorCode="2032">Unable to send stop request to child process.</string>
  122. <string id="BibSrvStarter.badXPath" errorCode="2033">Jaxen/XPath problem.</string>
  123. <string id="BibSrvStarter.badTCPBufferSize" errorCode="2034">Bad TCP buffer size parameter.</string>
  124. <string id="HttpToolError.CHUNKED_AND_LENGTH" errorCode="2035">Both chunked encoding and content-length were specified.</string>
  125. <string id="HttpToolError.HEADER_LINE_TOO_LONG" errorCode="2036">HTTP header was longer than internal buffer size.</string>
  126. <string id="HttpToolError.EXPECTING_CHUNKSIZE" errorCode="2037">Chunk size expected but not found.</string>
  127. <string id="HttpToolError.RIDICULOUS_CHUNKSIZE" errorCode="2038">Chunk size too big.</string>
  128. <string id="HttpToolError.LINE_TOO_LONG" errorCode="2039">HTTP line was longer than internal buffer size.</string>
  129. <string id="HttpToolError.MALFORMED_CONTENT_LENGTH" errorCode="2040">Incorrect content-length header syntax.</string>
  130. <string id="HttpToolError.UNBALANCED_MULTIPART" errorCode="2041">Unbalanced Mulitpart boundaries. Malformed Multipart message.</string>
  131. <string id="HttpToolError.BAD_RESPONSE" errorCode="2042">Incorrect response line. A proper HTTP response was not received.</string>
  132. <string id="HttpToolError.READ_FAILED" errorCode="2043">Unable to read from the HTTP connection.</string>
  133. <string id="LengthLimitedInputStream.unexpectedEOS" errorCode="2044">Unexpected end of input stream.</string>
  134. <string id="ProcessMTAHandler.badConfiguration" errorCode="2045">A dispatcher handler is misconfigured.</string>
  135. <string id="ProcessMTAHandler.missingEXE_NAME" errorCode="2046">Failed to initialize handler, need exe_name: </string>
  136. <string id="ProcessMTAHandler.missingWORKER_REQUEST_PATH" errorCode="2047">Unable to initialize handler, need worker_request_path: </string>
  137. <string id="ProcessMTAHandler.configError" errorCode="2048">Unable to initialize handler: </string>
  138. <string id="ConfigStoreServlet.IPFError" errorCode="2049">Unable to initialize the Cognos IPF.</string>
  139. <string id="ConfigStoreServlet.P2PDDeployPropertiesNotLoaded" errorCode="2050">Unable to load Properties file p2pd_deploy_defaults.</string>
  140. <string id="ForceConfigRefreshHandler.IOError" errorCode="2051">IO error occurred while updating configuration.</string>
  141. <string id="CR1CookieCorrupted" errorCode="2052">The IBM Cognos cookie is corrupt.</string>
  142. <string id="TestStoppedWarpHandler.missingHandler" errorCode="2053">
  143. <param name="0"/>The pogo handler configuration is incorrect.</string>
  144. <string id="ConnectionPool.poolDisposed" errorCode="2054">The connection pool has been shutdown.</string>
  145. <string id="ReportServerHandler.badConfig" errorCode="2055">The report server handler configuration cannot be parsed. Please check "pogo.xml".</string>
  146. <string id="ReportServerHandler.noResponse" errorCode="2056">The Report Server is not responding.</string>
  147. <string id="ReportServerHandler.noResponseWithPID" errorCode="2074">Failed to receive a timely response from an external process with a PID <param name="0"/>. Ensure that the process with a process ID <param name="0"/> 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</string>
  148. <string id="ReportServerHandler.staleRequest" errorCode="2057">The asynchronous request is stale. The request cannot be processed.</string>
  149. <string id="AbortIfSuspendedHandler.serviceStopped" errorCode="2059">The requested service has been stopped. The request cannot be completed.</string>
  150. <string id="NO_RESPONSE" errorCode="2022">No response generated. This may be due to an incorrect configuration, a damaged installation, or because the dispatcher did not finish initializing.</string>
  151. <string id="RegexFileCleaner.dontUse" errorCode="2027">This servlet can not be accessed directly.</string>
  152. <string id="BasicHandler.cantService" errorCode="2058">The dispatcher encountered an error while servicing a request: <param name="0"/>.
  153. </string>
  154. <string id="PogoServlet.noSOAPAction" errorCode="2060">The request is invalid. No SOAPAction or "b_action" parameter is found in the request.</string>
  155. <string id="UNABLE_TO_TALK_TO_CM_FOR_AUTHENTICATION" errorCode="2009">A request to authenticate the user in Content Manager failed. </string>
  156. <string id="PROBABLE_AUTHENTICATION_FAULT" errorCode="2061">An authentication request to Content Manager produced an error. The logon page will appear.</string>
  157. <string id="SystemServiceHandler.noOperation" errorCode="2062">The SOAP request is invalid. No operation was found in the SOAP body or the operation name is incorrect.</string>
  158. <string id="SystemServiceHandler.requestFailed" errorCode="2063">The request failed. Please verify the input parameters and try again.</string>
  159. <string id="AdminCommand.requestFailed" errorCode="2064">The administration request failed. Please verify the input parameters and try again.</string>
  160. <string id="DISPATCHER_NOT_YET" errorCode="2109">The dispatcher cannot service the request at this time. The dispatcher is still initializing. Contact your administrator if this problem persists.</string>
  161. <string id="ReportServerHandler.badResponse" errorCode="2065">The response from Report Server is not well formed. No response envelope is received.</string>
  162. <string id="DefaultHandlerService.threwException" errorCode="2066">The handler <param name="0"/> threw an exception during services initialization.</string>
  163. <string id="MD_PROVIDER_NOT_INSTALLED" errorCode="2067">Unable to process the request because the MetadataService is not installed.</string>
  164. <string id="AdminCommand.handoffFailed" errorCode="2068">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.</string>
  165. <string id="CMHandler.reportNotFound" errorCode="2069">There are no report output versions available for this report.</string>
  166. <string id="SERVICE_DIDNT_STOP" errorCode="2070">The service <param name="0"/> did not stop within a reasonable amount of time.</string>
  167. <string id="GetFormatSamples.noLocale" errorCode="2071">Unable to retrieve the requested format sample. No locale information was found in the user preferences</string>
  168. <string id="CANNOT_FORWARD_TO_ABSOLUTE_AFFINITY_NODE" errorCode="2072">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.</string>
  169. <string id="ConfigStoreServlet.ConfigPropertiesMissing" errorCode="2073">Unable to retrieve all startup configuration parameters.</string>
  170. <string id="notifyHandoffFailed" errorCode="2076">Error propagating notify command to: <param name="0"/>
  171. </string>
  172. <string id="ReportServerHandler.missingProcess" type="String" errorCode="2077">Failed to forward the request because the associated external process with PID <param name="0"/> 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.</string>
  173. <string id="ReportServerHandler.missingConversationContext" errorCode="2078">Unable to proceed with the request. The mandatory header "conversationContext" is missing from the request. </string>
  174. <string id="CAF_VALIDATION_FAILURE" errorCode="2079">Firewall Security Rejection. Your request was rejected by the security firewall.</string>
  175. <string id="CAF_ERROR" type="String" errorCode="2080">Firewall Security Error. A security firewall error occurred. Error status: </string>
  176. <string id="CAF_CONFIGURATION_ERROR" type="String" errorCode="2081">Firewall Security Configuration Error. A security firewall configuration error occurred. Error status: </string>
  177. <string id="CAF_SECURELOG_MSG" type="String" errorCode="2082">An error has occurred. Please contact your administrator. The complete error has been logged by CAF with SecureErrorID: </string>
  178. <string id="TARGET_GUID_MISMATCH" errorCode="2083">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.</string>
  179. <string id="UNKNOWN_SOURCE_GUID" errorCode="2084">The current dispatcher received a request from another dispatcher with GUID=<param name="0"/>, 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.</string>
  180. <string id="CMQueueTimeout" errorCode="2085">Request timed out. Unable to find active CM.</string>
  181. <string id="FormRequestProcessor.unsupportedEncoding" errorCode="2086">Unable to process the request because the encoding '<param name="0"/>' is not supported.</string>
  182. <string id="ReportServerHandler.executionLimitReached" type="String" errorCode="2087">The request has exceeded the execution time limit. It will be cancelled.</string>
  183. <string id="LoadBalanceHandler.unknownServerGroup" type="String" errorCode="2088">The requested Server Group '<param name="0" type="string"/>' does not exist.</string>
  184. <string id="MISSING_REQUEST_CONVERSATION_ID" type="String" errorCode="2089">The request cannot be processed because it is malformed. It is missing the element "conversationContext/id" that is mandatory in affine requests.</string>
  185. <string id="MISSING_REQUEST_CONVERSATION_NODEID" type="String" errorCode="2090">The request cannot be processed because it is malformed. It is missing the element "conversationContext/nodeId" that is mandatory in affine requests.</string>
  186. <string id="INVALID_REQUEST_CONVERSATION_PROCESSID" type="String" errorCode="2091">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.</string>
  187. <string id="INVALID_REQUEST_CONVERSATION_AFFINITYSTRENGTH" type="String" errorCode="2092">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.</string>
  188. <string id="mapPreview.badResponseFromRS" type="String" errorCode="2093">The response from reportService does not contain a getMapPreviewResponse element.</string>
  189. <string id="mapPreview.emptyImageData" type="String" errorCode="2094">The response from report server contains an empty getMapPreviewResponse element.</string>
  190. <string id="mapPreview.errorDecodingImage" type="String" errorCode="2095">Exception occurred processing the map preview image data.</string>
  191. <string id="mapPreview.badRequest" type="String" errorCode="2096">Malformed map preview request. getMapPreview is missing from URL or has no value.</string>
  192. <string id="SERVICE_CANNOT_BE_STOPPED" type="String" errorCode="2097">This service cannot be stopped.</string>
  193. <string id="BasicHandler.noReporter" type="String" errorCode="2098">A reporter instance must be associated with this handler for it to be marked as not startable.</string>
  194. <string id="StartServiceAdminCommand.startFailed" type="String" errorCode="2099">The service failed to start: <param name="0"/>.</string>
  195. <string id="StopServiceAdminCommand.stopFailed" type="String" errorCode="2100">The service failed to stop: <param name="0"/>.</string>
  196. <string id="NOT_FOUND" type="String" errorCode="2101">Your request was invalid. Please contact your administrator.</string>
  197. <string id="InteractiveReportMonitor.cancelSuceeded" type="String" errorCode="2102">The cancel request succeeded.</string>
  198. <string id="InteractiveReportMonitor.cancelFailed" type="String" errorCode="2103">The cancel request failed.</string>
  199. <string id="InteractiveReportMonitor.reportNotFound" type="String" errorCode="2104">The report was not found.</string>
  200. <string id="RequestInvoker.noResponse" type="String" errorCode="2105">The dispatcher was unable to communicate with the Report Server with pid <param name="0"/>. Diagnostic files may have been generated, please check the "bin" directory.</string>
  201. <string id="FormRequestProcessor.InvalidUrlSoapEncoding" type="String" errorCode="2106">URL SOAP Encoding is not valid.</string>
  202. <string id="UserCapabilitiesCache.parseError" type="String" errorCode="2107">The User Capabilities Cache cookie cannot be decoded.</string>
  203. <string id="UserCapabilitiesCache.encodeError" type="String" errorCode="2108">The User Capabilities Cache cookie cannot be encoded.</string>
  204. <string id="REQUEST_CANCELLED" type="String" errorCode="2200">The request has been cancelled.</string>
  205. <string id="NO_SUCH_CONVERSATION" type="String" errorCode="2201">The request cannot be processed because it refers to non-existent conversation.</string>
  206. <string id="NO_CONVERSATION_ID" type="String" errorCode="2202">The request cannot be processed because it is an absolute affinity request but does not specify a conversation.</string>
  207. <string id="contentManagerCacheService.disabled" type="String" errorCode="2203">The contentManagerCacheService is disabled.</string>
  208. <string id="ReportServerHandler.LimitedInputStreamError" type="String" errorCode="2204">The report has exceeded the size limit. Please contact your administrator to increase the limit.</string>
  209. <string id="MAXIMUM_HOP_COUNT" type="String" errorCode="2205">Maximum hop count exceeded. Please contact your administrator. Hop count maximum limit is</string>
  210. </section>
  211. <section name="EPG" usage="stuff that appears in the last chance error page" type="Messages">
  212. <string id="LANG_DIR">en/</string>
  213. <string id="ERRPAGE_HTML_TITLE">Error - IBM Cognos</string>
  214. <string id="ERRPAGE_APPNAME">IBM Cognos</string>
  215. <string id="ERRPAGE_UNEXPECTED">An error has occurred.</string>
  216. <string id="ERRPAGE_HELP">Help</string>
  217. <string id="ERRPAGE_CONTACTADMIN">Please try again or contact your administrator.</string>
  218. <string id="LABEL_OK">OK</string>
  219. <string id="CAF_ERRPAGE_CONTACTADMIN">CAF rejection details are available in the log. Please contact your administrator.</string>
  220. </section>
  221. <section name="GTY" usage="Messages from the Servlet Gateway" type="Messages">
  222. <string id="Gateway.communicationFailed" errorCode="5000">Communication failed while attempting to forward the request to the dispatcher. Ensure that IBM Cognos is running.</string>
  223. <string id="Gateway.resendFailed" errorCode="5001">Cannot forward the request to dispatcher even after retrying.</string>
  224. <string id="Gateway.cannotResend" errorCode="5002">Cannot resend request because the request was not saved.</string>
  225. <string id="Gateway.noActiveDispatcher" errorCode="5003">The request cannot be forwarded. No configured dispatchers are currently running.</string>
  226. <string id="Gateway.communicationFailedTryAgain" errorCode="5004">Communication failed while attempting to forward the request to the dispatcher. This may be due to dispatcher failover: Please try again.</string>
  227. </section>
  228. <section name="SYS" usage="Messages releated to the system as a whole" type="Messages">
  229. <string id="System.Started" errorCode="6000">The product is ready to use.</string>
  230. <string id="System.Stopped" errorCode="6001">The product is shutting down.</string>
  231. </section>
  232. <section name="TST" usage="This section is for test messages in dispatcher Unit Tests (DON'T REMOVE but translation not needed)" type="Messages">
  233. <string id="test.aTestMessage">Hello World!</string>
  234. </section>
  235. </component>
  236. </stringTable>