CCMS_GRMG - Alert-Nachtrichten f�r GRMG-Szenarien (Verf�gbarkeits�berw.)
The following messages are stored in message class CCMS_GRMG: Alert-Nachtrichten f�r GRMG-Szenarien (Verf�gbarkeits�berw.).
It is part of development package SMOI in software component BC-CCM-MON. This development package consists of objects that can be grouped under "CCMS: Monitoring Architecture".
It is part of development package SMOI in software component BC-CCM-MON. This development package consists of objects that can be grouped under "CCMS: Monitoring Architecture".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | &1&2&3&4 |
| 002 | &1: &2&3&4 |
| 003 | &1: &2 &3 &4 |
| 004 | &1&2&3: &4 |
| 005 | &1 &2 &3: &4 |
| 006 | &1 &2: &3 &4 |
| 008 | GRMG Reliability and Resets |
| 009 | GRMG: Could not create reset tool MTE: &1 |
| 010 | GRMG: At least one GRMG scenario reset from FATAL_ERROR |
| 011 | GRMG: Scenario &1 reset by method status FATAL_ERROR |
| 012 | GRMG: Could not report message: scenario &1 error &2 |
| 013 | GRMG: Could not reset GRMG_TRIGGER for scenario &1 |
| 014 | GRMG: GRMG_TRIGGER execution successful; no scenario in FATAL_ERROR |
| 015 | GRMG: Could not report performance value: scenario &1 error &2 |
| 016 | GRMG: No GRMG scenarios found on this instance |
| 017 | GRMG: Only abbreviated Web service context name stored: &1 &2 &3 |
| 019 | Error when building SAP GUI controls; update SAP GUI |
| 020 | RFC connection to &1 is available |
| 021 | RFC connection to &1 is not available: &2 |
| 022 | System error in GRMG application; initial context missing (zero): &1 |
| 023 | Beans are not available |
| 024 | Beans are not deployed: &1 |
| 025 | Cannot instantiate beans: &1 |
| 026 | Beans are available |
| 027 | Connector &1 is available |
| 028 | Connector &1 is not deployed: &2 |
| 029 | Connector &1 could not create a connection: &2 |
| 030 | Connector &1 does not support relational access |
| 031 | MMR is not available: &1 |
| 032 | MMR is not available: could not create instance |
| 033 | MMR is available |
| 050 | No access to SLD - check transaction SLDAPICUST. &1&2 |
| 051 | SLD did not report any ABAP systems of class SAP_BCSystem. &1. &2. |
| 052 | SLD did not report any instances or HTTP/S ports for &3. &1. &2 &4. |
| 053 | SLD reports no host for system &1 instance &2. &3 &4. |
| 054 | SLD reports no TCP/IP port for system &1 instance &2. &3 &4. |
| 055 | CCMS is not reporting any monitored systems; check system list in RZ21 |
| 056 | CCMS is not reporting any instances or HTTP/S ports for &1. &2 &3. |
| 057 | CCMS is not reporting any host for system &1 instance &2. &3 &4. |
| 058 | CCMS is not reporting any TCP/IP ports for system &1 instance &2. &3 &4. |
| 059 | Logon unsuccessful or WSIL reports no Web services for system &1 |
| 060 | No service end points selected |
| 061 | Service&1 activated as scenario name &2 version &3. &4 |
| 062 | Service &1 (scenario name &2 version &3) deactivated |
| 063 | First select a system |
| 064 | Could not determine system SID; select a system |
| 065 | Response header: &1 &2 |
| 066 | No response headers confirmed |
| 067 | Complete system details |
| 068 | First expand Web service &1 so that endpoint URLs are visible |
| 069 | Activate the HTTP service in this system (transaction SMICM) |
| 070 | Error in ICM; cannot start Web Dynpro application; check TX SMICM |
| 071 | Error in GRMG Web Dynpro programs for Web services; contact SAP |
| 100 | Break in monitoring; scenario execution stopped temporarily |
| 101 | Scenario &1, version &2 copied |
| 102 | RFC destination &1 does not exist in system |
| 103 | You are not authorized to execute external command &1 |
| 104 | External command &1 for &2 not defined in system; see transaction SM69 |
| 105 | Could not extract host name from URL; check URL |
| 106 | Could not execute external command &1 |
| 107 | Invalid scenario type: &1 |
| 150 | HTTP status code: &1 HTTP status reason &2 |
| 151 | GRMG check indicator chains specified, but HTTP method HEAD used |
| 152 | GRMG check indicator chain - &1 &2 |
| 160 | GRMG: availability of monitored component (%) |
| 161 | GRMG: runtime of GRMG or GRMG-lite query; send/receive |
| 162 | GRMG: status or error messages from monitored component |
| 163 | Upload of new GRMG scenarios by CCMS agents can take some time... |
| 164 | &1 new or modified GRMG scenario(s) found |
| 165 | GRMG could not access password (type PW) in Secure Storage |
| 166 | Component &1 cannot exist in different versions in &2 |
| 167 | You cannot modify the description of an existing component |
| 168 | Data record already exists; component &1, property &2 |
| 169 | Invalid character &1 in &2 |
| 170 | No systems of system group found |
| 180 | OK: default value set |
| 181 | Error: System property DocumentBuilderFactory is incorrect |
| 182 | Error: system property SAXParserFactory is incorrect |
| 183 | Error: system property TransformerFactory is incorrect |
| 184 | Exception: defaultTrace |
| 185 | No exceptions occurred |
| 186 | Error: unexpected response |
| 187 | Error: heartbeat failed |
| 188 | Error: Web service call failed |
| 189 | Error: No Web service port |
| 190 | Error: No host or no port |
| 200 | All components (HttpComunicator, Rule Engine ...) running |
| 201 | Some or all components are not running |
| 250 | KM connected |
| 251 | KM not connected |
| 265 | LONGRUNNING_JOBS: JOB_SELECT for active jobs exception: &1 |
| 266 | LONGRUNNING_JOBS: SALC_GET_MTE_BY_CLASS exception: &1 |
| 267 | LONGRUNNING_JOBS: Could not read system-wide background context |
| 268 | LONGRUNNING_JOBS: Invalid custmomer Customizing: &1 |
| 269 | LONGRUNNING_JOBS: Checking job &1 &2 &3 &4 |
| 270 | LONGRUNNING_JOBS: SALI error &1 |
| 271 | Job &1 started on &2 at &3 has exceeded maximum runtime &4 |
| 272 | CCMS monitoring of long-running programs: backgr. jobs with long runtimes |
| 273 | Long-running job &1 started on &2 at &3 is no longer active |
| 274 | LONGRUNNING_JOBS: ALLONGJOB_CTRL Customizing invalid: &1 |
| 275 | Alert for long-running job &1 count &2 is not completed - job active |
| 276 | Alert for job &1 count &2 is not completed - previously completed? |
| 277 | There are currently no background jobs active |
| 278 | Currently no jobs exceed the threshold values for maximum runtime |
| 300 | HTML tag not relevant for evaluation; tag name: &1 |
| 301 | Content type not relevant for evaluation; tag name &1 content type: &2 |
| 302 | HTML tag is empty; source character string: &1&2&3 |
| 303 | Resolution of HTML tag started: &1 |
| 304 | Resolution of HTML tag &1 ended: tag is not relevant |
| 305 | Resolving relevant HTML tag &1 |
| 306 | HTML tag inconsistent: source character string &1&2&3 |
| 307 | HTML tag content type is empty; source character string &1&2&3 |
| 308 | Resolving relevant content type &1 |
| 309 | HTML content type is not 'text' - content is not evaluated |
| 310 | Error when determining the GRMG tag reference: source text &1&2&3 |
| 311 | GRMG reference record initial; however, applicable record was determined |
| 312 | Content source attribute found but empty: source text: &1&2&3 |
| 313 | Resolution of HTML document started: URL &1 response &2 |
| 314 | GRMG HTML document property &1 set to &2 |
| 315 | GRMG: Base HTML tag is invalid. Tag: &1 |
| 316 | Base URL used from &1 |
| 317 | No document URL: resolved document URL is empty. |
| 318 | Response character string is empty or does not contain any HTML tags &1&2 |
| 319 | Response string does not contain an end tag or open tag without '>' &1&2 |
| 320 | Could not determine URL for the tag &1 |
| 321 | Parsing URL: &1&2 |
| 322 | Invalid URL: &1 invalid. URL: &2&3 |
| 323 | Executing Set_Effective_URL DB URL &1&2 CS URL &3&4 |
| 324 | Corrupt HTML tag: could not determine tag name: &1 |
| 325 | Corrupt HTML tag: empty tag name: &1 |
| 326 | Internal error in subroutine &1 error text &2 |
| 327 | Starting evaluation of content URLs for &1 |
| 328 | Evaluating response character string for URL &1&2&3 |
| 329 | Checking response character string for HTML tags to be processed |
| 330 | HTML FRAME, IFRAME, or OBJECT found and being evaluated: &1&2&3&4 |
| 331 | Internal GRMG processing of the HTML tags was specified |
| 332 | Processing of the HTML tags in an external browser was specified |
| 333 | Extended response character string: &1&2&3&4 |
| 334 | Problem in postprocessing scenario &1 context &2 - no extended response |
| 335 | Response character string: &1&2&3&4 |
| 336 | SET_EFFECTIVE_URL returns URL &2&3&4 for tag &1 |
| 337 | SET_EFFECTIVE_URL completed for tag &1 |
| 338 | Storing initial response character string: &1&2&3&4 |
| 339 | Processing redirect; HTTP status code &1. Request URL &1&2&3. |
| 340 | Redirect URL: &1&2&3&4 |
| 341 | Redirect response character string: &1&2&3&4 |
| 342 | GRMG could not read HTTP RFC dest. &1, no HTML tag resolution possible |
| 343 | GRMG: RFC dest. &1 uses logon data of &2, but password cannot be read |
| 344 | GRMG: Iteration &1 over response string of &2 |
| 345 | GRMG: Iteration stops with &1 recursions over response string of &2 |
| 346 | GRMG iteration &1 for &2 complete, iteration_count reduced by 1 |
| 350 | GRMG: Error when reading &1 from SLD for system &2 |
| 351 | GRMG: SLD reported no objects of type &1 found |
| 352 | GRMG: Check SLD-API - call transaction SLDAPICUST |
| 353 | GRMG: &1 not found in SLD handle &2 - SLD, system &3 skipped |
| 354 | GRMG: No remote systems are monitored by CCMS in this system |
| 355 | GRMG: Scenarios can only be set up for local Web services |
| 356 | GRMG: Cannot determine &1 with CCMS resources, system &2 skipped |
| 357 | GRMG: Error when reading &1 for system &2 in CCMS |
| 358 | GRMG: Check remote monitoring connection for system &1 in transact. RZ21 |
| 359 | GRMG: Could not set up a connection to SLD |
| 360 | GRMG: No SLD handle for object &1 name &2; see CCMS self-monitoring |
| 500 | Scenario &1 has been stopped and will not be executed |
| 550 | NWCPM BC-XOM Web service is available |
| 551 | NWCPM BC-XOM Web service is not available |
| 552 | NWCPM Management Web service is available |
| 553 | NWCPM Management Web service is not available |
| 554 | NWCPM Callback service is available |
| 555 | NWCPM Callback service is not available |
| 556 | ### LPO Messages - Vibhuti Chaturvedi |
| 557 | LPO is not available |
| 558 | LPO is running and available |
| 559 | Heartbeat monitoring has errors; create support msg., component XAP-LPO |
| 560 | Check LPO host. If down, restart. If up, support msg.: component XAP-LPO |
| 600 | GRMG is already being executed in the background: &1 &2 &3 &4 |
| 601 | Check GRMG background job &1 &2&3 |
| 602 | Internal error when querying job parameters |
| 603 | Standard method GRMG_TRIGGER not found, maintain in RZ21 |
| 604 | CCMS internal error when updating method GRMG_TRIGGER: &1 &2 |
| 605 | Error when scheduling the GRMG background job: &1 &2 &3 |
| 606 | Job &1 not released; release in transaction SM37 |
| 607 | Job &1 cannot run in the background |
| 608 | Error when deleting job &1; delete in SM37 |
| 609 | Background error during job search: check &1 in SM37, delete if necessary |
| 865 | LONGRUNNING_JOBS: JOB_SELECT for active jobs exception: &1 |
| 866 | LONGRUNNING_JOBS: SALC_GET_MTE_BY_CLASS exception: &1 |
| 867 | LONGRUNNING_JOBS: Could not read system-wide background context |
| 868 | LONGRUNNING_JOBS: Invalid custmomer Customizing: &1 |
| 869 | LONGRUNNING_JOBS: Checking job &1 &2 &3 &4 |
| 870 | LONGRUNNING_JOBS: SALI error &1 |
| 871 | Job &1 started on &2 at &3 has exceeded maximum runtime &4 |
| 872 | CCMS monitoring of long-running programs: backgr. jobs with long runtimes |
| 873 | Long-running job &1 started on &2 at &3 is no longer active |
| 874 | LONGRUNNING_JOBS: ALLONGJOB_CTRL Customizing invalid: &1 |
| 875 | Alert for long-running job &1 count &2 will not be completed - job active |
| 876 | Alert for job &1 count &2 not completed - already completed earlier? |
| 877 | There are currently no background jobs active |
| 878 | Currently no job is exceeding the threshold values for maximum runtime |