pfmsgs_en.properties 6.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124
  1. #
  2. # Licensed Materials - Property of IBM
  3. # IBM Cognos Products: localizationkit
  4. # (C) Copyright IBM Corp. 2005, 2016
  5. # US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
  6. #
  7. ## DO NOT EDIT!
  8. ## Generated using CCLXmlToProperties.xslt
  9. ## END OF WARNING
  10. ##
  11. ## Component: PF
  12. ##
  13. ## Description: Portal frameworks components
  14. ##
  15. #
  16. # Section: PRO
  17. #
  18. # Description: Fragments producer error messages
  19. #
  20. pf.fragment.producer.executionfailed = PF-PRO-6100 Unable to run the fragment producer.
  21. #
  22. # Section: SRV
  23. #
  24. # Description: Fragments server error messages
  25. #
  26. pf.fragment.server.executionfailed = PF-SRV-6110 Run failed.
  27. pf.fragment.server.invalidconfiguration = PF-SRV-6111 Configuration is not valid.
  28. pf.fragment.server.invaliddocument = PF-SRV-6112 Unrecognizable XML document starting with the element '{0}'.
  29. pf.fragment.server.rewritefailed = PF-SRV-6113 Unable to rewrite URLs in received markup.
  30. pf.fragment.server.unsupporteddocument = PF-SRV-6114 The document type is not supported.
  31. pf.fragment.server.expectingxmldocument = PF-SRV-6115 XML document was expected. Received '{0}' document.
  32. pf.fragment.server.notargetdocument = PF-SRV-6116 Unable to process the document, target is not valid or the target was not received.
  33. pf.fragment.server.invalidxmldocument.details = PF-SRV-6117 XML parsing error in received document (at line {0}, column {1}, offset {2}).
  34. pf.fragment.server.invalidxmldocument = PF-SRV-6118 XML parsing error.
  35. pf.fragment.server.receivedfault = PF-SRV-6119 Received remote fault: {0}
  36. pf.fragment.server.circularreference = PF-SRV-6120 The content of this portlet cannot be displayed because of a recursive reference.
  37. pf.fragment.server.maxdepthreached = PF-SRV-6121 Unable to process document, the maximum depth of {0} levels was reached.
  38. pf.fragment.server.invalidcredentials = PF-SRV-6122 The user credentials are not valid.
  39. pf.fragment.server.notsufficientcapabilities_portlet = PF-SRV-6123 You do not have sufficient capabilities to access this portlet.
  40. pf.fragment.server.notsufficientcapabilities_page = PF-SRV-6124 You do not have sufficient capabilities to access this page.
  41. pf.fragment.server.sessioncapabilityviolation = PF-SRV-6125 A security violation occurred. The session capability information failed to verify.
  42. #
  43. # Section: BRG
  44. #
  45. # Description: WSRP bridge error messages
  46. #
  47. pf.fragment.bridge.executionfailed = PF-BRG-6140 Not able to run the request.
  48. pf.fragment.bridge.wsrp.operationfailed = PF-BRG-6141 The operation did not run.
  49. pf.fragment.bridge.io.error = PF-BRG-6142 The request encountered an Input/Output error.
  50. pf.fragment.bridge.xml.error = PF-BRG-6143 The request encountered an error while processing XML content.
  51. #
  52. # Section: LOC
  53. #
  54. # Description: Localization error message
  55. #
  56. pf.fragment.loc.message.invalid = PF-LOC-6150 The message file '{filename}' is not valid.
  57. pf.fragment.loc.xmlfailed = PF-LOC-6151 An error occurred while localizing an XML input.
  58. #
  59. # Section: CMP
  60. #
  61. # Description: CM Provider error messages
  62. #
  63. pf.fragment.cmprovider.page.empty = No content.
  64. pf.fragment.cmprovider.page.insufficient.permissions = This page cannot be displayed. It may be deleted or you may not have sufficient privileges to see it.
  65. pf.fragment.cmprovider.fragment.insufficient.permissions = This portlet cannot be displayed. It may be deleted or you may not have sufficient privileges to see it.
  66. pf.fragment.cmprovider.fragment.disabled = This portlet cannot be displayed because it is not enabled.
  67. #
  68. # Section: VAL
  69. #
  70. # Description: Validation Provider error messages
  71. #
  72. pf.fragment.validation.initfailed = PF-VAL-6160 Failed initializing validation.
  73. pf.fragment.validation.initgeneralerror = PF-VAL-6161 General exception during initializing.
  74. pf.fragment.validation.compilefailed = PF-VAL-6162 Compile failed.
  75. pf.fragment.validation.compilegeneralerror = PF-VAL-6163 General exception during compile.
  76. pf.fragment.validation.compileconversionfailed = PF-VAL-6164 General exception during compile array conversion.
  77. pf.fragment.validation.verifyfailed = PF-VAL-6165 Security Rejection. Your request was rejected because it failed the fragment input validation.\nRejection details are available in the log. Please contact your administrator.
  78. pf.fragment.validation.verifyerror = PF-VAL-6166 Verification failed.
  79. pf.fragment.validation.verifygeneralerror = PF-VAL-6167 General exception during verification.
  80. pf.fragment.validation.signerror = PF-VAL-6168 Parameter signing failed.
  81. pf.fragment.validation.signgeneralerror = PF-VAL-6169 General exception during parameter signing.
  82. pf.fragment.validation.filereaderror = PF-VAL-6170 Error reading static validation document file.
  83. pf.fragment.validation.metaretrievalerror = PF-VAL-6171 Error retrieving metadata for the target fragment.
  84. pf.fragment.validation.unsignerror = PF-VAL-6172 Parameter unsigning failed.
  85. #
  86. # Section: COM
  87. #
  88. # Description: Common error messages
  89. #
  90. pf.common.xslt.notfound = PF-COM-6200 The stylesheet '{0}' could not be found.
  91. pf.common.xslt.loaderror = PF-COM-6201 An error occurred while loading the stylesheet '{0}'.
  92. pf.common.soapfault.parse.error = PF-COM-6202 An error occurred while parsing a soap fault.
  93. pf.common.securelog.errormsg = PF-COM-6203 The complete error has been logged by CAF with SecureErrorID: {0}
  94. pf.common.securelog.errormsg.noid = PF-COM-6204 The complete error has been logged.
  95. #
  96. # Section: PIP
  97. #
  98. # Description: Common pipeline error messages
  99. #
  100. pf.pipeline.process.init.failed = PF-PIP-6300 The process with name '{0}' failed to initialize.
  101. pf.pipeline.process.error = PF-PIP-6301 The process with name '{0}' failed to execute. A more detailed error message will be logged.
  102. pf.pipeline.process.io.error = PF-PIP-6302 The process with name '{0}' encountered an Input/Output error.
  103. pf.pipeline.process.xml.error = PF-PIP-6303 The process with name '{0}' encountered an error while processing XML content.
  104. #
  105. # Section: SKN
  106. #
  107. # Description: Skin service error messages
  108. #
  109. pf.skin.upgrade.error = PF-SKN-6400 An exception occurred while upgrading the skin from version '{0}' to '{1}'.
  110. pf.skin.read.error = PF-SKN-6401 An exception occurred while reading the skin specification.
  111. pf.skin.upgrade.spec.read.error = PF-SKN-6402 An exception occurred while reading the skin upgrade specification.
  112. pf.skin.upgrade.baseskin.read.error = PF-SKN-6403 An exception occurred while reading the upgrade base skin.
  113. pf.skin.upgrade.invalid.spec = PF-SKN-6404 Invalid skin upgrade specification. The element with name '{0}' is missing