RA - Monitoring-Infrastruktur Dialogmeldungen
The following messages are stored in message class RA: Monitoring-Infrastruktur Dialogmeldungen.
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 | Unable to read tree instance data |
001 | Unable to determine the name of the local monitoring segment |
002 | Unable to create monitoring context & |
003 | Unable to determine the class of MTE & |
004 | Unable to generate monitoring object & |
005 | Unable to construct MTE tree |
006 | Contexts and monitoring objects created |
007 | Value report failed |
008 | Unable to determine MTE of the monitoring context & |
009 | Error determining alert information (internal error) |
010 | Position the cursor on a node (MTE) |
011 | Node (MTE) data cannot be determined |
012 | Could not determine any information for multiple MTE nodes |
013 | Failed to determine alert data |
014 | Unable to display alert data |
015 | Unable to execute action - invalid work mode |
016 | Insufficient MTE information to be able to determine alert data |
017 | The properties of the MTE class are already in use |
018 | Select a node (MTE) or position cursor on a node (MTE) |
019 | Unable to execute action - invalid MTE tree instance |
020 | No alert data exists |
021 | Propagation of alert information in the tree failed |
022 | Failed to concatenate MTE trees |
023 | Failed to delete monitor |
024 | Failed to refresh MTE tree instance data |
025 | Failed to display an MTE tree |
026 | Unable to execute operation |
027 | Alerts Completed |
028 | No alerts were selected. Select alerts first |
029 | No SAP systems are currently configured |
030 | Failed to determine configured SAP system names |
031 | Unable to generate monitor (internal error) |
032 | Monitor & was deleted |
033 | Virtual (MTE) nodes or nodes with errors cannot be displayed |
034 | Virtual (MTE) nodes or nodes with errors are not permitted |
035 | Include nodes (MTE) in the monitor by selection |
036 | Node (MTE) entries for detail display missing |
037 | Node (MTE) detail display cannot be displayed |
038 | Only able to display details for attributes |
039 | Basic monitor data cannot be determined |
040 | The monitor was saved |
041 | The monitor was generated |
042 | Specify a monitor name |
043 | Attribute nodes could not be found |
044 | Select the alerts to be completed |
045 | Node (MTE) entries for analysis display missing |
046 | Node (MTE) entries for alert display missing |
047 | Unable to execute analysis |
048 | Analysis is only possible for summary, object and attribute nodes |
049 | Operation not possible for nodes (MTE) with errors |
050 | No properties can be maintained for the selected nodes (MTE) |
051 | & does not exist as attribute group for status attributes |
052 | General settings are already assigned MTE-specific |
053 | Failed to activate properties variant & |
054 | Properties variant & does not exist |
055 | Properties variant & already exists |
056 | Internal error occurred creating properties variant |
057 | Node (MTE) entries for configuring the alert generation missing |
058 | Node (MTE) status cannot be changed |
059 | Cannot configure alert generation for virtual nodes (MTE) or error nodes |
060 | Could not display nodes (MTE) with errors |
061 | Alert generation now permitted for specified nodes (MTE) |
062 | Alert generation now suppressed for specified nodes (MTE) |
063 | Unable to display nodes (MTE) for which the operation is invalid |
064 | Canceling operation |
065 | Node (MTE) specifications for deletion missing |
066 | Unable to delete nodes (MTE) |
067 | Cannot delete virtual nodes (MTE) or nodes with errors |
068 | Nodes (MTE) deleted or marked for deletion |
069 | Unable to reset nodes (MTE) |
070 | Cannot reset virtual nodes (MTE) or nodes with errors |
071 | Nodes (MTE) were reset |
072 | Node (MTE) specifications for reset missing |
073 | Unable to display the list with the selected nodes (MTE) |
074 | Cannot apply selections to the tree |
075 | Properties for & saved |
076 | Specify a monitor name |
077 | Specify a refresh time |
078 | Refresh time is not numerical |
079 | Refresh interval less than 60 seconds is not permitted |
080 | Data for method & saved |
081 | Release for method & saved |
082 | Caution: No definition exists for method & |
083 | Performance values were already assigned MTE-specific |
084 | Method assignment saved |
085 | No method assignment is stored in the DB for & |
086 | Node (MTE) is not assigned to a class |
087 | Program & does not exist |
088 | Method & not released as data collection method |
089 | Method & not released as auto-reaction method |
090 | Method & not released as analysis method |
091 | No entry exists in the DB for collection method assignment |
092 | No entry exists in the DB for auto-reaction method assignment |
093 | No entry exists in the DB for analysis method assignment |
094 | Error occurred updating segment data in ALCONSEG |
095 | Internal error. Unable to determine any methods |
096 | Unable to determine the methods effectively used for & |
097 | MTE entries missing - cannot start analysis method |
098 | Failed to determine method information |
099 | &1: method &2 is not released |
100 | & & |
101 | Method start failed. Reason: & |
102 | Cannot determine performance history data |
103 | &: No analysis method assigned |
104 | No method assignment for & is stored in the DB. Stored when you save. |
105 | You must specify a method |
106 | No method dispatcher specified. Setting default dispatcher |
107 | No data exists in the DB for MTE class & |
108 | You must specify the name of an MTE class |
109 | Context & already exists, it cannot be created |
110 | Error occurred during DB update of context/segment tables |
111 | Context & saved |
112 | You must specify the context name and system ID |
113 | Message & does not exist |
114 | The values for class & in system & have changed |
115 | The values for attribute group & in system & will be changed |
116 | Unable to determine the name of MTE class from & |
117 | MTE class from & not maintained. Assignment not possible. |
118 | You must specify an attribute group |
119 | You must specify the name of a properties variant |
120 | Changes affect all MTEs. Use the methods belonging to this MTE class. |
121 | Detailed data could not be updated |
122 | You do not have authorization to maintain release of methods |
123 | No monitoring program specified |
124 | No callback routine specified (Enter name) |
125 | No callback routine specified (Enter name) |
126 | No monitor set was specified |
127 | Monitor set & does not exist |
128 | Conversion of date entries failed |
129 | Monitor set & was saved |
130 | Error when saving monitor set & |
131 | Cannot be saved; no active monitor set exists |
132 | Monitor set & already exists |
133 | Monitor set & cannot be read |
134 | Specify name for monitor set |
135 | Monitor set & already exists |
136 | No monitor sets exist |
137 | Select monitor (set) |
138 | Basic monitors cannot be changed |
139 | Position cursor on a monitor |
140 | There are no selected nodes (MTE) |
141 | Deletion of monitor set & failed |
142 | Monitor set & was deleted |
143 | Automatic refresh deactivated due to problems with timer control |
144 | Monitor & was deleted |
145 | Automatic refresh of graphic display was stopped due to errors |
146 | Old DB format version |
147 | & does not exist as an attribute group for log attributes |
148 | Method is still assigned to MTEs and/or classes. Deletion not possible. |
149 | Node selections (MTE) cannot be determined |
150 | Enter name for MTE class |
151 | No class information found in the tree |
152 | Class name & is invalid |
153 | List with class names cannot be displayed |
154 | Node (MTE) specifications for class list missing |
155 | First select a class |
156 | Specify at least one class |
157 | No entry was selected |
158 | MTE specifications missing - cannot start data collection method |
159 | &: No data collection method assigned |
160 | Starting data collection method ... |
161 | MTE specifications missing - cannot start auto-reaction method |
162 | &: No method assigned |
163 | Starting auto-reaction method ... |
164 | Starting analysis method ... |
165 | Invalid method type |
166 | Data was saved for all contexts of the segment. |
167 | First select a method |
168 | Select one method only |
169 | Cannot display method list |
170 | No monitors exist |
171 | Error in Help processor |
172 | Entries to copy monitor are not complete |
173 | Monitor &1 does not exist in monitor set &2 |
174 | Data for the source monitor set could not be determined |
175 | Unable to determine data for the target monitor set |
176 | The copy required could not be executed |
177 | Monitor & copied |
178 | You cannot copy basic monitors |
179 | Entries to copy the monitor set are not complete |
180 | Monitor set & copied |
181 | Table of contents of the monitor set cannot be structured |
182 | First select a monitor set or monitor |
183 | The method definition for executing in the C kernel cannot be changed |
184 | Definition and release for method & saved |
185 | Scroll information for the list cannot be determined |
186 | Method & already exists. You cannot create it again |
187 | Method & does not exist |
188 | The refresh interval of & seconds is too short ( < 120 seconds ) |
189 | No measurements exist; choose a sample first |
190 | Sample context & does not exist |
191 | Measurements for & are invalid |
192 | Measurements for sample context & missing |
193 | Sample context & contains too many (more than 10) MTE samples |
194 | Unkown error occurred when displaying measurements |
195 | MTE entries missing - MTE data could not be determined |
196 | No data could be determined for & in system & |
197 | Column configuration for the current list cannot be determined |
198 | Values for MTE class/group will be changed |
199 | No data exists in the DB for & |
200 | Properties saved |
201 | There are no more measurements |
202 | MTE entries missing - description cannot be displayed |
203 | & does not exist as an attribute group for performance attributes |
204 | Invlaid selection mode - selection cannot be executed |
205 | Unit & from attribute group & is not suitable for MTE unit & |
206 | Table locked. Data currently being processed by user & |
207 | MTE description cannot be displayed |
208 | Function module & does not exist |
209 | Transaction & does not exist |
210 | Entries in table ALCONSEG deleted acc. to the selection conditions |
211 | NONE of the entries corresponding to the selection could be deleted |
212 | Unable to display node (internal error) |
213 | Failed to edit node (internal error) |
214 | Invalid parent node data found (internal error) |
215 | Failed to generate node (internal error) |
216 | The work mode of the node is invalid (internal error) |
217 | No further nodes can be appended |
218 | No MTE node for performance history data specified |
219 | Failed to determine rule data (key=&) (internal error) |
220 | You must specify an RFC destination |
221 | No segment data could be determined from destination & |
222 | Contexts for segment & were entered in ALCONSEG |
223 | Name of rule missing (Enter rule name) |
224 | Rule description does not exist in the logon language |
225 | Rule description & does not exist |
226 | First specify the name of the virtual summary node |
227 | Cannot determine system time zone |
228 | Could not display note for parameter check |
229 | Rule description & already exists |
230 | Cannot display alert description - internal error |
231 | Only one alert description can be displayed; restrict your selection |
232 | No server list could be determined from system & |
233 | Maintain rule parameters first |
234 | Select node type 'Rule nodes' first |
235 | The rule parameter contains obsolete parameters |
236 | Unable to determine information on parameter inheritance |
237 | Error at connection set-up: &1&2 |
238 | Specify node name first |
239 | Invalid work mode for rule callback: &1 |
240 | Parameter &1 was not evaluated by rule callback |
241 | Parameter &1 was not passed to rule callback |
242 | SAP system specification &1 is invalid |
243 | Callback routine &1 does not exist in program &2 |
244 | Value for rule parameter &1 missing. Specify a value |
245 | Invalid work mode for the editor of a monitor definition |
246 | Failed to display the monitor definition in the tree hierarchy |
247 | No monitor definition exists |
248 | Position the cursor on the top node first |
249 | Failed to search for rule & in the tree |
250 | Rule & already exists in the elevated node |
251 | Failed to determine node data |
252 | Position cursor on a node first |
253 | Failed to delete the node or the subtree |
254 | You cannot delete the top node |
255 | Include at least one node in the monitor definition first |
256 | Failed to generate the monitor |
257 | Monitor & already exists - new name required |
258 | Failed to generate a result node in rule call back & |
259 | The top node of the monitor definition is invalid (not virtual type) |
260 | You must specify a system ID |
261 | Unable to determine MTE data for class &1 of system &2 |
262 | No monitor template exists |
263 | Invalid top node of the monitor template (not virtual type) |
264 | The monitor definition was saved |
265 | Failed to search for node & in the tree |
266 | Filter does not contain T100 messages only. It cannot be changed |
267 | Filter does not contain system log messages only. It cannot be changed |
268 | Nodes with errors cannot be passed to the new monitor |
269 | The status attribute settings are already assigned specific to the MTE |
270 | The log attribute settings are already assigned specific to the MTE |
271 | Interval < &1 sec. not permitted. Specify a value >= &1 sec. |
272 | Failed to initialize the editor for the monitor definition |
273 | Failed to determine MTE information for system & |
274 | Unable to change node (presentation only) |
275 | Node does not have any attributes (presentation only) |
276 | Unable to delete node (presentation only) |
277 | Operation failed. Internal error |
278 | You can only remove nodes from the monitor by deleting the selection |
279 | & is the local system ID. Entry not possible |
280 | Connection test to & was performed successfully |
281 | Unable to create entry. Entry already exists for system & |
282 | Entries for individual servers already exist in system & |
283 | An entry already exists for system & |
284 | A reset to "WARMUP" status restarts the start-up methods |
285 | Method description is not available in the logon language |
286 | Method & was entered in task & |
287 | Caution: The executed call & must be in the target system |
288 | Background processing of methods not possible in dialog mode |
289 | Data currently being processed by user & . You cannot change it. |
290 | First select the MTE nodes |
291 | You can only display a maximum of 4 log attributes. Limit the selection. |
292 | First select log attribute |
293 | Interval data is incomplete. Fill all fields |
294 | Invalid interval data: From date / time > To date / time |
295 | No value <= 0 allowed. Specify value > 0 |
296 | Method &1 is not released as &2 |
297 | Could not determine dynpro values |
298 | Possible entries help does not exist for parameter & |
299 | The user is not assigned to a time zone |
300 | You cannot copy data to variant & |
301 | Data for variant "SAP DEFAULT" cannot be deleted |
302 | Failed to determine the system type (SAP / customer) |
303 | SAP monitor sets cannot be modified |
304 | Monitor set &1 entered in task &2 |
305 | First position the cursor on a monitor set |
306 | & is the currently active version and cannot be deleted |
307 | This also deletes all properties assigned to the variant |
308 | Nodes cannot be changed (choose "Monitor definition" -> "Change name") |
309 | The specified segment with the specified system does not make sense |
310 | No segment information found for system & |
311 | Unable to determine segment information for system & |
312 | Invalid segment name & |
313 | Segment spec. '<CURRENT>' only useful with SAP system spec. '<CURRENT>' |
314 | Context &1 is not in segment &2 |
315 | Internal error when determining the value set |
316 | The context specified does not make sense |
317 | Context & not found in any segment |
318 | Context & cannot be processed or displayed |
319 | Properties variant & created |
320 | Variant cannot be created as & is a reserved name |
321 | The values for "SAP DEFAULT" variants cannot be changed |
322 | To copy, specify "from" which variant name "to" which variant name |
323 | Copy was canceled |
324 | Data from variant & was copied to variant & |
325 | MTE entries are missing - no values can be reported |
326 | No value can be reported for this MTE |
327 | No values reported |
328 | Values can only be reported in one MTE. Therefore choose only one MTE. |
329 | Values are incomplete |
330 | This function is only allowed in SAP systems |
331 | Enter a date range for your selected aggregrate option |
332 | Enter a period that ends in the future |
333 | Specify your aggregate request properly |
334 | Alert ID (AID) not defined (function '&1') |
335 | Alert ID (AID) invalid (function '&1') |
336 | Error when calling the underlying C function (function '&1') |
337 | Communication problems (function '&1') |
338 | Internal problem (function '&1') |
339 | MTE ID (TID) not defined (function '&1') |
340 | MTE ID (TID) invalid (function '&1') |
341 | No additional information available (function &1) |
342 | Invalid C function call (function '&1') |
343 | Required segment not available (function '&1') |
344 | Name of MTE could not be expanded (function '&1') |
345 | MTE name not found (function '&1') |
346 | Problems accessing database (function '&1') |
347 | Invalid time interval defined (function '&1') |
348 | Missing function parameter (function '&1' - parameter '&2') |
349 | Source and target variant names must be different |
350 | No monitor sets defined (function '&1') |
351 | Monitor set name not defined (function '&1') |
352 | '&2' is not a valid monitor set name (function '&1') |
353 | Monitor set '&2' is empty (function '&1') |
354 | Properties of monitor set '&2' cannot be determined |
355 | Monitor name not defined (function '&1') |
356 | Monitor name '&2' invalid (function '&1') |
357 | Database unable to read monitor set &2 (function &1) |
358 | RFC destination for MTE & cannot be determined |
359 | Values can only be reported in local MTEs |
360 | Alert data missing (function '&1') |
361 | Monitor template not defined (function '&1') |
362 | Monitor tree could not be determined (function '&1') |
363 | Entries from variant & entered in transport request & |
364 | & does not support auto-reaction method |
365 | Only CCMS administrators can reset runtime status |
366 | Method runtime status could not be reset for some MTEs |
367 | Runtime status reset |
368 | MTE entry missing (first select or place cursor on MTE) |
369 | Only terminated methods can be reset (restrict selection) |
370 | Runtime status and alerts reset |
371 | Reset only possible for data collection and auto-reaction methods |
372 | Alert status reset failed |
373 | Methods to be executed manually cannot be automat. executed at start-up |
374 | History data could not be determined |
375 | Values for "SAP DEFAULT" variants cannot be transported |
376 | The "SAP DEFAULT" variant cannot be deleted |
377 | Request for history data not defined (function '&1') |
378 | Invalid type of history data requested (function '&1') |
379 | Invalid time interval for history data defined (function '&1') |
380 | Time interval not defined (function '&1') |
381 | Error accessing another SAP system (function '&1') |
382 | Only manual execution of transactions allowed |
383 | You are not authorized for transaction & |
384 | Error initializing graphic display (internal error) |
385 | Graphical object could not be destroyed |
386 | Creation of SAP-default variant on & is incomplete |
387 | New SAP DEFAULT variant cannot be created at this time |
388 | Monitor set cannot be edited (internal error) |
389 | Data transport in and out of table control failed |
390 | Monitor set &1 can only be changed by user &2 |
391 | Monitor set &1 can only be changed by user &2 or an administrator |
392 | To copy, specify "from" which method name "to" which method name |
393 | Cannot copy to &, method already exists |
394 | Cannot copy from &, method does not exist |
395 | Modifiability set to "Only modifiable by SAP" |
396 | The selected method is not assigned to any MTEs or classes |
397 | You do not have authorization to create monitors or monitor sets here |
398 | Could not get list of application servers (function &1) |
399 | Entries already exist for variant &1 of class &2 |
400 | Enter keepmths=0,keepqtrs=0 and keepyrs=0 when keepdays lessthan/equal 31 |
401 | Enter keepqtrs = 0 and keepyrs = 0 when keepmths < 4 |
402 | Enter keepyrs = 0 when keepqtrs < 5 |
403 | Cannot determine own RFC destinations |
404 | System ID not specified (function &1) |
405 | Context name not specified (function &1) |
406 | Variant &2 not defined (function &1) |
407 | User &2 is not owner of variant &3 (function &1) |
408 | System &3 cannot customize System &2 (function &1) |
409 | No data available for MTE class of the MTE (function &1) |
410 | TID-specific data MTE does not exist (function &1) |
411 | Do not change active variant |
412 | Data for variant & saved |
413 | No MTE name parts specified. Select at least one. |
414 | Could not activate background method dispatcher |
415 | No activation required - no background methods exist |
416 | Background dispatching is active; job: &1, user: &2, client: &3 |
417 | Cannot display job list - internal error |
418 | Choose a job and then release the job |
419 | Choose a job and specify a start period |
420 | Job &1 created by user &2 in client &3 |
421 | Checking jobs for background dispatcher |
422 | Could not create variant &2 (function &1) |
423 | The specified parent variant does not exist |
424 | Cannot execute method on RFC destination & (see Help) |
425 | Rule description data cannot be displayed (internal error) |
426 | Short description missing; Enter a description |
427 | Documentation module not specified; Enter a name of a module |
428 | Document module &1 does not exist in logon language &2 |
429 | Default node name for result node of rule missing; Enter name |
430 | Could not determine value set |
431 | Parameter name missing; Enter a paramater name |
432 | Parameter type & is invalid; Enter a valid type |
433 | Parameter type missing; Enter a parameter type |
434 | Parameter data type missing; Enter a parameter data type |
435 | Parameter data type & is invalid; Enter a valid data type |
436 | Parameter documentation missing; Enter documentation module |
437 | Documentation module & not found; Enter a valid module name |
438 | Rule description & saved |
439 | Error saving rule description & |
440 | First choose a rule description |
441 | "Ready for input" status of parameter data cannot be switched |
442 | Unable to delete rule description & |
443 | Rule description & deleted |
444 | Rule descriptions deleted |
445 | Rule description &2 is currently being edited by user &1 |
446 | Rule description & cannot be locked |
447 | Rule description &1 entered in request &2 |
448 | Rule descriptions entered in request & |
449 | Only one rule can be edited; Restrict selection |
450 | Event dispatching of ALV grid control failed |
451 | You are not authorized to start methods in system & |
452 | A URL can only be manually executed |
453 | Cannot determine RFC destination for MTE & |
454 | Cannot determine method data for MTE & |
455 | Cannot determine data for method & |
456 | The schema was sucessfully saved |
457 | Monitor specification missing; database cannot read monitor |
458 | Determining selected MTE failed |
459 | Unable to print graphic |
460 | Input behavior missing (Specify behavior) |
461 | Input behavior is invalid (Enter valid behavior) |
462 | Unable to create result parameter container |
463 | Rule parameter &1 not created from rule |
464 | Key of monitor definition node is invalid |
465 | Type of monitor definition node (&1) is unknown |
466 | << Error information cannot be formatted >> |
467 | << Cannot create result nodes >> |
468 | Name of an SAP System |
469 | Virtual summary node |
470 | &1: System is not configured |
471 | &1: System is not available |
472 | Cannot determine whether SAP system &1 is available |
473 | &1: There are currently no MTEs for class &2 |
474 | &1: MTE class &2 |
475 | &1: Context &2 |
476 | Segment of the CCMS monitoring architecture |
477 | Cannot determine segment information for local server |
478 | Could not determine documentation |
479 | Cannot add rule: Parameter & is not specified |
480 | Required parameter &1 is not specified |
481 | Entry for monitoring system &1 saved |
482 | Entry for system & already exists |
483 | Local system & cannot be specified as remote system |
484 | Could not enter system & in ALSYSTEMS |
485 | Internal error in syntax check of monitor definition |
486 | No syntax errors found |
487 | Monitor currently being edited by user & |
488 | Error in SAP lock management |
489 | Error saving monitor definition |
490 | Check of parameter &1: Cannot determine R/3 System groups |
491 | Could not determine data for MTE &1 |
492 | Specify missing data for node name creation |
493 | Cannot display parameter values (internal error) |
494 | Client & is unknown in local SAP system |
495 | No authorization for function &1 |
496 | MTE entries missing - Cannot log on to SAP system |
497 | Cannot display list of SAP system names |
498 | First choose an SAP system |
499 | Only select one SAP system |
500 | Unable to determine information about the selected SAP system |
501 | MTE entries missing - Unable to check SAP systems |
502 | Failed to log on to SAP system & |
503 | Type of MTE & is unknown; Cannot log on to SAP system |
504 | Unable to add MTEs to CCMS alert monitor |
505 | Context &1: No RFC destination for execution of analysis method |
506 | ABAP class &1: Constructor error occurred |
507 | Error occurred in toolbar event handler |
508 | Unable to execute function (internal error) |
509 | Unable to execute function (internal error) |
510 | Could not complete some alerts (internal error) |
511 | Cannot initialize monitor environment (internal error) |
512 | System group &1: Cannot determine systems in group |
513 | &1: There are currently no MTEs for class &2 in client &3 |
514 | Time monitoring for node selection deactivated (internal error) |
515 | Cannot add system & to system repository |
516 | The monitor viewer cannot be displayed (internal error) |
517 | The alert viewer cannot be displayed (internal error) |
518 | &: Event processing failed (internal error) |
519 | &: Asynchronously determined data is not processable |
520 | Component cannot be displayed (internal error) |
521 | Cannot display table of contents (internal error) |
522 | Only complete monitor sets can be transported |
523 | Invalid node type was requested for monitor definition node |
524 | Missing parameter specification |
525 | Invalid literal entry |
526 | Parameter & is not known |
527 | Conversion cannot be triggered (internal error) |
528 | System was unable to start the monitoring framework (internal error) |
529 | Conversion log cannot be displayed (internal error) |
530 | Event dispatching for GUI controls failed (internal error) |
531 | Select at least one performance MTE first |
532 | Only the first interval entry is currently respected |
533 | Central system tool dispatching is active; job: &1, user: &2, client: &3 |
534 | Activation of central system tool dispatching failed |
535 | Monitor definition was saved to file |
536 | File contains XML document with errors |
537 | File does not contain any monitor definitions |
538 | Loading the monitor definition from file failed |
539 | The monitor definition was read from file |
540 | The monitor definition was not imported |
541 | Syntax check failed (internal error) |
542 | Central system execution only possible for reports and function modules |
543 | Can only execute in central system if execution location is "any server" |
544 | Central system execution cannot be performed at "Startup" |
545 | Release at central system execution only possible as auto-reaction method |
546 | System group & is unknown |
547 | No systems are configured for system group & |
548 | RFC connection check for system group & failed |
549 | Select a sample first (30 minutes / 24 hours) |
550 | GET_CLASS_UNDER_CLASS cannot be included directly |
551 | System group & contains unconfigured SAP systems |
552 | Threshold value Green -> Yellow must not be higher than Yellow -> Red |
553 | Threshold value Yellow -> Green must not be higher than Green -> Yellow |
554 | Threshold value Red -> Yellow must not be higher than Yellow -> Red |
555 | Threshold value Green -> Yellow must not be lower than Yellow -> Red |
556 | Threshold value Yellow -> Green must not be lower than Green -> Yellow |
557 | Threshold value Red -> Yellow must not be lower than Yellow -> Red |
558 | Determining data |
559 | Changes have been saved |
560 | Cannot access contexts |
561 | Cannot access system |
562 | Connection test cannot be performed with empty RFC destination |
563 | CCMSPING communication error: Host &1 unknown |
564 | CCMSPING communication error: Service &1 unknown |
565 | CCMSPING communication error: Cannot access message server |
566 | CCMSPING &2 not accessible &1 |
567 | CCMSPING system error &1 |
568 | CCMSPING: internal error; check agent installation |
569 | &1 &2 unchanged, as defined in CCMS agent or central system |
570 | Cannot perform remote login with empty analysis destination |
571 | Operation cannot be performed - status is invalid |
572 | Node (MTE) activated |
573 | Node (MTE) deactivated |
574 | &1 entries deleted from routing cache |
575 | Tree control problem; restart transaction |
576 | Complete system connection specifications before saving |
577 | Inconsistent monitoring options for system and application servers |
578 | Select a system before you delete it |
579 | CCMSPING test successfully performed for system &1 |
580 | Always select a system that is already entered from the system lists |
581 | Error while loading the system list |
582 | No file selected |
583 | Complete system connection specifications before testing |
584 | No data available as no remote system is entered |
585 | The * variant (customer default) is activated instead of variant &1 |
586 | Choose a system before entering a monitoring pause |
587 | Values applied to the active variant &1 |
588 | Agent is not accessible |
589 | Specify XML file name first |
590 | Initialization of XML download environment failed |
591 | Error occurred when converting to XML |
592 | XML document cannot be saved in specified file |
593 | Empty input table (function "&1") |
594 | Invalid MTE in input table (function "&1") |
595 | Cannot determine MTE data (function "&1") |
596 | No alerts exist (function "&1") |
597 | First select as least one method assignment |
598 | &1 method assignment(s) deleted |
599 | First select exactly one method |
600 | Enter a name for the central autoreaction |
601 | Cannot get MTE classes from 4.0B system & |
602 | No routing information available for system & |
603 | Error saving method assignment for system & |
604 | Cannot activate variant &1 |
605 | Error occurred during definition of RFC system information |
606 | Error occurred during loading of directory information |
607 | Error occurred during loading of file information |
608 | Error occurred during loading of information on logical directory |
609 | Could not change collection and reorganization schema |
610 | Note: Changes to the assignments are not immediately visible |
611 | An error occurred when assigning collect/reorg schema to MTE class |
612 | System connection specifications incomplete; complete |
613 | Internal error; report to SAP |
614 | You are not authorized to change collection/reorganization schemas |
615 | Select exactly one collection/reorganization schema for the assignment |
616 | First select at least one schema assignment |
617 | Node (MTE) data for assigning attribute group is missing. |
618 | Internal error: attribute group cannot be assigned |
619 | The jobs for background dispatching have been deleted |
620 | There are no jobs active/released for background dispatching |
621 | The jobs for central system tool dispatching have been deleted |
622 | No jobs active/released for central system tool dispatching |
623 | First select an attribute group |
624 | Attribute group cannot be set for MTE & |
625 | Attribute group & does not match the selected MTE |
626 | Attribute group & does not exist for the selected MTE |
627 | Destination & already used for another system entry |
628 | End time or end date of the interval is in the past |
629 | Backup of properties terminated |
630 | Properties maint. for &1 is only possible in the primary central sys. &2 |
631 | Context "&1" is not a system-wide context; function cannot be executed |
632 | Connection setup: &1&2 |
633 | Invalid logon or invalid user |
634 | Context "&1" was fixed to segment "&2" |
635 | Fixing reset for context "&1" |
636 | Context "&1" is not fixed; fixing "out" not possible |
637 | Cannot determine agent destination, or destination is empty |
638 | Agent &1 is not registered with multiple systems |
639 | Agent &1 is only registered with the current system &2 |
640 | Agent &1 was registered with &2 as the primary central system |
641 | Agnent &1 is registered with the following systems: &2 |
642 | Agent &1 - error when setting up connection: &2&3 |
643 | End date is before start date |
644 | End time is before start time |
645 | Specification of the system number is required |
646 | You are not authorized to maintain RFC destinations |
647 | Internal error during RFC function & |
648 | Destination & was successfully created |
649 | Client and/or password missing for analysis destination |
650 | Connection test to destination &1 terminated with ERRORS |
651 | Error during remote call of &1 function: &2&3 |
652 | Destination &1 already exists |
653 | Properties maintenance not possible for &1 |
654 | Connection test to &1 started |
655 | &1 is not an ABAP connection; cannot perform connection test |
656 | Analysis method &1 can only be performed for object nodes |
657 | File &1 not found |
658 | TIMEOUT when reading file &1 |
659 | You are not authorized to read file &1 |
660 | No Customizing destination for J2EE segment |
661 | Error in J2EE function: &1 |
662 | &1 is not a J2EE segment, Customizing destination cannot be changed |
663 | RFC destination &1 does not exist; entry for &2 is not changed |
664 | Assignment for local system only works with nodes from agent segments |
665 | Error when creating a connection to &3: &1&2 |
666 | Change applied |
667 | Error on the database; could not apply change |
668 | Could not make change; table is locked by user &1 |
669 | Enter a valid value |
670 | Threshold value for YELLOW->GREEN cannot be higher than for RED->YELLOW |
671 | Threshold value for RED->YELLOW cannot be lower than for YELLOW->GREEN |
672 | CCMS agent sapstartsrv is not completely configured |
673 | CCMS agent sapstartsrv is not configured for central system &1 |
674 | Registration of the CCMS agent is inconsistent; repeat registration |
675 | Selected monitor does not contain a rule with the parameter R3System |
676 | You are not authorized to change threshold values. |
678 | Job &1 has been generated but not released, release in transaction SM37 |
680 | Error when creating path/file at front end |
681 | Process terminated by user |
682 | Error/termination when creating file &1 |
683 | &2 MTE classes were collected by system &1 |
700 | An error occurred when assigning collect/reorg schema to MTE class |
701 | There is already a CPH assignment for at least one MTE class |
702 | &1 objects were successfully assigned collect/reorg schema &2 |
703 | & |
730 | Failed to create WS proxy; RC = &1, message = &2&3&4 |
731 | WS proxy ports for local system all recreated. [&1 OK] [&2 errors] |
732 | Could not create WS proxy ports for local system [&1] |
733 | WS proxy ports for local system checked/created [&1 OK] [&2 errors] |
734 | You are not authorized to create WS proxy ports |
771 | Enter a valid value |
888 | Sorry ! Function under construction !! |
889 | Function not available |