SAP ABAP Message Class SRT_WSP (Messages for SRT WSP)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-ESI-WS-ABA-CFG (Application Component) WebServices ABAP Configuration
⤷
SOAP_CONFIG (Package) SOAP Configuration Framework
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-ESI-WS-ABA-CFG (Application Component) WebServices ABAP Configuration⤷
SOAP_CONFIG (Package) SOAP Configuration Framework 
Attributes
| Message class |  |
SRT_WSP |
| Short Description |  |
Messages for SRT WSP |
| Changed On |  |
20131127 |
| Last Changed At |  |
162503 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
& & & & | The short text describes the object sufficiently | |
| 2 | 001 |
Uninstantiated object "&1" in method &3 of class &2 | The short text describes the object sufficiently | |
| 3 | 002 |
Initial value "&1" in method &3 of class &2 | The short text describes the object sufficiently | |
| 4 | 003 |
Cannot execute method &2; object of class &1 terminated | The short text describes the object sufficiently | |
| 5 | 004 |
Error when deleting from database table &1 | The short text describes the object sufficiently | |
| 6 | 005 |
Configuration not yet saved | The short text describes the object sufficiently | |
| 7 | 006 |
Configuration is invalid: &1&2&3&4 | The short text describes the object sufficiently | |
| 8 | 007 |
Error when updating database table &1 | The short text describes the object sufficiently | |
| 9 | 008 |
No data for database table &1 | The short text describes the object sufficiently | |
| 10 | 009 |
Insertion error in database table &1 | The short text describes the object sufficiently | |
| 11 | 010 |
Invalid configuration type &1 in class &2, method &3 | The short text describes the object sufficiently | |
| 12 | 011 |
Invalid subject status '&1' | The short text describes the object sufficiently | |
| 13 | 012 |
Value cannot be modified | The short text describes the object sufficiently | |
| 14 | 013 |
Invalid value '&1' for property '&2:&3' | The short text describes the object sufficiently | |
| 15 | 014 |
Property '&1:&2' is unknown | The short text describes the object sufficiently | |
| 16 | 015 |
Property cannot be modified | The short text describes the object sufficiently | |
| 17 | 016 |
Invalid property status '&1' | The short text describes the object sufficiently | |
| 18 | 017 |
No metadata for feature '&1' | The short text describes the object sufficiently | |
| 19 | 018 |
Property list cannot be modified | The short text describes the object sufficiently | |
| 20 | 019 |
Property does not belong to this context | The short text describes the object sufficiently | |
| 21 | 020 |
Subject type '&2' is not in scope '&1' of property '&3:&4' | The short text describes the object sufficiently | |
| 22 | 021 |
Property already allocated | The short text describes the object sufficiently | |
| 23 | 022 |
Invalid property list status '&1' | The short text describes the object sufficiently | |
| 24 | 023 |
Error when creating property list | The short text describes the object sufficiently | |
| 25 | 024 |
Subject cannot be modified | The short text describes the object sufficiently | |
| 26 | 025 |
No corresponding parent subject node exists in the other context | The short text describes the object sufficiently | |
| 27 | 026 |
Specified subject does not have type "Operation" | The short text describes the object sufficiently | |
| 28 | 027 |
Specified subject does not have type "Service" | The short text describes the object sufficiently | |
| 29 | 028 |
Specified subject does not have type "Binding" | The short text describes the object sufficiently | |
| 30 | 029 |
Configuration cannot be modified | The short text describes the object sufficiently | |
| 31 | 030 |
Context cannot be modified | The short text describes the object sufficiently | |
| 32 | 031 |
Service '&1' already exists | The short text describes the object sufficiently | |
| 33 | 032 |
Operation '&1' already exists | The short text describes the object sufficiently | |
| 34 | 033 |
Binding '&1' already exists | The short text describes the object sufficiently | |
| 35 | 034 |
A service ('&1') already exists | The short text describes the object sufficiently | |
| 36 | 035 |
An interface ('&1') already exists | The short text describes the object sufficiently | |
| 37 | 036 |
SOAP application '&1' is unknown | The short text describes the object sufficiently | |
| 38 | 037 |
Type '&1' of XML string is not type of DT variant | The short text describes the object sufficiently | |
| 39 | 038 |
Invalid status '&1' for DT variant | The short text describes the object sufficiently | |
| 40 | 039 |
DT variant cannot be modified | The short text describes the object sufficiently | |
| 41 | 040 |
Structure name '&1' is unknown in ABAP Dictionary | The short text describes the object sufficiently | |
| 42 | 041 |
XSLT error: '&1'. | The short text describes the object sufficiently | |
| 43 | 042 |
Cannot create binding; no service exists | The short text describes the object sufficiently | |
| 44 | 043 |
Specified variant '&1' does not exist | The short text describes the object sufficiently | |
| 45 | 044 |
Variant '&1' is not part of development object '&2' | The short text describes the object sufficiently | |
| 46 | 045 |
Binding does not exist in configuration | The short text describes the object sufficiently | |
| 47 | 046 |
No variant assigned to binding '&1' | The short text describes the object sufficiently | |
| 48 | 047 |
Error when opening service definition: "&1" | The short text describes the object sufficiently | |
| 49 | 048 |
Error when opening client proxy: "&1" | The short text describes the object sufficiently | |
| 50 | 049 |
Configuration type "&1" is invalid | The short text describes the object sufficiently | |
| 51 | 050 |
Profile cannot be modified | The short text describes the object sufficiently | |
| 52 | 051 |
ICF: &1&2&3&4 | The short text describes the object sufficiently | |
| 53 | 052 |
HTTP: &1&2&3&4 | The short text describes the object sufficiently | |
| 54 | 053 |
Maximum one binding allowed for simple client providers | The short text describes the object sufficiently | |
| 55 | 054 |
Configuration type &1 is invalid | The short text describes the object sufficiently | |
| 56 | 055 |
Profile type &1 is invalid | The short text describes the object sufficiently | |
| 57 | 056 |
Profile has not yet been saved | The short text describes the object sufficiently | |
| 58 | 057 |
Profile is invalid | The short text describes the object sufficiently | |
| 59 | 058 |
Profile "&1" is not active | The short text describes the object sufficiently | |
| 60 | 059 |
Error when deleting service node | The short text describes the object sufficiently | |
| 61 | 060 |
Maximum of one service node permitted in configuration | The short text describes the object sufficiently | |
| 62 | 061 |
At least one service node required for configuration | The short text describes the object sufficiently | |
| 63 | 062 |
No variant assigned to binding &1 | The short text describes the object sufficiently | |
| 64 | 063 |
Specified subjects have different types | The short text describes the object sufficiently | |
| 65 | 064 |
Source object and target object are identical | The short text describes the object sufficiently | |
| 66 | 065 |
Error when reading service definition "&1": &2 | The short text describes the object sufficiently | |
| 67 | 066 |
Parameter &1 has an invalid value in the current context: &2 | The short text describes the object sufficiently | |
| 68 | 067 |
Binding &1 has an empty property list structure | The short text describes the object sufficiently | |
| 69 | 068 |
Error when deleting ICF entities: &1&2&3&4 | The short text describes the object sufficiently | |
| 70 | 069 |
Error when deleting HTTP entities: &1&2&3&4 | The short text describes the object sufficiently | |
| 71 | 070 |
Feature name "&1" is unknown | The short text describes the object sufficiently | |
| 72 | 071 |
Feature class "&1" not initialized | The short text describes the object sufficiently | |
| 73 | 072 |
Could not instantiate serialization class "&1" | The short text describes the object sufficiently | |
| 74 | 073 |
Error when creating SIDL interface for object '&1': '&2' | The short text describes the object sufficiently | |
| 75 | 074 |
Error when initializing Feature Factory | The short text describes the object sufficiently | |
| 76 | 075 |
No WSDL root element specified | The short text describes the object sufficiently | |
| 77 | 076 |
Only one WSDL root element permitted | The short text describes the object sufficiently | |
| 78 | 077 |
WSDL root element does not belong to this configuration | The short text describes the object sufficiently | |
| 79 | 078 |
Invalid subject type for WSDL root element | The short text describes the object sufficiently | |
| 80 | 079 |
No WSDL root element set | The short text describes the object sufficiently | |
| 81 | 080 |
"&1" cannot be used as a name for SOAP applications | The short text describes the object sufficiently | |
| 82 | 081 |
Status "&1" not valid for SOAP applications | The short text describes the object sufficiently | |
| 83 | 082 |
SOAP application "&1" does not exist | The short text describes the object sufficiently | |
| 84 | 083 |
Name "&1" is not valid for SOAP applications | The short text describes the object sufficiently | |
| 85 | 084 |
At least one semantic description must exist | The short text describes the object sufficiently | |
| 86 | 085 |
Error when determining language: "&1" | The short text describes the object sufficiently | |
| 87 | 086 |
Semantic description "&1" is invalid | The short text describes the object sufficiently | |
| 88 | 087 |
Invalid default value '&1' for property '&2:&3' | The short text describes the object sufficiently | |
| 89 | 088 |
Feature '&1' does not have a property called '&2' | The short text describes the object sufficiently | |
| 90 | 089 |
Instantiation error in Feature Factory | The short text describes the object sufficiently | |
| 91 | 090 |
SOAP application "&1" is not active | The short text describes the object sufficiently | |
| 92 | 091 |
Assignment &1 (type &2) already assigned to profile &3 (type &4) | The short text describes the object sufficiently | |
| 93 | 092 |
No profile specified for assignment &1 (type &2) | The short text describes the object sufficiently | |
| 94 | 093 |
Profile &1 (type &2) is not active | The short text describes the object sufficiently | |
| 95 | 094 |
Cannot delete assignment &1 (type &2) | The short text describes the object sufficiently | |
| 96 | 095 |
Error when saving assignment &1 (type &2) | The short text describes the object sufficiently | |
| 97 | 096 |
Assignment &1 (type &2) is initial | The short text describes the object sufficiently | |
| 98 | 097 |
Hash calculation for assignment &1 (type &2) failed | The short text describes the object sufficiently | |
| 99 | 098 |
Could not activate assignment &1 (type &2) | The short text describes the object sufficiently | |
| 100 | 099 |
Preconfiguration is invalid | The short text describes the object sufficiently | |
| 101 | 100 |
Invalid subject type "&1" for this preconfiguration | The short text describes the object sufficiently | |
| 102 | 101 |
Profile type &1 cannot be mapped to an assignment type | The short text describes the object sufficiently | |
| 103 | 102 |
Non-fulfilled dependencies within property list | The short text describes the object sufficiently | |
| 104 | 103 |
Property '&1:&2' with value '&3' is invalid | The short text describes the object sufficiently | |
| 105 | 104 |
Assignment &1 (type &2) cannot be modified | The short text describes the object sufficiently | |
| 106 | 105 |
Profile type &1 cannot be mapped to a configuration type | The short text describes the object sufficiently | |
| 107 | 106 |
Profile &1 with type &2 has multiple service entries | The short text describes the object sufficiently | |
| 108 | 107 |
Invalid combination of parameters in assignment &1 (type &2) | The short text describes the object sufficiently | |
| 109 | 108 |
Cannot determine namespace for object &1 | The short text describes the object sufficiently | |
| 110 | 109 |
Assignment &1 not activated; error in configuration | The short text describes the object sufficiently | |
| 111 | 110 |
Property '&1:&2' is not valid in this property list | The short text describes the object sufficiently | |
| 112 | 111 |
No default value available for property "&1:&2" | The short text describes the object sufficiently | |
| 113 | 112 |
No default URL available for property "&1:&2" | The short text describes the object sufficiently | |
| 114 | 113 |
Cannot cancel changes for assignment &1 and &2 | The short text describes the object sufficiently | |
| 115 | 114 |
Could not modify assignment &1 for profile change | The short text describes the object sufficiently | |
| 116 | 115 |
Assignment &1 of type &2 is not yet saved | The short text describes the object sufficiently | |
| 117 | 116 |
Error when deleting assignment for object &1, &2, and binding &3 | The short text describes the object sufficiently | |
| 118 | 117 |
Cannot copy configuration; invalid name &1 | The short text describes the object sufficiently | |
| 119 | 118 |
Name and/or type of assignment is not specified | The short text describes the object sufficiently | |
| 120 | 119 |
Invalid variants and binding information in configuration &1 | The short text describes the object sufficiently | |
| 121 | 120 |
Invalid assignment type '&1' specified | The short text describes the object sufficiently | |
| 122 | 121 |
Cannot use profile type &1 for assignment type &2 | The short text describes the object sufficiently | |
| 123 | 122 |
Could not activate configuration &1 with type &2 | The short text describes the object sufficiently | |
| 124 | 123 |
Specified profile &1:&2 not the same as saved &3:&4 profile | The short text describes the object sufficiently | |
| 125 | 124 |
Assignment for &1:&2 is invalid; &3 | The short text describes the object sufficiently | |
| 126 | 125 |
Binding &3 in configuration &1:&2; object &4 cannot be deleted | The short text describes the object sufficiently | |
| 127 | 126 |
End point '&1' is not valid for SOAP applications | The short text describes the object sufficiently | |
| 128 | 127 |
No DT profile exists with the name "&1" for SOAP application "&2" | The short text describes the object sufficiently | |
| 129 | 128 |
Status "&1" not valid for DT profile | The short text describes the object sufficiently | |
| 130 | 129 |
Profile assignment not possible; no interface node exists | The short text describes the object sufficiently | |
| 131 | 130 |
Profile assignment not possible; no operation node exists | The short text describes the object sufficiently | |
| 132 | 131 |
Profile assignment not possible; assigned profile is invalid | The short text describes the object sufficiently | |
| 133 | 132 |
Error when reading variant "&2" of service definition "&1": &3 | The short text describes the object sufficiently | |
| 134 | 133 |
Error when reading variant "&2" of service definition "&1" | The short text describes the object sufficiently | |
| 135 | 134 |
No variants of type "&1" exist | The short text describes the object sufficiently | |
| 136 | 135 |
Error when opening LPT of proxy class "&1" | The short text describes the object sufficiently | |
| 137 | 136 |
Invalid WSDL attributes for LPT of proxy class "&1" | The short text describes the object sufficiently | |
| 138 | 137 |
Error: &1 | The short text describes the object sufficiently | |
| 139 | 138 |
Cannot determine LP name for endpoint &1 | The short text describes the object sufficiently | |
| 140 | 139 |
Could not determine name of service definition | The short text describes the object sufficiently | |
| 141 | 140 |
Incorrect combination of parameters | The short text describes the object sufficiently | |
| 142 | 141 |
Cannot find variant for endpoint &1 | The short text describes the object sufficiently | |
| 143 | 142 |
Invalid combination of namespace and interface name | The short text describes the object sufficiently | |
| 144 | 143 |
You cannot specify a generic inbound interface | The short text describes the object sufficiently | |
| 145 | 144 |
Cannot find unique inbound interface for &1:&2 | The short text describes the object sufficiently | |
| 146 | 145 |
Error reading service definition '&1' | The short text describes the object sufficiently | |
| 147 | 146 |
Error reading client proxy '&1' | The short text describes the object sufficiently | |
| 148 | 147 |
Characters &2 are not permitted in string "&1" | The short text describes the object sufficiently | |
| 149 | 148 |
Blanks are not permitted in string "&1" | The short text describes the object sufficiently | |
| 150 | 149 |
Characters &2 and blanks are not permitted in string "&1" | The short text describes the object sufficiently | |
| 151 | 150 |
Configuration name "&1" is invalid | The short text describes the object sufficiently | |
| 152 | 151 |
Configuration does not have an endpoint node | The short text describes the object sufficiently | |
| 153 | 152 |
Endpoints of configuration are in different namespaces | The short text describes the object sufficiently | |
| 154 | 153 |
Invalid name for profile "&1" | The short text describes the object sufficiently | |
| 155 | 154 |
Configuration &1 already exists for interface &2 | The short text describes the object sufficiently | |
| 156 | 155 |
Source and target configuration use the same name (&1) | The short text describes the object sufficiently | |
| 157 | 156 |
No service exists within this configuration | The short text describes the object sufficiently | |
| 158 | 157 |
Undefined value &1 for WSDL section parameter | The short text describes the object sufficiently | |
| 159 | 158 |
You cannot specify both an endpoint key and an endpoint name | The short text describes the object sufficiently | |
| 160 | 159 |
No endpoint key or endpoint name specified | The short text describes the object sufficiently | |
| 161 | 160 |
Specified endpoint key '&1' is invalid | The short text describes the object sufficiently | |
| 162 | 161 |
Specified endpoint name (&1:&2) is invalid | The short text describes the object sufficiently | |
| 163 | 162 |
WSDL HTTP handler not initialized correctly; (&1='&2'?) | The short text describes the object sufficiently | |
| 164 | 163 |
Configuration '&1' of interface '&2' is not active | The short text describes the object sufficiently | |
| 165 | 164 |
Parameters are incomplete or invalid | The short text describes the object sufficiently | |
| 166 | 165 |
Configuration is in use (profile assignment, STCM). No changes possible! | The short text describes the object sufficiently | |
| 167 | 166 |
Configuration &1 (type &2) is already assigned in &3 (type &4) | The short text describes the object sufficiently | |
| 168 | 167 |
Unknown value '&1' for WSDL style parameter | The short text describes the object sufficiently | |
| 169 | 168 |
Unknown assignment type '&1' found | The short text describes the object sufficiently | |
| 170 | 169 |
Error when opening Web service configuration | Space: object requires documentation | |
| 171 | 170 |
No configuration for proxy class "&1" and logical port "&2" | Space: object requires documentation | |
| 172 | 171 |
No Web service configuration for this access path: "&1&2&3&4" | Space: object requires documentation | |
| 173 | 172 |
Subject &1: &2 of type &3 is not active | The short text describes the object sufficiently | |
| 174 | 173 |
No interface exists with name (&1:&2) | The short text describes the object sufficiently | |
| 175 | 174 |
No operation exists with name (&1:&2) | The short text describes the object sufficiently | |
| 176 | 175 |
No service exsits with name (&1:&2) | The short text describes the object sufficiently | |
| 177 | 176 |
No endpoint exists with name (&1:&2) | The short text describes the object sufficiently | |
| 178 | 177 |
No endpoint operation exists with name (&1:&2) | The short text describes the object sufficiently | |
| 179 | 178 |
Web service configuration not yet initialized | Space: object requires documentation | |
| 180 | 179 |
Web service configuration not yet initialized (specific to operation) | Space: object requires documentation | |
| 181 | 180 |
Error in WS configuration when determining location (server/client) | Space: object requires documentation | |
| 182 | 181 |
Assignment for configuration &1 (type &2) is not unique (number: &3) | The short text describes the object sufficiently | |
| 183 | 182 |
Inbound XI interface does not exist: &1 (&2) | The short text describes the object sufficiently | |
| 184 | 183 |
Outbound XI interface does not exist: &1 (&2) | The short text describes the object sufficiently | |
| 185 | 184 |
No design time object or variant specified | The short text describes the object sufficiently | |
| 186 | 185 |
Cannot read ESR design time information; &1 | The short text describes the object sufficiently | |
| 187 | 186 |
Configuration generated by ESR input but profile is missing | The short text describes the object sufficiently | |
| 188 | 187 |
No access URL specified for binding &1 (configuration &2) | The short text describes the object sufficiently | |
| 189 | 188 |
No selected property list exists for binding &1 (&2) | The short text describes the object sufficiently | |
| 190 | 189 |
ESR channel not specified | The short text describes the object sufficiently | |
| 191 | 190 |
Client: IF not specified or specified generically for &1 | The short text describes the object sufficiently | |
| 192 | 191 |
Server: IF not specified or specified generically for &1 | The short text describes the object sufficiently | |
| 193 | 192 |
Specified profile &1 (type &2) cannot be used | The short text describes the object sufficiently | |
| 194 | 193 |
Could not generate configuration for channel/profile &1 | The short text describes the object sufficiently | |
| 195 | 194 |
External access URL not set for channel &1 | The short text describes the object sufficiently | |
| 196 | 195 |
Generic interface information is not permitted here | The short text describes the object sufficiently | |
| 197 | 196 |
More than one configuration created (IIF: &1.&2) | The short text describes the object sufficiently | |
| 198 | 197 |
No interface objects or multiple objects found for proxy &1 (using SIDL) | The short text describes the object sufficiently | |
| 199 | 198 |
No operations foumd for proxy &1 (using SIDL) | The short text describes the object sufficiently | |
| 200 | 199 |
No endpoints or multiple endpoints exist for configuration &1 | The short text describes the object sufficiently | |
| 201 | 200 |
Property &1 not set for channel &2 | The short text describes the object sufficiently | |
| 202 | 201 |
Calculation error in access URL for channel &1; &2 | The short text describes the object sufficiently | |
| 203 | 202 |
No unique active proxy definition exists for OIF &1:&2 (number: &3) | The short text describes the object sufficiently | |
| 204 | 203 |
Target host not specified: binding &1; configuration &2 | The short text describes the object sufficiently | |
| 205 | 204 |
Unknown protocol '&1': binding &2; configuration &3 | The short text describes the object sufficiently | |
| 206 | 205 |
Calculate property failed: binding '&1'; configuration '&2'. &3&4 | The short text describes the object sufficiently | |
| 207 | 206 |
Property missing: &1 (&2) | The short text describes the object sufficiently | |
| 208 | 207 |
Configurations are assigned to the profile; special change required | The short text describes the object sufficiently | |
| 209 | 208 |
Error in deserialization of DT configuration | The short text describes the object sufficiently | |
| 210 | 209 |
URL path not specified; usage relationship cannot be resolved | The short text describes the object sufficiently | |
| 211 | 210 |
Internal error when reading usage condition; &1 | The short text describes the object sufficiently | |
| 212 | 211 |
Invalid input; not all parameters determined | The short text describes the object sufficiently | |
| 213 | 212 |
Could not save usage relationship | The short text describes the object sufficiently | |
| 214 | 213 |
Object is still being used and cannot be deleted | The short text describes the object sufficiently | |
| 215 | 214 |
Could not delete usage relationship | The short text describes the object sufficiently | |
| 216 | 215 |
Specified configuration &1 with type &2 does not exist | The short text describes the object sufficiently | |
| 217 | 216 |
Configuration type &1 not supported for this operation | The short text describes the object sufficiently | |
| 218 | 217 |
Unknown protocol '&1' specified | The short text describes the object sufficiently | |
| 219 | 218 |
Error when reading local information for protocol '&1' | The short text describes the object sufficiently | |
| 220 | 219 |
Calculated URL path does not exist for binding &1 (&2) | The short text describes the object sufficiently | |
| 221 | 220 |
IIF '&1' has no active service definition: NS '&2' | The short text describes the object sufficiently | |
| 222 | 221 |
LP name &1 is already allocated for DT object &2 | The short text describes the object sufficiently | |
| 223 | 222 |
Property &1 has an empty value for channel &2 | The short text describes the object sufficiently | |
| 224 | 223 |
IIF '&1' has no active auto-generated service definition: NS '&2' | The short text describes the object sufficiently | |
| 225 | 224 |
Specify a SOAP application name and subject type | The short text describes the object sufficiently | |
| 226 | 225 |
Could not calculate hash value (RC: &1) | The short text describes the object sufficiently | |
| 227 | 226 |
Could not lock configuration entry (hash: &1) | The short text describes the object sufficiently | |
| 228 | 227 |
Could not lock secure link entry &1 | The short text describes the object sufficiently | |
| 229 | 228 |
Could not save secure link entry &1 | The short text describes the object sufficiently | |
| 230 | 229 |
Data too long for secure link entry &1; &2 | The short text describes the object sufficiently | |
| 231 | 230 |
Secure link entry &1 is read-only and not locked | The short text describes the object sufficiently | |
| 232 | 231 |
Write error in secure link ID &1. &2&3&4 | The short text describes the object sufficiently | |
| 233 | 232 |
Read error in secure link ID &1. &2&3&4 | The short text describes the object sufficiently | |
| 234 | 233 |
Could not delete secure link entry &1; &2 | The short text describes the object sufficiently | |
| 235 | 234 |
Cannot navigate to entry &1 in SOAP Runtime | The short text describes the object sufficiently | |
| 236 | 235 |
Key (ID and/or type) of SOAP Runtime objects is not specified | The short text describes the object sufficiently | |
| 237 | 236 |
Transport binding contains properties with differing releases | The short text describes the object sufficiently | |
| 238 | 237 |
Caller cannot call this method | The short text describes the object sufficiently | |
| 239 | 238 |
Entry in configuration &1 does not exist for property &2 | The short text describes the object sufficiently | |
| 240 | 239 |
Error when saving configuration &1 for property &2 | The short text describes the object sufficiently | |
| 241 | 240 |
Unknown data type &1 specified for secure store | The short text describes the object sufficiently | |
| 242 | 241 |
Entry in profile &1 does not exist for property &2 | The short text describes the object sufficiently | |
| 243 | 242 |
Error saving profile &1 for property &2 | The short text describes the object sufficiently | |
| 244 | 243 |
Service node and binding node are in same namespace | The short text describes the object sufficiently | |
| 245 | 244 |
Web service configuration "&1" is not active | The short text describes the object sufficiently | |
| 246 | 245 |
Access URL for administration tool is not defined | The short text describes the object sufficiently | |
| 247 | 246 |
Unknown error: &1&2&3&4 | The short text describes the object sufficiently | |
| 248 | 247 |
Enter a host name | The short text describes the object sufficiently | |
| 249 | 248 |
Enter a valid port number [1..65535] | The short text describes the object sufficiently | |
| 250 | 249 |
Enter a valid access path | The short text describes the object sufficiently | |
| 251 | 250 |
Access information for web service administration saved | The short text describes the object sufficiently | |
| 252 | 251 |
Enter a valid Web service administration user | The short text describes the object sufficiently | |
| 253 | 252 |
Enter a Web service administration password | The short text describes the object sufficiently | |
| 254 | 253 |
Error saving: &1&2&3&4 | The short text describes the object sufficiently | |
| 255 | 254 |
Entered access data is formally correct | The short text describes the object sufficiently | |
| 256 | 255 |
Could not generate GUI container | The short text describes the object sufficiently | |
| 257 | 256 |
Could not create HTML control | The short text describes the object sufficiently | |
| 258 | 257 |
Query error; no action | The short text describes the object sufficiently | |
| 259 | 258 |
Configuration data removed from permanent memory | The short text describes the object sufficiently | |
| 260 | 259 |
Configuration data not changed in permanent memory | The short text describes the object sufficiently | |
| 261 | 260 |
Error deleting configuration data; &1&2&3&4 | The short text describes the object sufficiently | |
| 262 | 261 |
Error repeating read of configuration data; &1 | The short text describes the object sufficiently | |
| 263 | 262 |
Configuration data read from persistent memory again | The short text describes the object sufficiently | |
| 264 | 263 |
Error when getting administration data; &1 | The short text describes the object sufficiently | |
| 265 | 264 |
No administration data exists yet | The short text describes the object sufficiently | |
| 266 | 265 |
Internal error; cannot set protocol details | The short text describes the object sufficiently | |
| 267 | 266 |
Profile &1 of type &2 is still used in assignments | The short text describes the object sufficiently | |
| 268 | 267 |
Hash value calculation failed; &1 | The short text describes the object sufficiently | |
| 269 | 268 |
Namespace/name of property missing for calculation of hash value | The short text describes the object sufficiently | |
| 270 | 269 |
Error in database access for client-wide configuration | The short text describes the object sufficiently | |
| 271 | 270 |
Property cannot be locked: &1, &2 | The short text describes the object sufficiently | |
| 272 | 271 |
Object cannot be modified; switch to change mode | The short text describes the object sufficiently | |
| 273 | 272 |
Permanent error. &1&2&3&4 | The short text describes the object sufficiently | |
| 274 | 273 |
Error when reading secure store for SOAP key '&1' | The short text describes the object sufficiently | |
| 275 | 274 |
Invalid state: &1 | The short text describes the object sufficiently | |
| 276 | 275 |
Unknown end point type: &1 | The short text describes the object sufficiently | |
| 277 | 276 |
Unknown state change: &1 | The short text describes the object sufficiently | |
| 278 | 277 |
Could not get configuration &1 with state &2 | The short text describes the object sufficiently | |
| 279 | 278 |
Error when starting browser (RC=&1) | The short text describes the object sufficiently | |
| 280 | 279 |
Browser started | The short text describes the object sufficiently | |
| 281 | 280 |
IIF does not have an inbound proxy; IIF: &1:&2 | The short text describes the object sufficiently | |
| 282 | 281 |
IIF does not have a service definition; IIF: '&1':'&2' | The short text describes the object sufficiently | |
| 283 | 282 |
DT object '&1' is inconsistent; operation '&2' is missing (NS: '&3') | The short text describes the object sufficiently | |
| 284 | 283 |
No configuration for binding key "&1" | The short text describes the object sufficiently | |
| 285 | 284 |
Configuration with binding key "&1" is not active | The short text describes the object sufficiently | |
| 286 | 285 |
Property '&1' is not numerical | The short text describes the object sufficiently | |
| 287 | 286 |
Cannot map language code &1 to ISO code | The short text describes the object sufficiently | |
| 288 | 287 |
Binding names are empty or have different namespaces | The short text describes the object sufficiently | |
| 289 | 288 |
Interface "&1" is not active | The short text describes the object sufficiently | |
| 290 | 289 |
Protocol &1 is not supported | The short text describes the object sufficiently | |
| 291 | 290 |
No interface node exists | The short text describes the object sufficiently | |
| 292 | 291 |
Cannot determine server name of database | The short text describes the object sufficiently | |
| 293 | 292 |
Cannot determine design time URL; &1 | The short text describes the object sufficiently | |
| 294 | 293 |
Invalid value for WSDL version "&1" | The short text describes the object sufficiently | |
| 295 | 294 |
Invalid value for WSDL format "&1" | The short text describes the object sufficiently | |
| 296 | 295 |
Invalid value for WSDL style "&1" | The short text describes the object sufficiently | |
| 297 | 296 |
Invalid cardinality. Property: &1. Namespace: &2 | The short text describes the object sufficiently | |
| 298 | 297 |
Design time configuration name is not specified | The short text describes the object sufficiently | |
| 299 | 298 |
Server design time object '&1' does not exist | The short text describes the object sufficiently | |
| 300 | 299 |
Client design time object or STCM '&1' does not exist | The short text describes the object sufficiently | |
| 301 | 300 |
You cannot use this API to change DT object &1 | The short text describes the object sufficiently | |
| 302 | 301 |
No DT object and DT configuration found | The short text describes the object sufficiently | |
| 303 | 302 |
Error reading directory entry (&1, &2, &3) | The short text describes the object sufficiently | |
| 304 | 303 |
DT configuration does not exist (&1, &2, &3) | The short text describes the object sufficiently | |
| 305 | 304 |
Serialiazation of object is missing: &1 (status: &2) | The short text describes the object sufficiently | |
| 306 | 305 |
Error getting ESR data: &1&2&3&4 | The short text describes the object sufficiently | |
| 307 | 306 |
No error messages selected | The short text describes the object sufficiently | |
| 308 | 307 |
Error in user query. &1 | The short text describes the object sufficiently | |
| 309 | 308 |
Deletion error | The short text describes the object sufficiently | |
| 310 | 309 |
Error making correction | The short text describes the object sufficiently | |
| 311 | 310 |
Endpoint type is not specified | The short text describes the object sufficiently | |
| 312 | 311 |
You cannot change the key attributes | The short text describes the object sufficiently | |
| 313 | 312 |
DT configuration is invalid | The short text describes the object sufficiently | |
| 314 | 313 |
Error in WSDL parsing: &1 | The short text describes the object sufficiently | |
| 315 | 314 |
Could not find DT configuration from WSDL | The short text describes the object sufficiently | |
| 316 | 315 |
Database operation '&1' in table '&2' failed | The short text describes the object sufficiently | |
| 317 | 316 |
Serialized data of design time object not found | The short text describes the object sufficiently | |
| 318 | 317 |
Design time object '&1' is not locked | The short text describes the object sufficiently | |
| 319 | 318 |
WSDL does not contain information about interface | The short text describes the object sufficiently | |
| 320 | 319 |
WSDL does not contain information about SOAP application | The short text describes the object sufficiently | |
| 321 | 320 |
ICF error: &1&2&3&4 | The short text describes the object sufficiently | |
| 322 | 321 |
No valid request name for operation: '&1' | The short text describes the object sufficiently | |
| 323 | 322 |
Error when creating DT configuration: '&1' | The short text describes the object sufficiently | |
| 324 | 323 |
Could not construct DT configuration | The short text describes the object sufficiently | |
| 325 | 324 |
Object from SIDL generation is unknown | The short text describes the object sufficiently | |
| 326 | 325 |
Method '&1' can get SIDL from DT object only | The short text describes the object sufficiently | |
| 327 | 326 |
Method '&1' can get proxy from ESR-generated service only | The short text describes the object sufficiently | |
| 328 | 327 |
Client object; SIDL generated for server objects only | The short text describes the object sufficiently | |
| 329 | 328 |
Design time configuration '&1' does not exist | The short text describes the object sufficiently | |
| 330 | 329 |
Design time configuration name is not specified | The short text describes the object sufficiently | |
| 331 | 330 |
DT configuration &1: Endpoint type is not unique | The short text describes the object sufficiently | |
| 332 | 331 |
Change is possible only for assigned profiles | The short text describes the object sufficiently | |
| 333 | 332 |
Qualified name of inbound interface is not specified | The short text describes the object sufficiently | |
| 334 | 333 |
Name of design time object is not specified | The short text describes the object sufficiently | |
| 335 | 334 |
No design time configuration found for '&1' | The short text describes the object sufficiently | |
| 336 | 335 |
No old SOAP server runtime configurations found | The short text describes the object sufficiently | |
| 337 | 336 |
Cannot find DT profile &2 for SOAP application &1 | The short text describes the object sufficiently | |
| 338 | 337 |
Error when deleting Web service configuration(s) | The short text describes the object sufficiently | |
| 339 | 338 |
At least one error or warning occurred. See long text for handling | Space: object requires documentation | |
| 340 | 339 |
ESR IF name is not (fully) specified | The short text describes the object sufficiently | |
| 341 | 340 |
User &1 attempted to load a SOAP application at &3 on &2 | The short text describes the object sufficiently | |
| 342 | 341 |
User &1 loaded SOAP application &4 at &3 on &2 | The short text describes the object sufficiently | |
| 343 | 342 |
User &1 attempted to load a DT profile at &3 on &2 | The short text describes the object sufficiently | |
| 344 | 343 |
User &1 loaded DT profile &3 for SOAP application &4 on &2 | The short text describes the object sufficiently | |
| 345 | 344 |
Request/task &1 does not exist or cannot be used | The short text describes the object sufficiently | |
| 346 | 345 |
LP name &1 cannot be used for local calls | The short text describes the object sufficiently | |
| 347 | 346 |
Property &2:&3 missing in profile &1 | The short text describes the object sufficiently | |
| 348 | 347 |
Property &2:&3 missing in destination &1 | The short text describes the object sufficiently | |
| 349 | 348 |
Values in profile &1 and destination &2 do not match; property &3:&4 | The short text describes the object sufficiently | |
| 350 | 349 |
Destination &1; property not set &2:&3 | The short text describes the object sufficiently | |
| 351 | 350 |
Destination &1; HTTP error: &2&3&4 | The short text describes the object sufficiently | |
| 352 | 351 |
Separate browser window started | The short text describes the object sufficiently | |
| 353 | 352 |
Feature Factory of runtime environment not instantiated | The short text describes the object sufficiently | |
| 354 | 353 |
No property key for property "&1" of feature "&2" | The short text describes the object sufficiently | |
| 355 | 354 |
Multiple profiles found for destination &1 | The short text describes the object sufficiently | |
| 356 | 355 |
Invalid parameter values when opening RT cache instance | The short text describes the object sufficiently | |
| 357 | 356 |
No configuration exists for binding %1 | The short text describes the object sufficiently | |
| 358 | 357 |
Configuration key is initial | The short text describes the object sufficiently | |
| 359 | 358 |
'&1' is not a client-side SOAP application | The short text describes the object sufficiently | |
| 360 | 359 |
No valid configuration derived from WSDL | The short text describes the object sufficiently | |
| 361 | 360 |
Profile &1 (&2) already used in an assignment other than &3 | The short text describes the object sufficiently | |
| 362 | 361 |
RT configuration &1 blocked by another object in working memory | The short text describes the object sufficiently | |
| 363 | 362 |
RT cache object &1 blocked by another object in working memory | The short text describes the object sufficiently | |
| 364 | 363 |
Configuration &1 does not yet have an interface node | The short text describes the object sufficiently | |
| 365 | 364 |
RT cache object &1 does not have binding &2 | The short text describes the object sufficiently | |
| 366 | 365 |
User &1 saved configuration &2 for interface &3 | The short text describes the object sufficiently | |
| 367 | 366 |
User &1 activated configuration &2 for interface &3 | The short text describes the object sufficiently | |
| 368 | 367 |
User &1 deactivated configuration &2 for interface &3 | The short text describes the object sufficiently | |
| 369 | 368 |
User &1 deleted configuration &2 for interface &3 | The short text describes the object sufficiently | |
| 370 | 369 |
User &1 saved profile &2 | The short text describes the object sufficiently | |
| 371 | 370 |
User &1 activated profile &2 | The short text describes the object sufficiently | |
| 372 | 371 |
User &1 deactivated profile &2 | The short text describes the object sufficiently | |
| 373 | 372 |
User &1 deleted profile &2 | The short text describes the object sufficiently | |
| 374 | 373 |
User &1 saved destination &2 | The short text describes the object sufficiently | |
| 375 | 374 |
User &1 activated destination &2 | The short text describes the object sufficiently | |
| 376 | 375 |
User &1 deactivated destination &2 | The short text describes the object sufficiently | |
| 377 | 376 |
User &1 deleted destination &2 | The short text describes the object sufficiently | |
| 378 | 377 |
Error in assignment of LP '&1': &2&3&4 | The short text describes the object sufficiently | |
| 379 | 378 |
Cannot find binding '&1' for LP '&2' | The short text describes the object sufficiently | |
| 380 | 379 |
Property &1 not found in LP &2 and binding &3 | The short text describes the object sufficiently | |
| 381 | 380 |
Cannot find binding '&1' | The short text describes the object sufficiently | |
| 382 | 381 |
Not found: Property &1 (binding &2) | The short text describes the object sufficiently | |
| 383 | 382 |
Multiple properties found: Property &1 (binding &2) | The short text describes the object sufficiently | |
| 384 | 383 |
HTTP error in LP &1: &2&3&4 | The short text describes the object sufficiently | |
| 385 | 384 |
Not enough parameters for object instance: &1 | The short text describes the object sufficiently | |
| 386 | 385 |
Severe error when getting maximum property length of RT cache | The short text describes the object sufficiently | |
| 387 | 386 |
Destination cannot be modified | The short text describes the object sufficiently | |
| 388 | 387 |
Destination has not yet been saved | The short text describes the object sufficiently | |
| 389 | 388 |
Multiple values for parameter "&1" | The short text describes the object sufficiently | |
| 390 | 389 |
You cannot specify a service definition and binding at the same time | The short text describes the object sufficiently | |
| 391 | 390 |
No service definition, interface name, or binding specified | The short text describes the object sufficiently | |
| 392 | 391 |
Endpoint key &1 is invalid | The short text describes the object sufficiently | |
| 393 | 392 |
Service definition "&1" is invalid | The short text describes the object sufficiently | |
| 394 | 393 |
Agreement &1 is invalid | The short text describes the object sufficiently | |
| 395 | 394 |
No value for parameter &1 | The short text describes the object sufficiently | |
| 396 | 395 |
Invalid value for protocol &1 | The short text describes the object sufficiently | |
| 397 | 396 |
You cannot specify a service definition and agreement at the same time | The short text describes the object sufficiently | |
| 398 | 397 |
Error occurred that cannot be handled | The short text describes the object sufficiently | |
| 399 | 398 |
Generated WSDL document does not contain data | The short text describes the object sufficiently | |
| 400 | 399 |
No data for binding key "&1" | The short text describes the object sufficiently | |
| 401 | 400 |
Subject context contains more than one endpoint for endpoint key "&1" | The short text describes the object sufficiently | |
| 402 | 401 |
Subject context does not contain an endpoint for endpoint key "&1" | The short text describes the object sufficiently | |
| 403 | 402 |
Invalid value "&1" for WSDL version | The short text describes the object sufficiently | |
| 404 | 403 |
Invalid value "&1" for WSDL style | The short text describes the object sufficiently | |
| 405 | 404 |
Invalid value "&1" for WSDL format | The short text describes the object sufficiently | |
| 406 | 405 |
Invalid value "&1" for WSDL section | The short text describes the object sufficiently | |
| 407 | 406 |
Invalid value "&1" for transport protocol of WSDL request | The short text describes the object sufficiently | |
| 408 | 407 |
Could not determine name for service definition | The short text describes the object sufficiently | |
| 409 | 408 |
Cannot determine web service URL | The short text describes the object sufficiently | |
| 410 | 409 |
Agreement found in unexpected position | The short text describes the object sufficiently | |
| 411 | 410 |
You cannot specify more than one service definition | The short text describes the object sufficiently | |
| 412 | 411 |
You cannot specify more than one binding key | The short text describes the object sufficiently | |
| 413 | 412 |
You cannot specify an agreement for this WSDL section | The short text describes the object sufficiently | |
| 414 | 413 |
Serious error; could not create GUID | The short text describes the object sufficiently | |
| 415 | 414 |
Invalid framework ID: "&1" | The short text describes the object sufficiently | |
| 416 | 415 |
Invalid access of framework "&1" to objects of framework "&2" | The short text describes the object sufficiently | |
| 417 | 416 |
Undefined configuration status "&1" | The short text describes the object sufficiently | |
| 418 | 417 |
No data after RTC conversion | The short text describes the object sufficiently | |
| 419 | 418 |
Invalid binding: ID = "&1", KEY = "&2" | The short text describes the object sufficiently | |
| 420 | 419 |
Different number of binding nodes and binding keys | The short text describes the object sufficiently | |
| 421 | 420 |
Passed and found binding keys are different | The short text describes the object sufficiently | |
| 422 | 421 |
No data for configuration key "&1" in database | The short text describes the object sufficiently | |
| 423 | 422 |
Empty context table for configuration key "&1" | The short text describes the object sufficiently | |
| 424 | 423 |
No binding name for binding ID "&1" in configuration "&2" | The short text describes the object sufficiently | |
| 425 | 424 |
UDDI publishing of configuration &1 failed: &2 | The short text describes the object sufficiently | |
| 426 | 425 |
UDDI unpublishing of configuration &1 failed: &2 | The short text describes the object sufficiently | |
| 427 | 426 |
Binding "&1" is not part of a server configuration | The short text describes the object sufficiently | |
| 428 | 427 |
Call URL for binding &1 exists only if configuration is active | The short text describes the object sufficiently | |
| 429 | 428 |
WSDL URLs for binding &1 exist only if configuration is active | The short text describes the object sufficiently | |
| 430 | 429 |
SIDL generation possible only if configuration is active | The short text describes the object sufficiently | |
| 431 | 430 |
WSDL generation possible only if configuration is active | The short text describes the object sufficiently | |
| 432 | 431 |
No configuration for local ICF path "&1" | Space: object requires documentation | |
| 433 | 432 |
Initial binding key for local ICF path "&1" | Space: object requires documentation | |
| 434 | 433 |
No data for binding key "&1" | The short text describes the object sufficiently | |
| 435 | 434 |
Cannot delete default profile | The short text describes the object sufficiently | |
| 436 | 435 |
No binding data for configuration key: "&1" | The short text describes the object sufficiently | |
| 437 | 436 |
Error in initialization of SOAP application: "&1" | The short text describes the object sufficiently | |
| 438 | 437 |
Invalid character "&2" in SOAP application name "&1" | The short text describes the object sufficiently | |
| 439 | 438 |
Invalid blanks in SOAP application name "&1" | The short text describes the object sufficiently | |
| 440 | 439 |
Error when parsing WSDL | The short text describes the object sufficiently | |
| 441 | 440 |
No data for binding "&1:&2" in subject table | The short text describes the object sufficiently | |
| 442 | 441 |
IIF &1 (channel &2) does not have an endpoint | The short text describes the object sufficiently | |
| 443 | 442 |
Configuration destination "&1" does not exist | The short text describes the object sufficiently | |
| 444 | 443 |
Assignment &1 (type &2): Generic client &3 does not have an endpoint | The short text describes the object sufficiently | |
| 445 | 444 |
Could not open job &1; RC = &2 | The short text describes the object sufficiently | |
| 446 | 445 |
Could not start job &1; RC = &2 | The short text describes the object sufficiently | |
| 447 | 446 |
Could not save job &1; RC = &2 | The short text describes the object sufficiently | |
| 448 | 447 |
Could not save task. (&1, &2). ID=&3 | The short text describes the object sufficiently | |
| 449 | 448 |
Current call stack has no authorization for this action | The short text describes the object sufficiently | |
| 450 | 449 |
Invalid interface namespace "&1" | The short text describes the object sufficiently | |
| 451 | 450 |
You cannot specify more than one interface namespace | The short text describes the object sufficiently | |
| 452 | 451 |
Invalid interface name "&1" | The short text describes the object sufficiently | |
| 453 | 452 |
You cannot specify more than one interface name | The short text describes the object sufficiently | |
| 454 | 453 |
Interface name not specified | The short text describes the object sufficiently | |
| 455 | 454 |
Channel found in an unexpected position | The short text describes the object sufficiently | |
| 456 | 455 |
Channel "&1" is invalid | The short text describes the object sufficiently | |
| 457 | 456 |
No channel specified | The short text describes the object sufficiently | |
| 458 | 457 |
You cannot specify a service definition and an interface at the same time | The short text describes the object sufficiently | |
| 459 | 458 |
You cannot specify an interface and a binding at the same time | The short text describes the object sufficiently | |
| 460 | 459 |
Invalid WSDL section "&1" when interface and channel specified | The short text describes the object sufficiently | |
| 461 | 460 |
Interface name found in an unexpected position | The short text describes the object sufficiently | |
| 462 | 461 |
IIF &1 (channel &2): No ESR reference | The short text describes the object sufficiently | |
| 463 | 462 |
IIF &1 (channel &2): No service definition exists | The short text describes the object sufficiently | |
| 464 | 463 |
IIF &1 (channel &2): No unique service definition (number: &3) | The short text describes the object sufficiently | |
| 465 | 464 |
IIF &1 (channel &2): No unique configuration (number: &3) | The short text describes the object sufficiently | |
| 466 | 465 |
IIF &1 (channel &2): No unique binding (number: &3) | The short text describes the object sufficiently | |
| 467 | 466 |
IIF &1 (channel &2): Binding '&3' has no binding name | The short text describes the object sufficiently | |
| 468 | 467 |
No changes possible; object opened in client-specific mode | The short text describes the object sufficiently | |
| 469 | 468 |
IIF &1 (channel &2) invalid: &3&4 | The short text describes the object sufficiently | |
| 470 | 469 |
Configuration &1 does not have a binding | The short text describes the object sufficiently | |
| 471 | 470 |
Transport protocol missing in configuration "&1" | The short text describes the object sufficiently | |
| 472 | 471 |
Host name missing in configuration "&1" | The short text describes the object sufficiently | |
| 473 | 472 |
Invalid URL path "&1" in configuration "&2" | The short text describes the object sufficiently | |
| 474 | 473 |
Missing URL path in configuration "&1" | The short text describes the object sufficiently | |
| 475 | 474 |
Invalid host name "&1" in configuration "&2" | The short text describes the object sufficiently | |
| 476 | 475 |
Invalid URL port "&1" in configuration "&2" | The short text describes the object sufficiently | |
| 477 | 476 |
URL port missing in configuration "&1" | The short text describes the object sufficiently | |
| 478 | 477 |
Binding type missing in configuration "&1" | The short text describes the object sufficiently | |
| 479 | 478 |
User interaction error | The short text describes the object sufficiently | |
| 480 | 479 |
Error: &1&2&3&4 | The short text describes the object sufficiently | |
| 481 | 480 |
Could not delete job &1; RC=&2 | The short text describes the object sufficiently | |
| 482 | 481 |
Error in WSDL access (destination &1). &2&3&4 | The short text describes the object sufficiently | |
| 483 | 482 |
Job '&1' deleted | The short text describes the object sufficiently | |
| 484 | 483 |
Job '&1' already exists and does not need to be scheduled | The short text describes the object sufficiently | |
| 485 | 484 |
Job '&1' scheduled | The short text describes the object sufficiently | |
| 486 | 485 |
Error when creating instance of assignment query interface | The short text describes the object sufficiently | |
| 487 | 486 |
Serialization error in serializer: &1 | The short text describes the object sufficiently | |
| 488 | 487 |
Serialization error: &1 | The short text describes the object sufficiently | |
| 489 | 488 |
Error when creating instance of URL handler | The short text describes the object sufficiently | |
| 490 | 489 |
Access URL not set or cannot be determined | The short text describes the object sufficiently | |
| 491 | 490 |
Could not read property '&1' ('&2') | The short text describes the object sufficiently | |
| 492 | 491 |
Assignment missing; configuration: '&1' ('&2'); DT object: '&3' | The short text describes the object sufficiently | |
| 493 | 492 |
Logical port '&1' not locked | The short text describes the object sufficiently | |
| 494 | 493 |
Authentication method for logical port '&1' is unknown | The short text describes the object sufficiently | |
| 495 | 494 |
No WSDL: '&1' | The short text describes the object sufficiently | |
| 496 | 495 |
Assignment '&1' (type '&2') saved (configurations: &3) | The short text describes the object sufficiently | |
| 497 | 496 |
Assignment '&1' (type '&2') activated (configurations: &3) | The short text describes the object sufficiently | |
| 498 | 497 |
Assignment '&1' (type '&2') deleted (configurations: &3) | The short text describes the object sufficiently | |
| 499 | 498 |
Assignment '&1' (type '&2') removed | The short text describes the object sufficiently | |
| 500 | 499 |
Assignment '&1' (type '&2') deactivated (configurations: &3) | The short text describes the object sufficiently | |
| 501 | 500 |
WSDL URL generation: Property '&1' is missing (NS: '&2') | The short text describes the object sufficiently | |
| 502 | 501 |
ESR P2P client assignment '&1' (type '&2'): DT object '&3' | The short text describes the object sufficiently | |
| 503 | 502 |
ESR P2P server assignment '&1' (type '&2'): DT object '&3' | The short text describes the object sufficiently | |
| 504 | 503 |
ESR IS client assignment '&1' (type '&2'): Channel '&3', IF '&4' | The short text describes the object sufficiently | |
| 505 | 504 |
ESR IS server assignment '&1' (type '&2'): DT object '&3' | The short text describes the object sufficiently | |
| 506 | 505 |
Unknown error in WSDL generation | The short text describes the object sufficiently | |
| 507 | 506 |
No check subject chosen. Select at least one check | The short text describes the object sufficiently | |
| 508 | 507 |
No runtime configuration found for specified criteria | The short text describes the object sufficiently | |
| 509 | 508 |
Exception: &1&2&3&4 | The short text describes the object sufficiently | |
| 510 | 509 |
No inconsistencies found | The short text describes the object sufficiently | |
| 511 | 510 |
DT object '&1' is not in namespace '&2' | The short text describes the object sufficiently | |
| 512 | 511 |
Task inserted: ESR IS client assignment '&1' (type '&2'). ID=&3 | The short text describes the object sufficiently | |
| 513 | 512 |
Task removed: ESR IS client assignment '&1' (type '&2'). ID=&3 | The short text describes the object sufficiently | |
| 514 | 513 |
Error when reading task ID (number range = &1, RC = &2) | The short text describes the object sufficiently | |
| 515 | 514 |
Could not remove task (&1, &2); ID=&3 | The short text describes the object sufficiently | |
| 516 | 515 |
Task job '&1' scheduled ('&2' min) | The short text describes the object sufficiently | |
| 517 | 516 |
Task job '&1' removed | The short text describes the object sufficiently | |
| 518 | 517 |
No configuration for operation "&1{&2}" (binding key: "&3") | The short text describes the object sufficiently | |
| 519 | 518 |
Operation "&1{&2}" not supported (interface: "&3" binding key: "&4") | Space: object requires documentation | |
| 520 | 519 |
Cannot delete binding: &1 (&2) | The short text describes the object sufficiently | |
| 521 | 520 |
Error in DT configuration '&1': &2&3&4 | The short text describes the object sufficiently | |
| 522 | 521 |
No design time configuration for interface "&1{&2}" | The short text describes the object sufficiently | |
| 523 | 522 |
No design time configuration for operation "&1{&2}" | The short text describes the object sufficiently | |
| 524 | 523 |
No operations for interface "&1{&2}" | The short text describes the object sufficiently | |
| 525 | 524 |
Configuration '&1' has '&2' default LP | The short text describes the object sufficiently | |
| 526 | 525 |
Configuration "&1" has no operation | The short text describes the object sufficiently | |
| 527 | 526 |
Invalid number of "MEP" attributes in operation "&1{&2}" | The short text describes the object sufficiently | |
| 528 | 527 |
Multiple "blocking" attributes in operation "&1{&2}" | The short text describes the object sufficiently | |
| 529 | 528 |
Multiple "WSRM" attributes in operation "&1{&2}" | The short text describes the object sufficiently | |
| 530 | 529 |
"Blocking" required for "Request/Response" operation "&1{&2}" | The short text describes the object sufficiently | |
| 531 | 530 |
"Blocking" not permitted for "OneWay" operation "&1{&2}" | The short text describes the object sufficiently | |
| 532 | 531 |
No "WSRM" possible for "Request/Response" operation "&1{&2}" | The short text describes the object sufficiently | |
| 533 | 532 |
"WSRM" required for "OneWay" operation "&1{&2}" | The short text describes the object sufficiently | |
| 534 | 533 |
Globale property &1 (&2) deleted | The short text describes the object sufficiently | |
| 535 | 534 |
Values of global property &1 (&2) deleted | The short text describes the object sufficiently | |
| 536 | 535 |
Group &1 of global property &2 (&3) deleted | The short text describes the object sufficiently | |
| 537 | 536 |
Global property &1 (&2) saved | The short text describes the object sufficiently | |
| 538 | 537 |
Global property &1 (&2): Encrypted value (group &3) added | The short text describes the object sufficiently | |
| 539 | 538 |
Global property &1 (&2): Simple value (group &3) added | The short text describes the object sufficiently | |
| 540 | 539 |
Global property &1 (&2): Encrypted value added | The short text describes the object sufficiently | |
| 541 | 540 |
Global property &1 (&2): Simple value added | The short text describes the object sufficiently | |
| 542 | 541 |
Global property &1 (&2): Multiple values (&3) added | The short text describes the object sufficiently | |
| 543 | 542 |
Global property &1 (&2): Value (group &3) deleted | The short text describes the object sufficiently | |
| 544 | 543 |
Global property &1 (&2): Value deleted | The short text describes the object sufficiently | |
| 545 | 544 |
Global property &1 (&2): Multiple values (&3) set | The short text describes the object sufficiently | |
| 546 | 545 |
Use transaction &1 for internal SAP purposes only; alternative: &2 | The short text describes the object sufficiently | |
| 547 | 546 |
Error in self-test of global SOAP properties: Incorrect values | The short text describes the object sufficiently | |
| 548 | 547 |
Error in self-test of global SOAP properties: No deletion possible | The short text describes the object sufficiently | |
| 549 | 548 |
Task for assignment '&1' (type '&2'); LP '&3' | The short text describes the object sufficiently | |
| 550 | 549 |
No template specified for profile copy constructor | The short text describes the object sufficiently | |
| 551 | 550 |
Profile '&1' (type '&2') already exists and cannot be created again | The short text describes the object sufficiently | |
| 552 | 551 |
Software component version found in unexpected position | The short text describes the object sufficiently | |
| 553 | 552 |
Software component version "&1" is invalid | The short text describes the object sufficiently | |
| 554 | 553 |
DT object &1 is being used; configuration &2 (type &3, client &4) | The short text describes the object sufficiently | |
| 555 | 554 |
Exception of type "&1" caught: "&2" | The short text describes the object sufficiently | |
| 556 | 555 |
No exception handling possible for type "&2"; object not instantiated | The short text describes the object sufficiently | |
| 557 | 556 |
Service definition "&1" is not released (configuration missing) | The short text describes the object sufficiently | |
| 558 | 557 |
No active configuration found for specified values | The short text describes the object sufficiently | |
| 559 | 558 |
Configuration request is not in change mode | The short text describes the object sufficiently | |
| 560 | 559 |
Profile has not yet been saved | The short text describes the object sufficiently | |
| 561 | 560 |
Error when reading DT object &1. &2&3&4 | The short text describes the object sufficiently | |
| 562 | 561 |
Pending action found for specified values; ID=&1 | The short text describes the object sufficiently | |
| 563 | 562 |
Assignment &1 (type &2): Generic client &3 does not exist | The short text describes the object sufficiently | |
| 564 | 563 |
No job exists for pending tasks | The short text describes the object sufficiently | |
| 565 | 564 |
Invalid endpoint namespace "&1" | The short text describes the object sufficiently | |
| 566 | 565 |
Invalid service namespace "&1" | The short text describes the object sufficiently | |
| 567 | 566 |
Select a service for the WSDL display | The short text describes the object sufficiently | |
| 568 | 567 |
Service &1 not found | The short text describes the object sufficiently | |
| 569 | 568 |
Error when reading WSDL URL: &1&2&3&4 | The short text describes the object sufficiently | |
| 570 | 569 |
Configuration &1 is not active which means no WSDL can be generated | The short text describes the object sufficiently | |
| 571 | 570 |
Error when initializing configuration context: &1&2&3&4 | The short text describes the object sufficiently | |
| 572 | 571 |
No service/endpoint selected | The short text describes the object sufficiently | |
| 573 | 572 |
Could not delete service/endpoint: &1&2&3&4 | The short text describes the object sufficiently | |
| 574 | 573 |
Could not find endpoint: name &1, namespace &2 | The short text describes the object sufficiently | |
| 575 | 574 |
Could not delete endpoint &1: RC=&2 | The short text describes the object sufficiently | |
| 576 | 575 |
Specified service name is already being used | The short text describes the object sufficiently | |
| 577 | 576 |
Specify a valid service name and/or endpoint name | The short text describes the object sufficiently | |
| 578 | 577 |
Specified endpoint name is already being used | The short text describes the object sufficiently | |
| 579 | 578 |
Error: &1&2&3&4 | The short text describes the object sufficiently | |
| 580 | 579 |
Error when reading property &1: &2&3&4 | The short text describes the object sufficiently | |
| 581 | 580 |
SRT Framework exception: &1&2&3&4 | The short text describes the object sufficiently | |
| 582 | 581 |
Design time view error. &1&2&3&4 | The short text describes the object sufficiently | |
| 583 | 582 |
Design time object &1 does not have any operations and is inconsistent | The short text describes the object sufficiently | |
| 584 | 583 |
Proxy class "&1" is not active | The short text describes the object sufficiently | |
| 585 | 584 |
System &3 is assigned to key &2; no allocation to key &1 possible | The short text describes the object sufficiently | |
| 586 | 585 |
Destination &3 is assigned to key &2; allocation to key &1 not possible | The short text describes the object sufficiently | |
| 587 | 586 |
UDDI query not possible. The target interface has not been specified | The short text describes the object sufficiently | |
| 588 | 587 |
UDDI query not possible. The provider system has not been specified | The short text describes the object sufficiently | |
| 589 | 588 |
UDDI error: &1&2&3&4 | The short text describes the object sufficiently | |
| 590 | 589 |
WSIL query not possible. The target interface has not been specified | The short text describes the object sufficiently | |
| 591 | 590 |
WSIL query not possible. The provider system has not been specified | The short text describes the object sufficiently | |
| 592 | 591 |
Cannot modify read-only instance of profile "&2", type "&1" | The short text describes the object sufficiently | |
| 593 | 592 |
Cannot modify read-only instance of destination "&2", type "&1" | The short text describes the object sufficiently | |
| 594 | 593 |
Cannot initialize read-only instance of destination "&2", type "&1" | The short text describes the object sufficiently | |
| 595 | 594 |
Profile "&2", version "&1" is not active | The short text describes the object sufficiently | |
| 596 | 595 |
Provider System "&2", type "&1" is not active | The short text describes the object sufficiently | |
| 597 | 596 |
No destination for system key "&1" | The short text describes the object sufficiently | |
| 598 | 597 |
No HTTP URL: &1&2&3&4 | The short text describes the object sufficiently | |
| 599 | 598 |
Error when parsing URL: &1&2&3&4 | The short text describes the object sufficiently | |
| 600 | 599 |
Error "&2&3&4" in WSIL access to system "&1" | The short text describes the object sufficiently | |
| 601 | 600 |
Unknown error in WSIL access to system "&1" | The short text describes the object sufficiently | |
| 602 | 601 |
HTTP destination and system key are both missing | The short text describes the object sufficiently | |
| 603 | 602 |
System maintenance not locked for processing | The short text describes the object sufficiently | |
| 604 | 603 |
Could not update system; invalid system key &1 | The short text describes the object sufficiently | |
| 605 | 604 |
Could not update system; invalid SLD system name &1 | The short text describes the object sufficiently | |
| 606 | 605 |
Could not update system; invalid business system name &1 | The short text describes the object sufficiently | |
| 607 | 606 |
No Provider System exists for system key "&1" | The short text describes the object sufficiently | |
| 608 | 607 |
System maintenance API is already locked by another instance | The short text describes the object sufficiently | |
| 609 | 608 |
Error in the lock administration for the system maintenance API | The short text describes the object sufficiently | |
| 610 | 609 |
Destination '&1' does not contain a system key | The short text describes the object sufficiently | |
| 611 | 610 |
No system exists for system key "&1" | The short text describes the object sufficiently | |
| 612 | 611 |
No system exists for SLD system name "&1" | The short text describes the object sufficiently | |
| 613 | 612 |
No system exists for business system name "&1" | The short text describes the object sufficiently | |
| 614 | 613 |
No system exists for destination "&1" | The short text describes the object sufficiently | |
| 615 | 614 |
SLD system name &1 is already assigned to system key &2 | The short text describes the object sufficiently | |
| 616 | 615 |
Business system name &1 is already assigned to system key &2 | The short text describes the object sufficiently | |
| 617 | 616 |
No system exists for application key "&1" | The short text describes the object sufficiently | |
| 618 | 617 |
Could not filter properties. &1&2&3&4 | The short text describes the object sufficiently | |
| 619 | 618 |
Binding '&1' activated in service '&2' | The short text describes the object sufficiently | |
| 620 | 619 |
Profile version "&1" is invalid | The short text describes the object sufficiently | |
| 621 | 620 |
Error in WSDL access: &1&2&3&4 | The short text describes the object sufficiently | |
| 622 | 621 |
Error in WSDL parsing: &1&2&3&4 | The short text describes the object sufficiently | |
| 623 | 622 |
Invalid port type name in WSDL: found=&1:&2; expected=&3:&4 | The short text describes the object sufficiently | |
| 624 | 623 |
WSDL does not have a valid endpoint | The short text describes the object sufficiently | |
| 625 | 624 |
WSDL does not have a valid port type | The short text describes the object sufficiently | |
| 626 | 625 |
WSDL does not have readable content | The short text describes the object sufficiently | |
| 627 | 626 |
No WSDL contexts exist | The short text describes the object sufficiently | |
| 628 | 627 |
Cannot determine web service destination without system key | The short text describes the object sufficiently | |
| 629 | 628 |
Existing WSDL contexts are invalid | The short text describes the object sufficiently | |
| 630 | 629 |
Default used due to different values: Property '&1' (NS: '&2') | The short text describes the object sufficiently | |
| 631 | 630 |
Error when executing a configuration task (worklist key: '&1') | The short text describes the object sufficiently | |
| 632 | 631 |
Configuration '&1' not found | The short text describes the object sufficiently | |
| 633 | 632 |
Could not merge HTTP and message authentication | The short text describes the object sufficiently | |
| 634 | 633 |
Local calls not permitted in outbound integration server | The short text describes the object sufficiently | |
| 635 | 634 |
Input missing or is incorrect for field '&1' | The short text describes the object sufficiently | |
| 636 | 635 |
WSDL document content missing | The short text describes the object sufficiently | |
| 637 | 636 |
The WSDL document is not compatible with proxy class "&1": "&2&3&4" | The short text describes the object sufficiently | |
| 638 | 637 |
Unknown WSIL type "&1" | The short text describes the object sufficiently | |
| 639 | 638 |
No binding generated by the WSDL document | The short text describes the object sufficiently | |
| 640 | 639 |
No ID found for feature '&1&2&3&4' | The short text describes the object sufficiently | |
| 641 | 640 |
No destination for system key '&1' | The short text describes the object sufficiently | |
| 642 | 641 |
Destination '&1' is not active | The short text describes the object sufficiently | |
| 643 | 642 |
Service group '&1' is not active | The short text describes the object sufficiently | |
| 644 | 643 |
No proxy interface for consumer interface "&1{&2}" | The short text describes the object sufficiently | |
| 645 | 644 |
Multiple proxy objects for consumer interface "&1{&2}" | The short text describes the object sufficiently | |
| 646 | 645 |
Invalid proxy class name "&1" for consumer interface "&2{&3}" | The short text describes the object sufficiently | |
| 647 | 646 |
Service group '&1' blocked by other object in memory | The short text describes the object sufficiently | |
| 648 | 647 |
Service group '&1' is not configured | The short text describes the object sufficiently | |
| 649 | 648 |
No logical port exists for service group '&1' | The short text describes the object sufficiently | |
| 650 | 649 |
No logical port for proxy class '&2' of service group '&1' | The short text describes the object sufficiently | |
| 651 | 650 |
Invalid SLD system name "&1" for system key "&2" | The short text describes the object sufficiently | |
| 652 | 651 |
Error in UDDI system query for system "&1": "&2&3&4" | The short text describes the object sufficiently | |
| 653 | 652 |
No data after UDDI system query for system "&1" (system key="&2) | The short text describes the object sufficiently | |
| 654 | 653 |
Invalid classification: Name="&1" Value "&2" | The short text describes the object sufficiently | |
| 655 | 654 |
Cannot persist until UDDI system query is successful | The short text describes the object sufficiently | |
| 656 | 655 |
Error in UDDI system query: "&1&2&3&4" | The short text describes the object sufficiently | |
| 657 | 656 |
Invalid SLD system name: "&1" | The short text describes the object sufficiently | |
| 658 | 657 |
Invalid business system name "&1" (service group "&2"; appl. key "&3") | The short text describes the object sufficiently | |
| 659 | 658 |
Invalid SLD system name "&1" (service group "&2"; appl. key "&3") | The short text describes the object sufficiently | |
| 660 | 659 |
Invalid proxy class "&1" in service group "&2" | The short text describes the object sufficiently | |
| 661 | 660 |
Invalid logical port name "&1" (proxy "&2"; service group "&3") | The short text describes the object sufficiently | |
| 662 | 661 |
Invalid method call for service group "&1" (see long text) | Space: object requires documentation | |
| 663 | 662 |
Port number '&1' invalid | The short text describes the object sufficiently | |
| 664 | 663 |
URL error: &1&2&3&4 | The short text describes the object sufficiently | |
| 665 | 664 |
J2EE host and/or port not specified; define them under 'System Settings' | The short text describes the object sufficiently | |
| 666 | 665 |
No WSIL URL in destination "&1" | The short text describes the object sufficiently | |
| 667 | 666 |
No URL parameters for registry "&1": "&2&3&4" | The short text describes the object sufficiently | |
| 668 | 667 |
Invalid URL parameter: Query host="&1" Host="&2" HTTP="&3" HTTPS="&4" | The short text describes the object sufficiently | |
| 669 | 668 |
Invalid URL parameter: Registry="&1" Host="&2" HTTP="&3" HTTPS="&4" | The short text describes the object sufficiently | |
| 670 | 669 |
Invalid URL parameter: Protocol="&1" Host="&2" Port="&3" | The short text describes the object sufficiently | |
| 671 | 670 |
Profile "&1" used: CFG request "&2" "&3" (SDef.: "&4") | The short text describes the object sufficiently | |
| 672 | 671 |
Provider System "&1" is used in Business Scenario "&2" State "&3" | The short text describes the object sufficiently | |
| 673 | 672 |
Error in user account query: "&1&2&3&4" | The short text describes the object sufficiently | |
| 674 | 673 |
&1 service(s) found in Services Registry:&2 | The short text describes the object sufficiently | |
| 675 | 674 |
Could not determine service using UDDI query | The short text describes the object sufficiently | |
| 676 | 675 |
&1 service entry/entries determined in UDDI registry | The short text describes the object sufficiently | |
| 677 | 676 |
&1 service(s) determined using WSIL query | The short text describes the object sufficiently | |
| 678 | 677 |
Could not determine service using WSIL query | The short text describes the object sufficiently | |
| 679 | 678 |
Error in WSIL query: "&1&2&3&4" | The short text describes the object sufficiently | |
| 680 | 679 |
&1 valid and &2 invalid WSDL document(s) parsed | The short text describes the object sufficiently | |
| 681 | 680 |
No valid WSDL documents found | The short text describes the object sufficiently | |
| 682 | 681 |
Error when generating configuration: "&1&2&3&4" | The short text describes the object sufficiently | |
| 683 | 682 |
&1 valid and &2 invalid configuration(s) created | The short text describes the object sufficiently | |
| 684 | 683 |
Could not create a valid configuration | The short text describes the object sufficiently | |
| 685 | 684 |
Invalid profile: Name="&1", version="&2", type ="&3" | The short text describes the object sufficiently | |
| 686 | 685 |
Error when initializing service group "&1": "&2&3&4" | The short text describes the object sufficiently | |
| 687 | 686 |
Error in initialization of proxy class "&1": "&2&3&4" | The short text describes the object sufficiently | |
| 688 | 687 |
Could not create configuration for proxy class "&1" | The short text describes the object sufficiently | |
| 689 | 688 |
Could not persist configuration for proxy class "&1" | The short text describes the object sufficiently | |
| 690 | 689 |
Error when cleaning up configuration for proxy class "&1" | The short text describes the object sufficiently | |
| 691 | 690 |
Cannot delete default request | The short text describes the object sufficiently | |
| 692 | 691 |
Configuration request not saved | The short text describes the object sufficiently | |
| 693 | 692 |
DT object '&1': Operation '&2' not found [NS: '&3'] | The short text describes the object sufficiently | |
| 694 | 693 |
Initialization error [registry/factory/RTC]: &1&2&3&4 | The short text describes the object sufficiently | |
| 695 | 694 |
Specify either an external or internal name, not both | The short text describes the object sufficiently | |
| 696 | 695 |
You cannot make changes to this end point with this interface | The short text describes the object sufficiently | |
| 697 | 696 |
Save to remove the default LP from configuration &1 (type &2) | The short text describes the object sufficiently | |
| 698 | 697 |
LP name already used; service '&1', binding '&2' | The short text describes the object sufficiently | |
| 699 | 698 |
Observer entry does not exist. &1&2&3&4 | The short text describes the object sufficiently | |
| 700 | 699 |
Observer entry exists more than once. &1&2&3&4 | The short text describes the object sufficiently | |
| 701 | 700 |
Observer entry written for binding key '&1' | The short text describes the object sufficiently | |
| 702 | 701 |
Observer entry removed for binding key '&1' | The short text describes the object sufficiently | |
| 703 | 702 |
Configuration reference not set for configuration '&1' | The short text describes the object sufficiently | |
| 704 | 703 |
No such global property '&1' ('&2') | The short text describes the object sufficiently | |
| 705 | 704 |
Cannot modify SRT number range '&1' (start '&2'). Client dependent: &3 | The short text describes the object sufficiently | |
| 706 | 705 |
Database table '&1': Operation '&2' failed | The short text describes the object sufficiently | |
| 707 | 706 |
Could not provide lock for DT integration (client '&1') | The short text describes the object sufficiently | |
| 708 | 707 |
Cannot lock central change directory | The short text describes the object sufficiently | |
| 709 | 708 |
Cannot lock central change directory (&1) | The short text describes the object sufficiently | |
| 710 | 709 |
WSIL URL is not a valid HTTP URL | The short text describes the object sufficiently | |
| 711 | 710 |
Design time objects of type '&1' can not be updated | The short text describes the object sufficiently | |
| 712 | 711 |
No runtime configurations found for this object | The short text describes the object sufficiently | |
| 713 | 712 |
Unknown operation (ID=&1) | The short text describes the object sufficiently | |
| 714 | 713 |
Deletion of configuration '&1': UDDI 'Hide' error &2&3&4 | The short text describes the object sufficiently | |
| 715 | 714 |
WSDL URL '&1' is not a valid HTTP URL | The short text describes the object sufficiently | |
| 716 | 715 |
Unknown design time object type '&1' | The short text describes the object sufficiently | |
| 717 | 716 |
Assignment '&1' (type '&2') updated | The short text describes the object sufficiently | |
| 718 | 717 |
Missing property value for '&1' ('&2') | The short text describes the object sufficiently | |
| 719 | 718 |
Initialization of proxy '&1' failed: &2&3&4 | The short text describes the object sufficiently | |
| 720 | 719 |
Internal error "&1&2&3&4" | The short text describes the object sufficiently | |
| 721 | 720 |
No Business Applications exist for system "&1" (system key "&2") | The short text describes the object sufficiently | |
| 722 | 721 |
No Business Application exists for Business Application Key "&1" | The short text describes the object sufficiently | |
| 723 | 722 |
No Business Application called "&1" exists | The short text describes the object sufficiently | |
| 724 | 723 |
No Business Application exists for Business Application ID "&1" | The short text describes the object sufficiently | |
| 725 | 724 |
No application update possible; invalid system key &1 | The short text describes the object sufficiently | |
| 726 | 725 |
No application update possible; invalid application key &1 | The short text describes the object sufficiently | |
| 727 | 726 |
No application update possible; invalid application name &1 | The short text describes the object sufficiently | |
| 728 | 727 |
No application update possible; invalid external ID &1 | The short text describes the object sufficiently | |
| 729 | 728 |
Business Application ID &1 already used by Application &2 in system &3 | The short text describes the object sufficiently | |
| 730 | 729 |
Business Application name &1 already used in system &2 | The short text describes the object sufficiently | |
| 731 | 730 |
Calling method &1->&2() | The short text describes the object sufficiently | |
| 732 | 731 |
Unknown instance type "&1" | The short text describes the object sufficiently | |
| 733 | 732 |
Invalid alternative host name "&1" for reverse proxy "&2" | The short text describes the object sufficiently | |
| 734 | 733 |
Invalid host name "&1" | The short text describes the object sufficiently | |
| 735 | 734 |
Invalid HTTP port "&1" | The short text describes the object sufficiently | |
| 736 | 735 |
Invalid HTTPS port "&1" | The short text describes the object sufficiently | |
| 737 | 736 |
Invalid reverse proxy name "&1" | The short text describes the object sufficiently | |
| 738 | 737 |
Invalid call of method &1 in class &2 for instance type &3 | The short text describes the object sufficiently | |
| 739 | 738 |
Invalid application name "&1" (service group "&2"; appl. key "&3") | The short text describes the object sufficiently | |
| 740 | 739 |
Invalid external name "&1" (service group "&2"; appl. key "&3") | The short text describes the object sufficiently | |
| 741 | 740 |
Error in WSDL handler (configuration key="&1"; endpoint key="&2") | The short text describes the object sufficiently | |
| 742 | 741 |
No endpoint (configuration key="&1"; endpoint key="&2"; endpoint ID "&3") | The short text describes the object sufficiently | |
| 743 | 742 |
No endpoint found (configuration key="&1", endpoint key "&2") | The short text describes the object sufficiently | |
| 744 | 743 |
Multiple endpoints found (configuration key="&1", endpoint key "&2") | The short text describes the object sufficiently | |
| 745 | 744 |
Invalid endpoint ID (configuration key="&1", endpoint ID "&2") | The short text describes the object sufficiently | |
| 746 | 745 |
Different endpoint namespaces not allowed in same WSDL | The short text describes the object sufficiently | |
| 747 | 746 |
No data for service definition, interface, service, or endpoint | The short text describes the object sufficiently | |
| 748 | 747 |
Configuration is not a server configuration (configuration key="&1") | The short text describes the object sufficiently | |
| 749 | 748 |
Configuration is not active (configuration key="&1") | The short text describes the object sufficiently | |
| 750 | 749 |
Error when calculating WSDL URL (configuration key="&1") | The short text describes the object sufficiently | |
| 751 | 750 |
Invalid endpoint ID "&1" | The short text describes the object sufficiently | |
| 752 | 751 |
Configuration key "&1" is invalid | The short text describes the object sufficiently | |
| 753 | 752 |
You cannot specify multiple configuration keys | The short text describes the object sufficiently | |
| 754 | 753 |
You cannot specify a service and an endpoint at the same time | The short text describes the object sufficiently | |
| 755 | 754 |
You cannot specify a service and a service definition at the same time | The short text describes the object sufficiently | |
| 756 | 755 |
You cannot specify a service and an interface at the same time | The short text describes the object sufficiently | |
| 757 | 756 |
Logical port '&1' for Process Integration (PI) deleted | The short text describes the object sufficiently | |
| 758 | 757 |
Logical port '&1' covered by PI; no details available | The short text describes the object sufficiently | |
| 759 | 758 |
Logical port '&1' activated for Process Integration (PI) | The short text describes the object sufficiently | |
| 760 | 759 |
Fallback LP cannot be modified | The short text describes the object sufficiently | |
| 761 | 760 |
Fallback logical port "&1" does not exist | The short text describes the object sufficiently | |
| 762 | 761 |
Task ('&2') exists for LP '&1'; no detailed display possible | The short text describes the object sufficiently | |
| 763 | 762 |
Could not read LP '&1'; assignment missing | The short text describes the object sufficiently | |
| 764 | 763 |
Could not read LP '&1'; no RTC data exists | The short text describes the object sufficiently | |
| 765 | 764 |
No assignment of service group "&1" to application key "&2" | The short text describes the object sufficiently | |
| 766 | 765 |
Application (key &1) is configured for use of XI protocol | The short text describes the object sufficiently | |
| 767 | 766 |
Fallback logical port not possible due to allocation to XI protocol | The short text describes the object sufficiently | |
| 768 | 767 |
XI logical ports not permitted as fallback | The short text describes the object sufficiently | |
| 769 | 768 |
Business system does not match | The short text describes the object sufficiently | |
| 770 | 769 |
Invalid proxy class "&1" | The short text describes the object sufficiently | |
| 771 | 770 |
Invalid service group "&1" | The short text describes the object sufficiently | |
| 772 | 771 |
Invalid business application ID "&1" | The short text describes the object sufficiently | |
| 773 | 772 |
Service group "&1" is not configured | The short text describes the object sufficiently | |
| 774 | 773 |
Service group "&1" is not configured for business application ID "&2" | The short text describes the object sufficiently | |
| 775 | 774 |
Service group "&1" is assigned to multiple applications | The short text describes the object sufficiently | |
| 776 | 775 |
No configuration for proxy class "&1" in service group "&2" | The short text describes the object sufficiently | |
| 777 | 776 |
Business Scenario "&1" already exists | The short text describes the object sufficiently | |
| 778 | 777 |
Cannot get RFC dest. for client &1 (see SAP Note 1043195) | The short text describes the object sufficiently | |
| 779 | 778 |
Could not instantiate proxy "&1" with logical port "&2" | The short text describes the object sufficiently | |
| 780 | 779 |
Error accessing routing protocol (proxy="&1"; LP="&2") | The short text describes the object sufficiently | |
| 781 | 780 |
Logical port '&1' is already assigned to proxy '&2' | The short text describes the object sufficiently | |
| 782 | 781 |
Logical Port name not set or invalid (valid characters are: &1) | The short text describes the object sufficiently | |
| 783 | 782 |
WSTASKCHECK: ID '&1' processed | The short text describes the object sufficiently | |
| 784 | 783 |
WSTASKCHECK: Could not process ID '&1' | The short text describes the object sufficiently | |
| 785 | 784 |
WSTASKCHECK: Job '&1' removed | The short text describes the object sufficiently | |
| 786 | 785 |
WSTASKCHECK: Job '&1' scheduled | The short text describes the object sufficiently | |
| 787 | 786 |
WSTASKCHECK: Error in task ID '&1'. &2&3&4 | The short text describes the object sufficiently | |
| 788 | 787 |
WSTASKCHECK: ID '&1' removed manually | The short text describes the object sufficiently | |
| 789 | 788 |
No task job currently exists [&1] | The short text describes the object sufficiently | |
| 790 | 789 |
Task job exists [&1] | The short text describes the object sufficiently | |
| 791 | 790 |
RFC destination get failed for client &1. &2&3&4 | The short text describes the object sufficiently | |
| 792 | 791 |
Destination '&1' [&2] is unusable. &3&4 | The short text describes the object sufficiently | |
| 793 | 792 |
Specified ID '&1' does not exist in '&2' | The short text describes the object sufficiently | |
| 794 | 793 |
Process is active in client '&1'; no change currently possible | The short text describes the object sufficiently | |
| 795 | 794 |
Database access error: Table &1', operation '&2' | The short text describes the object sufficiently | |
| 796 | 795 |
Number of Web service DT-to-RT comparisons selected: &1 | The short text describes the object sufficiently | |
| 797 | 796 |
Username/password has not been configured | The short text describes the object sufficiently | |
| 798 | 797 |
PSE for SSL X.509 certificate has not been configured | The short text describes the object sufficiently | |
| 799 | 798 |
PSE for WSSE X.509 certificate has not been configured | The short text describes the object sufficiently | |
| 800 | 799 |
Communication error: &1&2&3&4 | The short text describes the object sufficiently | |
| 801 | 800 |
User '&1' connected | The short text describes the object sufficiently | |
| 802 | 801 |
Unexpected message received | The short text describes the object sufficiently | |
| 803 | 802 |
Specified authentication method not supported by user type | The short text describes the object sufficiently | |
| 804 | 803 |
Caution: This program is only for internal use at SAP | Space: object requires documentation | |
| 805 | 804 |
RFC destination '&1' read successfully | The short text describes the object sufficiently | |
| 806 | 805 |
Error when processing changes: &1&2&3&4 | The short text describes the object sufficiently | |
| 807 | 806 |
Error in call of RFC destination '&1' (client'&2'): &3&4 | The short text describes the object sufficiently | |
| 808 | 807 |
There is no selectable service | The short text describes the object sufficiently | |
| 809 | 808 |
Service name is not valid | The short text describes the object sufficiently | |
| 810 | 809 |
Endpoint name is not valid | The short text describes the object sufficiently | |
| 811 | 810 |
Service '&1' not found | The short text describes the object sufficiently | |
| 812 | 811 |
Invalid assignment type '&2' for assignment '&1' | The short text describes the object sufficiently | |
| 813 | 812 |
Failed to read details: &1&2&3&4 | The short text describes the object sufficiently | |
| 814 | 813 |
Failed to get ICF alias: &1&2&3&4 | The short text describes the object sufficiently | |
| 815 | 814 |
Failed to get ICF service: &1&2&3&4 | The short text describes the object sufficiently | |
| 816 | 815 |
Can not execute operation! Parallel process is triggered by user '&1' | The short text describes the object sufficiently | |
| 817 | 816 |
Provider configuration(s) successfully deleted | The short text describes the object sufficiently | |
| 818 | 817 |
Consumer configuration(s) successfully deleted | The short text describes the object sufficiently | |
| 819 | 818 |
No configuration selected: Nothing done | The short text describes the object sufficiently | |
| 820 | 819 |
Provider configuration(s) successfully migrated | The short text describes the object sufficiently | |
| 821 | 820 |
Consumer configuration(s) successfully migrated | The short text describes the object sufficiently | |
| 822 | 821 |
Configuration was removed: No details available. See history log | The short text describes the object sufficiently | |
| 823 | 822 |
Can not access ICF details | The short text describes the object sufficiently | |
| 824 | 823 |
History information removed. Application log entry written. | The short text describes the object sufficiently | |
| 825 | 824 |
Entry already migrated. Use transaction SOAMANAGER to view details | The short text describes the object sufficiently | |
| 826 | 825 |
Wrong authentication data! (Error '&1') | The short text describes the object sufficiently | |
| 827 | 826 |
Missing authorizations! (Error '&1') | The short text describes the object sufficiently | |
| 828 | 827 |
The password for user '&1' might be set wrong in XI Directory! | The short text describes the object sufficiently | |
| 829 | 828 |
Also the user '&1' might be locked or missing on the receiver! | The short text describes the object sufficiently | |
| 830 | 829 |
Probably trust has not been established between IS and receiver! | The short text describes the object sufficiently | |
| 831 | 830 |
User '&1' does not have enough permissions to retrieve the wsdl. | The short text describes the object sufficiently | |
| 832 | 831 |
File is empty: &1&2&3&4 | The short text describes the object sufficiently | |
| 833 | 832 |
File successfully uploaded: &1&2&3&4 | The short text describes the object sufficiently | |
| 834 | 833 |
Failed to upload file: &1&2&3&4 | The short text describes the object sufficiently | |
| 835 | 834 |
Security Token Service has not been configured on the provider system | The short text describes the object sufficiently | |
| 836 | 835 |
Security Token Service is not configured for basic authentication | The short text describes the object sufficiently | |
| 837 | 836 |
Security Token Service is not configured for sso authentication | The short text describes the object sufficiently | |
| 838 | 837 |
Security Token Service is not configured for https authentication | The short text describes the object sufficiently | |
| 839 | 838 |
Security Token Service is not configured for user token authentication | The short text describes the object sufficiently | |
| 840 | 839 |
Security Token Service is not configured for saml authentication | The short text describes the object sufficiently | |
| 841 | 840 |
Security Token Service is not configured for wsse x509 authentication | The short text describes the object sufficiently | |
| 842 | 841 |
Connection test to service registry '&1' is successful | The short text describes the object sufficiently | |
| 843 | 842 |
Connection test to WSIL service is successful | The short text describes the object sufficiently | |
| 844 | 843 |
Connection test to service registry '&1' is not successful | The short text describes the object sufficiently | |
| 845 | 844 |
Start configuration of service group '&1' | The short text describes the object sufficiently | |
| 846 | 845 |
Configuration of service group '&1' complete | The short text describes the object sufficiently | |
| 847 | 846 |
Configuration of service group '&1' failed | The short text describes the object sufficiently | |
| 848 | 847 |
Start configuration of proxy '&1' | The short text describes the object sufficiently | |
| 849 | 848 |
Configuration of proxy '&1' complete | The short text describes the object sufficiently | |
| 850 | 849 |
Configuration of proxy '&1' failed | The short text describes the object sufficiently | |
| 851 | 850 |
Try to create a logical port using Service Registry | The short text describes the object sufficiently | |
| 852 | 851 |
Failed to create a logical port using Service Registry. | The short text describes the object sufficiently | |
| 853 | 852 |
Successfully created a logical port using Service Registry. | The short text describes the object sufficiently | |
| 854 | 853 |
Try to create a logical port using WSIL | The short text describes the object sufficiently | |
| 855 | 854 |
Failed to create a logical port using WSIL | The short text describes the object sufficiently | |
| 856 | 855 |
Successfully created a logical port using WSIL | The short text describes the object sufficiently | |
| 857 | 856 |
WSIL is not configured in the system connection | The short text describes the object sufficiently | |
| 858 | 857 |
Assigned inbound interface '&1' '&2' | The short text describes the object sufficiently | |
| 859 | 858 |
Successfully created a logical port for inbound interface '&1' '&2' | The short text describes the object sufficiently | |
| 860 | 859 |
Failed to create a logical port for inbound interface '&1' '&2' | The short text describes the object sufficiently | |
| 861 | 860 |
Use profile name = '&1' version = '&2' type = '&3' | The short text describes the object sufficiently | |
| 862 | 861 |
Check content of WSDL &1&2&3&4 | The short text describes the object sufficiently | |
| 863 | 862 |
WSDL &1&2&3&4 contains the same profile name and version | The short text describes the object sufficiently | |
| 864 | 863 |
WSDL &1&2&3&4 contains the same profile name but different version | The short text describes the object sufficiently | |
| 865 | 864 |
WSDL &1&2&3&4 contains different profile name | The short text describes the object sufficiently | |
| 866 | 865 |
&1 WSDLs were successfully retrieved | The short text describes the object sufficiently | |
| 867 | 866 |
None of the WSDL URLs can be rerieved successfully | The short text describes the object sufficiently | |
| 868 | 867 |
Try to create logical ports by WSDL &1&2&3&4 | The short text describes the object sufficiently | |
| 869 | 868 |
&1 logical ports were created by WSDL &2&3&4 | The short text describes the object sufficiently | |
| 870 | 869 |
No user account was assigned for business application &1/&2 | The short text describes the object sufficiently | |
| 871 | 870 |
User account &1 is assigned | The short text describes the object sufficiently | |
| 872 | 871 |
User account &1 and the profile &2 version &3 do not match | The short text describes the object sufficiently | |
| 873 | 872 |
They support different sets of authentication methods | The short text describes the object sufficiently | |
| 874 | 873 |
Target WSIL type &1 | The short text describes the object sufficiently | |
| 875 | 874 |
Delete configuration of service group '&1' | The short text describes the object sufficiently | |
| 876 | 875 |
Deletion of configuration for service group '&1' finished | The short text describes the object sufficiently | |
| 877 | 876 |
Deletion of configuration for service group '&1' failed | The short text describes the object sufficiently | |
| 878 | 877 |
Proxy '&1' is assigned to fallback logical port '&2' | The short text describes the object sufficiently | |
| 879 | 878 |
Start deletion of logical port for proxy '&1' and application &2/&3 | The short text describes the object sufficiently | |
| 880 | 879 |
Logical port for proxy '&1' and application &2/&3 deleted | The short text describes the object sufficiently | |
| 881 | 880 |
Deletion of logical port for proxy '&1' and application &2/&3 failed | The short text describes the object sufficiently | |
| 882 | 881 |
Delete configuration of service definition '&1' | The short text describes the object sufficiently | |
| 883 | 882 |
Configuration of service definition '&1' deleted | The short text describes the object sufficiently | |
| 884 | 883 |
Deletion of configuration for service definition '&1' failed | The short text describes the object sufficiently | |
| 885 | 884 |
Create configuration of service definition '&1' | The short text describes the object sufficiently | |
| 886 | 885 |
Configuration of service definition '&1' created | The short text describes the object sufficiently | |
| 887 | 886 |
Creation of configuration for service definition '&1' failed | The short text describes the object sufficiently | |
| 888 | 887 |
No valid binding could be created | The short text describes the object sufficiently | |
| 889 | 888 |
Profile doesn't match the designtime settings of the service | The short text describes the object sufficiently | |
| 890 | 889 |
Could not set value for obligatory configuration property &1 | The short text describes the object sufficiently | |
| 891 | 890 |
Try to create endpoint with &1&2&3&4 | The short text describes the object sufficiently | |
| 892 | 891 |
Successfully created endpoint with &1&2&3&4 | The short text describes the object sufficiently | |
| 893 | 892 |
Message "&1{&2}" not supported (interface: "&3" binding key: "&4") | Space: object requires documentation | |
| 894 | 893 |
Invalid URL "&1" for the Secure Token Service | Space: object requires documentation | |
| 895 | 894 |
No Logical Port for this Secure Token Service URL: "&1" | Space: object requires documentation | |
| 896 | 895 |
XI-Protocol not allowed for Secure Token Service Requests.(LP=&1 URL=&2) | Space: object requires documentation | |
| 897 | 896 |
Error while creating SOAP Application for STS Request.(LP=&1 URL=&2) | Space: object requires documentation | |
| 898 | 897 |
This is an STS proxy. The access URL is already assiged in LP '&1'. | The short text describes the object sufficiently | |
| 899 | 898 |
SOAP version is only allowed for endpoint WSDLs | The short text describes the object sufficiently | |
| 900 | 899 |
Feature "&1" already defined | The short text describes the object sufficiently | |
| 901 | 900 |
Property "&1{&2}" already defined | The short text describes the object sufficiently | |
| 902 | 901 |
Value "&1" for property "&2{&3}" is already defined | The short text describes the object sufficiently | |
| 903 | 902 |
Definition of feature "&1" is invalid | The short text describes the object sufficiently | |
| 904 | 903 |
Definition of property "&1{&2}" is invalid | The short text describes the object sufficiently | |
| 905 | 904 |
Definition of value "&1" property "&2{&3}" is invalid | The short text describes the object sufficiently | |
| 906 | 905 |
Feature "&2" of property "&1{&2}" is undefined | The short text describes the object sufficiently | |
| 907 | 906 |
Property "&2{&3}" of value "&1" is undefined | The short text describes the object sufficiently | |
| 908 | 907 |
Data saved | The short text describes the object sufficiently | |
| 909 | 908 |
Data successfully deleted | The short text describes the object sufficiently | |
| 910 | 909 |
Data successfully (re-) read | The short text describes the object sufficiently | |
| 911 | 910 |
&1 entries found! | The short text describes the object sufficiently | |
| 912 | 911 |
Changed configurations: &1 [&2 change(s), &3 deletion(s), &4 failure(s)] | The short text describes the object sufficiently | |
| 913 | 912 |
At least one authentication method must be selected | The short text describes the object sufficiently | |
| 914 | 913 |
You must check in addition the configuration checkbox | The short text describes the object sufficiently | |
| 915 | 914 |
Auth. settings w/o configuration selection get ignored or deleted | The short text describes the object sufficiently | |
| 916 | 915 |
SOAP Version "&1" not supported | The short text describes the object sufficiently | |
| 917 | 916 |
Simple client provider entry is missing | The short text describes the object sufficiently | |
| 918 | 917 |
Multiple simple client provider entries found (number: &1) | The short text describes the object sufficiently | |
| 919 | 918 |
No simple client provider information is set | The short text describes the object sufficiently | |
| 920 | 919 |
On simple client provider configurations only one binding is allowed | The short text describes the object sufficiently | |
| 921 | 920 |
Service Definition "&1" does not exist | The short text describes the object sufficiently | |
| 922 | 921 |
Design Time security settings violated. Runtime settings reverted | The short text describes the object sufficiently | |
| 923 | 922 |
No HTTPS protocol maintained on this server. X.509 auth. may not work! | The short text describes the object sufficiently | |
| 924 | 923 |
Load failures for simple client providers: &1 | The short text describes the object sufficiently | |
| 925 | 924 |
Invalid simple client provider call | The short text describes the object sufficiently | |
| 926 | 925 |
Error retrieving mex data from server | The short text describes the object sufficiently | |
| 927 | 926 |
Mex client not usable for proxy class &1 | The short text describes the object sufficiently | |
| 928 | 927 |
Error parsing metadata fragment with dialect &1 | The short text describes the object sufficiently | |
| 929 | 928 |
Endpoint &1 for service definition &2 is inactive | The short text describes the object sufficiently | |
| 930 | 929 |
Endpoint &1 for service definition &2 doesn't exist | The short text describes the object sufficiently | |
| 931 | 930 |
Logical port &1 for client proxy &2 is inactive | The short text describes the object sufficiently | |
| 932 | 931 |
Logical port &1 for client proxy &2 doesn't exist | The short text describes the object sufficiently | |
| 933 | 932 |
Endpoint &1 for service definition &2 is not adjusted for local call | The short text describes the object sufficiently | |
| 934 | 933 |
Logical port &1 for client proxy &2 is not adjusted for local call | The short text describes the object sufficiently | |
| 935 | 934 |
Access to the A1S factory denied | The short text describes the object sufficiently | |
| 936 | 935 |
No System Connections maintained in the System | The short text describes the object sufficiently | |
| 937 | 936 |
Unknown Service Group &1 | The short text describes the object sufficiently | |
| 938 | 937 |
No Technical Receiver maintained for Service Group &1 | The short text describes the object sufficiently | |
| 939 | 938 |
No Logical Receiver maintained for Service Group &1 | The short text describes the object sufficiently | |
| 940 | 939 |
No Logical Receiver structure maintained for Service Group &1 | The short text describes the object sufficiently | |
| 941 | 940 |
Data does not match with structure &1 stored with Service Group &2 | The short text describes the object sufficiently | |
| 942 | 941 |
Error parsing data | The short text describes the object sufficiently | |
| 943 | 942 |
No fields found as part of data coming as input for Service Group &1 | The short text describes the object sufficiently | |
| 944 | 943 |
No active routing maintained for Service Group &1 | The short text describes the object sufficiently | |
| 945 | 944 |
Multiple Receivers not allowed for Service Group &1 | The short text describes the object sufficiently | |
| 946 | 945 |
No Technical Receiver found for Business System: &1 and Application: &2 | The short text describes the object sufficiently | |
| 947 | 946 |
System Key &1 and Application Key &2 does not exist in system connections | The short text describes the object sufficiently | |
| 948 | 947 |
URL access path of &1 not identical to service definition access URL | The short text describes the object sufficiently | |
| 949 | 948 |
Access URL of service definition &1 is inaccessible | The short text describes the object sufficiently | |
| 950 | 949 |
Metadata cache successfully cleared | The short text describes the object sufficiently | |
| 951 | 950 |
Runtime cache successfully cleared | The short text describes the object sufficiently | |
| 952 | 951 |
Internal error. Data of object is inconsistent | The short text describes the object sufficiently | |
| 953 | 952 |
Web service ping failed (RC=&1). &2&3&4 | The short text describes the object sufficiently | |
| 954 | 953 |
Web service ping successful for LP '&1', proxy '&2' | The short text describes the object sufficiently | |
| 955 | 954 |
PI Integration Server ping successful for LP '&1', proxy '&2' | The short text describes the object sufficiently | |
| 956 | 955 |
Error retrieving sidl instance with the help of mex fragments | The short text describes the object sufficiently | |
| 957 | 956 |
The property &1 in XIDIR does not match to the target wsdl settings | The short text describes the object sufficiently | |
| 958 | 957 |
No service definition found interface '&1' | The short text describes the object sufficiently | |
| 959 | 958 |
More than one service definition for interface '&1' | The short text describes the object sufficiently | |
| 960 | 959 |
Specified URL is invalid. &1 | The short text describes the object sufficiently | |
| 961 | 960 |
STS proxy has already LP &1 with the given STS-URL &2 | The short text describes the object sufficiently | |
| 962 | 961 |
This STS proxy is still in use by other LPs (&1). | The short text describes the object sufficiently | |
| 963 | 962 |
Invalid use case '&1' for WSDL Analyzer Context | The short text describes the object sufficiently | |
| 964 | 963 |
No appropriate binding evaluated for endpoint URL "&1" | The short text describes the object sufficiently | |
| 965 | 964 |
No appropriate binding evaluated | The short text describes the object sufficiently | |
| 966 | 965 |
Service Group '&1' does not allow multiple receiver assignments | The short text describes the object sufficiently | |
| 967 | 966 |
No LP exists for STS: &1&2. Create LP via MEX: &3&4 (OSS note 1319507) | Space: object requires documentation | |
| 968 | 967 |
STS URL and MEX-URL are missing | The short text describes the object sufficiently | |
| 969 | 968 |
Secure Token URL is missing | The short text describes the object sufficiently | |
| 970 | 969 |
MEX URL is missing | The short text describes the object sufficiently | |
| 971 | 970 |
STS-Support required, but not enabled. Read OSS note 1320198. | The short text describes the object sufficiently | |
| 972 | 971 |
STS-Support is already enabled. | The short text describes the object sufficiently | |
| 973 | 972 |
STS-Support successfully enabled. | The short text describes the object sufficiently | |
| 974 | 973 |
Invalid authentication level specified. Design Time object is invalid. &1 | The short text describes the object sufficiently | |
| 975 | 974 |
DT-RT incompatibility: DT auth. level '&1', RT auth. method '&2' too weak | The short text describes the object sufficiently | |
| 976 | 975 |
&1&2&3&4 | The short text describes the object sufficiently | |
| 977 | 976 |
Invalid name for domain "&1" | The short text describes the object sufficiently | |
| 978 | 977 |
No LP of default STS. Create it for consumer proxy &1. | The short text describes the object sufficiently | |
| 979 | 978 |
You must not use defaults and specify an auth method at the same time. | The short text describes the object sufficiently | |
| 980 | 979 |
Domain "&1" has not yet been saved | The short text describes the object sufficiently | |
| 981 | 980 |
Cannot activate domain systems for inactive domain "&1" | The short text describes the object sufficiently | |
| 982 | 981 |
Profile type "Template" is not allowed in this system | The short text describes the object sufficiently | |
| 983 | 982 |
No metadata for Connectivity Type "&1" | The short text describes the object sufficiently | |
| 984 | 983 |
System connection type "Template" is not allowed in this system | The short text describes the object sufficiently | |
| 985 | 984 |
Unknown Connectivity Types "&1". | The short text describes the object sufficiently | |
| 986 | 985 |
Invalid scope "&1" for common property "&3{&2}" | The short text describes the object sufficiently | |
| 987 | 986 |
Invalid scope "&1" for connectivity type specific property "&3{&2}" | The short text describes the object sufficiently | |
| 988 | 987 |
Cannot create domain "&1" | The short text describes the object sufficiently | |
| 989 | 988 |
Configuration request type "Central" is not allowed in this system | The short text describes the object sufficiently | |
| 990 | 989 |
Subject "&1{&2}" of Type "&3" does not exist in this context. | The short text describes the object sufficiently | |
| 991 | 990 |
Error while reading from proxy "&1" in shortcut scenario (LP="&2"). | The short text describes the object sufficiently | |
| 992 | 991 |
Error while reading service definition &1 in shortcut scenario (URL=&2). | The short text describes the object sufficiently | |
| 993 | 992 |
Designtime cache successfully cleared | The short text describes the object sufficiently | |
| 994 | 993 |
Error while reading from Logical Port &1 in shortcut scenario (URL=&2). | The short text describes the object sufficiently | |
| 995 | 994 |
Proxy Definition '&1' and Service Def '&2' are compatible in local system | The short text describes the object sufficiently | |
| 996 | 995 |
Object type '&1' with name '&2' does not exist | The short text describes the object sufficiently | |
| 997 | 996 |
Shortcut connection already exists. Proxy=&1, LP=&2, Service=&3. | The short text describes the object sufficiently | |
| 998 | 997 |
Invalid operation in multi tenant environment! | The short text describes the object sufficiently | |
| 999 | 998 |
Logical port '&1' activated for local shortcut | The short text describes the object sufficiently | |
| 1,000 | 999 |
Logical port '&1' is local shortcut; no details available | The short text describes the object sufficiently |
History
| Last changed on/by | |
20131127 | SAP |
| SAP Release Created in | 700 |
