SAP ABAP Message Class VSCAN (Virus Scan Interface)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-SEC-VIR (Application Component) Anti-Virus Protection
⤷ SVSCAN (Package) Virus Scan of SAP Objects
⤷ BC-SEC-VIR (Application Component) Anti-Virus Protection
⤷ SVSCAN (Package) Virus Scan of SAP Objects
Attributes
Message class | VSCAN | |
Short Description | Virus Scan Interface | |
Changed On | 20130531 | |
Last Changed At | 091844 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | Status of virus scan server (start/stop by application server) | Space: object requires documentation | |
2 | 001 | Virus scan provider utilization | Space: object requires documentation | |
3 | 002 | Virus scan servers monitored by this application server | Space: object requires documentation | |
4 | 003 | Virus scan servers | Space: object requires documentation | |
5 | 004 | Virus scan servers | Space: object requires documentation | |
6 | 005 | Virus scan server &1 is active | Space: object requires documentation | |
7 | 006 | Virus scan server &1 is not active (application server) | Space: object requires documentation | |
8 | 007 | Virus scan server &1 is not active (started externally) | Space: object requires documentation | |
9 | 008 | Virus scan server &1 is still active | Space: object requires documentation | |
10 | 009 | Virus scan server &1 is not active (default setting) | Space: object requires documentation | |
11 | 010 | Virus scan server workload exceeds threshold value (&1 &3 > &2 &3) | Space: object requires documentation | |
12 | 011 | You are not authorized to administer virus scan server &2 | Space: object requires documentation | |
13 | 012 | Virus scan server &1 is not configured | Space: object requires documentation | |
14 | 013 | Virus scan provider &1 is not local to application server &2 | Space: object requires documentation | |
15 | 014 | RFC destination &1 does not exist | Space: object requires documentation | |
16 | 015 | RFC destination &1 is of type &2 instead of "T" | Space: object requires documentation | |
17 | 016 | RFC destination &1 is incorrectly configured | Space: object requires documentation | |
18 | 017 | Name and program ID of RFC destination &1 must be identical | Space: object requires documentation | |
19 | 018 | Virus scan server &1 is already active | Space: object requires documentation | |
20 | 019 | Error when communicating with RFC destination &1: &2&3&4 | Space: object requires documentation | |
21 | 020 | Could not stop virus scan server &1 | Space: object requires documentation | |
22 | 021 | Could not start virus scan server &1 | Space: object requires documentation | |
23 | 022 | Error creating monitor structure for virus scan providers (&1 &2 &3 &4) | Space: object requires documentation | |
24 | 023 | Virus scan server log attribute | Space: object requires documentation | |
25 | 024 | Virus scan server &1 started by user &2 | The short text describes the object sufficiently | |
26 | 025 | Virus scan server &1 was stopped by user &2 | Space: object requires documentation | |
27 | 027 | Error when connecting to the following remote systems: &1 | Space: object requires documentation | |
28 | 028 | Save the changed data before executing this function | The short text describes the object sufficiently | |
29 | 029 | Virus scan server &1 initialized by user &2 | Space: object requires documentation | |
30 | 030 | Configuration parameter &1 does not exist | Space: object requires documentation | |
31 | 031 | Value &2 not permitted for configuration parameter &1 (type &3) | Space: object requires documentation | |
32 | 032 | Virus scan profile &1 does not exist | Space: object requires documentation | |
33 | 033 | Virus scan profile &1 is not active | Space: object requires documentation | |
34 | 034 | No virus scan profile is selected as the "default profile" | Space: object requires documentation | |
35 | 035 | Multiple virus scan profiles are selected as the "default profile" | Space: object requires documentation | |
36 | 036 | Recursive occurrence of virus scan profile &1 in the sequence &2&3&4 | Space: object requires documentation | |
37 | 037 | Scanner group &1 does not exist | Space: object requires documentation | |
38 | 038 | Virus scan server &1 triggered exception &3 in function &2 | Space: object requires documentation | |
39 | 039 | Virus scan server &1 updated the local configuration file | Space: object requires documentation | |
40 | 040 | Incorrect parameters for virus scan server &1 | Space: object requires documentation | |
41 | 041 | Could not start the scan engine of virus scan server &1 | Space: object requires documentation | |
42 | 042 | Writing of local configuration parameters failed | Space: object requires documentation | |
43 | 043 | Command line for virus scan server &1 longer than &2 characters | Space: object requires documentation | |
44 | 044 | Virus scan server &1 was not started due to configuration errors | Space: object requires documentation | |
45 | 045 | Configuration parameter &1 from scanner group &2 is not supported | Space: object requires documentation | |
46 | 046 | Configuration parameter &1 is not permitted in this context | Space: object requires documentation | |
47 | 047 | Virus scan server &1 uses BAdI-implemented scanner group &2 | Space: object requires documentation | |
48 | 048 | Configuration parameter &1 from profile &2 (step &3) is not supported | Space: object requires documentation | |
49 | 049 | Virus scan server &1 is temporarily not available | Space: object requires documentation | |
50 | 050 | Internal error in virus scan server &1 | Space: object requires documentation | |
51 | 051 | No virus scan provider available for scanner group &1 | Space: object requires documentation | |
52 | 052 | Virus scan profile &1 does not contain any steps | Space: object requires documentation | |
53 | 053 | No BAdI implementation found for scanner group &1 | Space: object requires documentation | |
54 | 054 | Profile name &1 violates namespace convention for SAP virus scan profiles | Space: object requires documentation | |
55 | 055 | Scan error "&1&2" for object "&3&4" | Space: object requires documentation | |
56 | 056 | Virus "&1&2" found in object "&3&4" | Space: object requires documentation | |
57 | 057 | You are not authorized to test the virus scan interface | Space: object requires documentation | |
58 | 058 | Enter file name | Space: object requires documentation | |
59 | 059 | Stop request is still being processed | Space: object requires documentation | |
60 | 060 | Virus scan server &1 is already initialized | Space: object requires documentation | |
61 | 061 | Initialization still being processed | Space: object requires documentation | |
62 | 062 | Fill either IF_SERVER_NAME or IF_SCANNER_GROUP | The short text describes the object sufficiently | |
63 | 063 | User &1 is not authorized to administer scan instances | The short text describes the object sufficiently | |
64 | 064 | Status of the virus scan server (self-starter) | Space: object requires documentation | |
65 | 065 | The trace output contains at least one error (highlighted red) | The short text describes the object sufficiently | |
66 | 066 | This program requires the authorization object S_RZL_ADM | Space: object requires documentation | |
67 | 067 | Profile violates guidelines for profiles delivered by SAP | Space: object requires documentation | |
68 | 068 | Cannot transport package &1 from this system | Space: object requires documentation | |
69 | 069 | Table type &1 is not supported (only STANDARD and SORTED) | The short text describes the object sufficiently | |
70 | 070 | Table column &1 has the unsupported row type &2 | The short text describes the object sufficiently | |
71 | 071 | Row type of the table contains more than one field | The short text describes the object sufficiently | |
72 | 072 | Virus scan adapter &1 is not configured | The short text describes the object sufficiently | |
73 | 073 | No virus scan adapter available for scanner group &1 | The short text describes the object sufficiently | |
74 | 074 | The type of the new provider must be ADAPTER or SERVER | Space: object requires documentation | |
75 | 075 | The name of the virus scan adapter must begin with the prefix VSA_ | Space: object requires documentation | |
76 | 076 | Virus scan provider &1 is not configured | The short text describes the object sufficiently | |
77 | 077 | Could not start virus scan adapter &1 | Space: object requires documentation | |
78 | 078 | Instance name &1 cannot be used | Space: object requires documentation | |
79 | 079 | Instance directory &1 is not valid | Space: object requires documentation | |
80 | 080 | Group &1 (kernel use): BAdI implementation not permitted | The short text describes the object sufficiently | |
81 | 081 | Group &1 (kernel use): No local virus scan adapter | The short text describes the object sufficiently | |
82 | 082 | &1 is not a permissible MIME type here | Space: object requires documentation | |
83 | 083 | Could not start the engine of &1. Error: "&2&3" | Space: object requires documentation | |
84 | 084 | Content in object "&3&4" blocked; rule violation "&1&2" | Space: object requires documentation | |
85 | 085 | Active content in object "&3&4" was blocked; rule violation "&1&2" | Space: object requires documentation | |
86 | 086 | Profile parameters exist, but evaluation has not been activated | Space: object requires documentation | |
87 | 087 | MIME types have been entered, but the MIME check has not been activated | Space: object requires documentation | |
88 | 088 | Blacklist indicator is only meaningful with an active MIME check | Space: object requires documentation | |
89 | 089 | Changes were not saved | The short text describes the object sufficiently | |
90 | 090 | Profile is active without steps | Space: object requires documentation | |
91 | 091 | Profile is active and uses an unsuitable reference profile | Space: object requires documentation | |
92 | 092 | Profile is active and has both reference profile and steps | Space: object requires documentation | |
93 | 093 | Step &1 uses an unsuitable profile | Space: object requires documentation | |
94 | 094 | Group &1 from step &2 does not have a functioning scanner | Space: object requires documentation | |
95 | 100 | Start the processing of virus scan profile &1 | Space: object requires documentation | |
96 | 101 | Virus scan profile &1, step &2: scanner group &3 | Space: object requires documentation | |
97 | 102 | Virus scan profile &1, step &2: virus scan server &3 | Space: object requires documentation | |
98 | 103 | Virus scan profile &1, step &2: virus scan profile &3 | Space: object requires documentation | |
99 | 104 | Virus scan profile &1, step &2: scan instance returns &3 (&4) | Space: object requires documentation | |
100 | 105 | Profile &1 successful, since step &2 successful (OR linkage) | The short text describes the object sufficiently | |
101 | 106 | Profile &1 failed, since step &2 failed (AND linkage) | The short text describes the object sufficiently | |
102 | 107 | Virus scan server &1 was selected from scanner group &2 | Space: object requires documentation | |
103 | 108 | Scanner group &1 is a BAdI implementation (scanner class: &2) | Space: object requires documentation | |
104 | 109 | Virus scan adapter &1 was selected from scanner group &2 | The short text describes the object sufficiently |
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in | 640 |