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