| VSCAN007 |
Virus scan server &1 is not active (started externally) |
| VSCAN008 |
Virus scan server &1 is still active |
| VSCAN009 |
Virus scan server &1 is not active (default setting) |
| VSCAN010 |
Virus scan server workload exceeds threshold value (&1 &3 > &2 &3) |
| VSCAN011 |
You are not authorized to administer virus scan server &2 |
| VSCAN012 |
Virus scan server &1 is not configured |
| VSCAN013 |
Virus scan provider &1 is not local to application server &2 |
| VSCAN014 |
RFC destination &1 does not exist |
| VSCAN015 |
RFC destination &1 is of type &2 instead of "T" |
| VSCAN016 |
RFC destination &1 is incorrectly configured |
| VSCAN017 |
Name and program ID of RFC destination &1 must be identical |
| VSCAN018 |
Virus scan server &1 is already active |
| VSCAN019 |
Error when communicating with RFC destination &1: &2&3&4 |
| VSCAN020 |
Could not stop virus scan server &1 |
| VSCAN021 |
Could not start virus scan server &1 |
| VSCAN022 |
Error creating monitor structure for virus scan providers (&1 &2 &3 &4) |
| VSCAN023 |
Virus scan server log attribute |
| VSCAN024 |
Virus scan server &1 started by user &2 |
| VSCAN025 |
Virus scan server &1 was stopped by user &2 |
| VSCAN027 |
Error when connecting to the following remote systems: &1 |
| VSCAN028 |
Save the changed data before executing this function |
| VSCAN029 |
Virus scan server &1 initialized by user &2 |
| VSCAN030 |
Configuration parameter &1 does not exist |
| VSCAN031 |
Value &2 not permitted for configuration parameter &1 (type &3) |
| VSCAN032 |
Virus scan profile &1 does not exist |
| VSCAN033 |
Virus scan profile &1 is not active |
| VSCAN034 |
No virus scan profile is selected as the "default profile" |
| VSCAN035 |
Multiple virus scan profiles are selected as the "default profile" |
| VSCAN036 |
Recursive occurrence of virus scan profile &1 in the sequence &2&3&4 |
| VSCAN037 |
Scanner group &1 does not exist |
| VSCAN038 |
Virus scan server &1 triggered exception &3 in function &2 |
| VSCAN039 |
Virus scan server &1 updated the local configuration file |
| VSCAN040 |
Incorrect parameters for virus scan server &1 |
| VSCAN041 |
Could not start the scan engine of virus scan server &1 |
| VSCAN042 |
Writing of local configuration parameters failed |
| VSCAN043 |
Command line for virus scan server &1 longer than &2 characters |
| VSCAN044 |
Virus scan server &1 was not started due to configuration errors |
| VSCAN045 |
Configuration parameter &1 from scanner group &2 is not supported |
| VSCAN046 |
Configuration parameter &1 is not permitted in this context |
| VSCAN047 |
Virus scan server &1 uses BAdI-implemented scanner group &2 |
| VSCAN048 |
Configuration parameter &1 from profile &2 (step &3) is not supported |
| VSCAN049 |
Virus scan server &1 is temporarily not available |
| VSCAN050 |
Internal error in virus scan server &1 |
| VSCAN051 |
No virus scan provider available for scanner group &1 |
| VSCAN052 |
Virus scan profile &1 does not contain any steps |
| VSCAN053 |
No BAdI implementation found for scanner group &1 |
| VSCAN054 |
Profile name &1 violates namespace convention for SAP virus scan profiles |
| VSCAN055 |
Scan error "&1&2" for object "&3&4" |
| VSCAN056 |
Virus "&1&2" found in object "&3&4" |
| VSCAN057 |
You are not authorized to test the virus scan interface |
| VSCAN058 |
Enter file name |
| VSCAN059 |
Stop request is still being processed |
| VSCAN060 |
Virus scan server &1 is already initialized |
| VSCAN061 |
Initialization still being processed |
| VSCAN062 |
Fill either IF_SERVER_NAME or IF_SCANNER_GROUP |
| VSCAN063 |
User &1 is not authorized to administer scan instances |
| VSCAN064 |
Status of the virus scan server (self-starter) |
| VSCAN065 |
The trace output contains at least one error (highlighted red) |
| VSCAN066 |
This program requires the authorization object S_RZL_ADM |
| VSCAN067 |
Profile violates guidelines for profiles delivered by SAP |
| VSCAN068 |
Cannot transport package &1 from this system |
| VSCAN069 |
Table type &1 is not supported (only STANDARD and SORTED) |
| VSCAN070 |
Table column &1 has the unsupported row type &2 |
| VSCAN071 |
Row type of the table contains more than one field |
| VSCAN072 |
Virus scan adapter &1 is not configured |
| VSCAN073 |
No virus scan adapter available for scanner group &1 |
| VSCAN074 |
The type of the new provider must be ADAPTER or SERVER |
| VSCAN075 |
The name of the virus scan adapter must begin with the prefix VSA_ |
| VSCAN076 |
Virus scan provider &1 is not configured |
| VSCAN077 |
Could not start virus scan adapter &1 |
| VSCAN078 |
Instance name &1 cannot be used |
| VSCAN079 |
Instance directory &1 is not valid |
| VSCAN100 |
Start the processing of virus scan profile &1 |
| VSCAN101 |
Virus scan profile &1, step &2: scanner group &3 |
| VSCAN102 |
Virus scan profile &1, step &2: virus scan server &3 |
| VSCAN103 |
Virus scan profile &1, step &2: virus scan profile &3 |
| VSCAN104 |
Virus scan profile &1, step &2: scan instance returns &3 (&4) |
| VSCAN105 |
Profile &1 successful, since step &2 successful (OR linkage) |
| VSCAN106 |
Profile &1 failed, since step &2 failed (AND linkage) |
| VSCAN107 |
Virus scan server &1 was selected from scanner group &2 |
| VSCAN108 |
Scanner group &1 is a BAdI implementation (scanner class: &2) |
| VSCAN109 |
Virus scan adapter &1 was selected from scanner group &2 |
| VSCE301 |
Knowledge base object &1 does not exist |
| VSCE310 |
Language key & not defined (check your entry) |
| VSCE345 |
Class &1 has no description in language &2 |
| VSCE355 |
KNNUM is assigned in CUOB but is missing in CUKB (network: &) |
| VSCE356 |
Action &1 to &2 not supported |
| VSCE357 |
Procedure &1 to &2 not supported |
| VSCE359 |
Variant table &1 does not exist on date &2 |
| VSCE360 |
Table &1 has no entry in row &2, column &3 |
| VSCE364 |
Characteristic &2 (or its values) has no description in &1 |
| VSCE368 |
Source text of relationship &1 is too long (>10,000 lines) |
| VSCE370 |
Invalid derivation for &1 characteristc &2 in procedure &3 |
| VSCE380 |
Check ended without errors |
| VSCE381 |
Check ended with warnings |
| VSCE382 |
Errors were found during the check |
| VSCE387 |
SCREEN_DEP not supported: dependency &1, characteristic &2, facette &3 |
| VSCE388 |
Error in SCREEN_DEP: dependency &1, characteristic &2, cause &3 |
| VSCE389 |
Characteristic &1: SCREEN_DEP-NO_INPUT supported as of IPC 3.0 |
| VSCE391 |
Object characteristic &1 is not supported in any IPC scenario |