| SRT_WSP406 |
Invalid value "&1" for transport protocol of WSDL request |
| SRT_WSP407 |
Could not determine name for service definition |
| SRT_WSP408 |
Cannot determine web service URL |
| SRT_WSP409 |
Agreement found in unexpected position |
| SRT_WSP410 |
You cannot specify more than one service definition |
| SRT_WSP411 |
You cannot specify more than one binding key |
| SRT_WSP412 |
You cannot specify an agreement for this WSDL section |
| SRT_WSP413 |
Serious error; could not create GUID |
| SRT_WSP414 |
Invalid framework ID: "&1" |
| SRT_WSP415 |
Invalid access of framework "&1" to objects of framework "&2" |
| SRT_WSP416 |
Undefined configuration status "&1" |
| SRT_WSP417 |
No data after RTC conversion |
| SRT_WSP418 |
Invalid binding: ID = "&1", KEY = "&2" |
| SRT_WSP419 |
Different number of binding nodes and binding keys |
| SRT_WSP420 |
Passed and found binding keys are different |
| SRT_WSP421 |
No data for configuration key "&1" in database |
| SRT_WSP422 |
Empty context table for configuration key "&1" |
| SRT_WSP423 |
No binding name for binding ID "&1" in configuration "&2" |
| SRT_WSP424 |
UDDI publishing of configuration &1 failed: &2 |
| SRT_WSP425 |
UDDI unpublishing of configuration &1 failed: &2 |
| SRT_WSP426 |
Binding "&1" is not part of a server configuration |
| SRT_WSP427 |
Call URL for binding &1 exists only if configuration is active |
| SRT_WSP428 |
WSDL URLs for binding &1 exist only if configuration is active |
| SRT_WSP429 |
SIDL generation possible only if configuration is active |
| SRT_WSP430 |
WSDL generation possible only if configuration is active |
| SRT_WSP431 |
No configuration for local ICF path "&1" |
| SRT_WSP432 |
Initial binding key for local ICF path "&1" |
| SRT_WSP433 |
No data for binding key "&1" |
| SRT_WSP434 |
Cannot delete default profile |
| SRT_WSP435 |
No binding data for configuration key: "&1" |
| SRT_WSP436 |
Error in initialization of SOAP application: "&1" |
| SRT_WSP437 |
Invalid character "&2" in SOAP application name "&1" |
| SRT_WSP438 |
Invalid blanks in SOAP application name "&1" |
| SRT_WSP439 |
Error when parsing WSDL |
| SRT_WSP440 |
No data for binding "&1:&2" in subject table |
| SRT_WSP441 |
IIF &1 (channel &2) does not have an endpoint |
| SRT_WSP442 |
Configuration destination "&1" does not exist |
| SRT_WSP443 |
Assignment &1 (type &2): Generic client &3 does not have an endpoint |
| SRT_WSP444 |
Could not open job &1; RC = &2 |
| SRT_WSP445 |
Could not start job &1; RC = &2 |
| SRT_WSP446 |
Could not save job &1; RC = &2 |
| SRT_WSP447 |
Could not save task. (&1, &2). ID=&3 |
| SRT_WSP448 |
Current call stack has no authorization for this action |
| SRT_WSP449 |
Invalid interface namespace "&1" |
| SRT_WSP450 |
You cannot specify more than one interface namespace |
| SRT_WSP451 |
Invalid interface name "&1" |
| SRT_WSP452 |
You cannot specify more than one interface name |
| SRT_WSP453 |
Interface name not specified |
| SRT_WSP454 |
Channel found in an unexpected position |
| SRT_WSP455 |
Channel "&1" is invalid |
| SRT_WSP456 |
No channel specified |
| SRT_WSP457 |
You cannot specify a service definition and an interface at the same time |
| SRT_WSP458 |
You cannot specify an interface and a binding at the same time |
| SRT_WSP459 |
Invalid WSDL section "&1" when interface and channel specified |
| SRT_WSP460 |
Interface name found in an unexpected position |
| SRT_WSP461 |
IIF &1 (channel &2): No ESR reference |
| SRT_WSP462 |
IIF &1 (channel &2): No service definition exists |
| SRT_WSP463 |
IIF &1 (channel &2): No unique service definition (number: &3) |
| SRT_WSP464 |
IIF &1 (channel &2): No unique configuration (number: &3) |
| SRT_WSP465 |
IIF &1 (channel &2): No unique binding (number: &3) |
| SRT_WSP466 |
IIF &1 (channel &2): Binding '&3' has no binding name |
| SRT_WSP467 |
No changes possible; object opened in client-specific mode |
| SRT_WSP468 |
IIF &1 (channel &2) invalid: &3&4 |
| SRT_WSP469 |
Configuration &1 does not have a binding |
| SRT_WSP470 |
Transport protocol missing in configuration "&1" |
| SRT_WSP471 |
Host name missing in configuration "&1" |
| SRT_WSP472 |
Invalid URL path "&1" in configuration "&2" |
| SRT_WSP473 |
Missing URL path in configuration "&1" |
| SRT_WSP474 |
Invalid host name "&1" in configuration "&2" |
| SRT_WSP475 |
Invalid URL port "&1" in configuration "&2" |
| SRT_WSP476 |
URL port missing in configuration "&1" |
| SRT_WSP477 |
Binding type missing in configuration "&1" |
| SRT_WSP478 |
User interaction error |
| SRT_WSP479 |
Error: &1&2&3&4 |
| SRT_WSP480 |
Could not delete job &1; RC=&2 |
| SRT_WSP481 |
Error in WSDL access (destination &1). &2&3&4 |
| SRT_WSP482 |
Job '&1' deleted |
| SRT_WSP483 |
Job '&1' already exists and does not need to be scheduled |
| SRT_WSP484 |
Job '&1' scheduled |
| SRT_WSP485 |
Error when creating instance of assignment query interface |
| SRT_WSP486 |
Serialization error in serializer: &1 |
| SRT_WSP487 |
Serialization error: &1 |
| SRT_WSP488 |
Error when creating instance of URL handler |
| SRT_WSP489 |
Access URL not set or cannot be determined |
| SRT_WSP490 |
Could not read property '&1' ('&2') |
| SRT_WSP491 |
Assignment missing; configuration: '&1' ('&2'); DT object: '&3' |
| SRT_WSP492 |
Logical port '&1' not locked |
| SRT_WSP493 |
Authentication method for logical port '&1' is unknown |
| SRT_WSP494 |
No WSDL: '&1' |
| SRT_WSP495 |
Assignment '&1' (type '&2') saved (configurations: &3) |
| SRT_WSP496 |
Assignment '&1' (type '&2') activated (configurations: &3) |
| SRT_WSP497 |
Assignment '&1' (type '&2') deleted (configurations: &3) |
| SRT_WSP498 |
Assignment '&1' (type '&2') removed |
| SRT_WSP499 |
Assignment '&1' (type '&2') deactivated (configurations: &3) |
| SRT_WSP500 |
WSDL URL generation: Property '&1' is missing (NS: '&2') |
| SRT_WSP501 |
ESR P2P client assignment '&1' (type '&2'): DT object '&3' |
| SRT_WSP502 |
ESR P2P server assignment '&1' (type '&2'): DT object '&3' |
| SRT_WSP503 |
ESR IS client assignment '&1' (type '&2'): Channel '&3', IF '&4' |
| SRT_WSP504 |
ESR IS server assignment '&1' (type '&2'): DT object '&3' |
| SRT_WSP505 |
Unknown error in WSDL generation |