| SRT_WSP049 |
Configuration type "&1" is invalid |
| SRT_WSP050 |
Profile cannot be modified |
| SRT_WSP051 |
ICF: &1&2&3&4 |
| SRT_WSP052 |
HTTP: &1&2&3&4 |
| SRT_WSP053 |
Maximum one binding allowed for simple client providers |
| SRT_WSP054 |
Configuration type &1 is invalid |
| SRT_WSP055 |
Profile type &1 is invalid |
| SRT_WSP056 |
Profile has not yet been saved |
| SRT_WSP057 |
Profile is invalid |
| SRT_WSP058 |
Profile "&1" is not active |
| SRT_WSP059 |
Error when deleting service node |
| SRT_WSP060 |
Maximum of one service node permitted in configuration |
| SRT_WSP061 |
At least one service node required for configuration |
| SRT_WSP062 |
No variant assigned to binding &1 |
| SRT_WSP063 |
Specified subjects have different types |
| SRT_WSP064 |
Source object and target object are identical |
| SRT_WSP065 |
Error when reading service definition "&1": &2 |
| SRT_WSP066 |
Parameter &1 has an invalid value in the current context: &2 |
| SRT_WSP067 |
Binding &1 has an empty property list structure |
| SRT_WSP068 |
Error when deleting ICF entities: &1&2&3&4 |
| SRT_WSP069 |
Error when deleting HTTP entities: &1&2&3&4 |
| SRT_WSP070 |
Feature name "&1" is unknown |
| SRT_WSP071 |
Feature class "&1" not initialized |
| SRT_WSP072 |
Could not instantiate serialization class "&1" |
| SRT_WSP073 |
Error when creating SIDL interface for object '&1': '&2' |
| SRT_WSP074 |
Error when initializing Feature Factory |
| SRT_WSP075 |
No WSDL root element specified |
| SRT_WSP076 |
Only one WSDL root element permitted |
| SRT_WSP077 |
WSDL root element does not belong to this configuration |
| SRT_WSP078 |
Invalid subject type for WSDL root element |
| SRT_WSP079 |
No WSDL root element set |
| SRT_WSP080 |
"&1" cannot be used as a name for SOAP applications |
| SRT_WSP081 |
Status "&1" not valid for SOAP applications |
| SRT_WSP082 |
SOAP application "&1" does not exist |
| SRT_WSP083 |
Name "&1" is not valid for SOAP applications |
| SRT_WSP084 |
At least one semantic description must exist |
| SRT_WSP085 |
Error when determining language: "&1" |
| SRT_WSP086 |
Semantic description "&1" is invalid |
| SRT_WSP087 |
Invalid default value '&1' for property '&2:&3' |
| SRT_WSP088 |
Feature '&1' does not have a property called '&2' |
| SRT_WSP089 |
Instantiation error in Feature Factory |
| SRT_WSP090 |
SOAP application "&1" is not active |
| SRT_WSP091 |
Assignment &1 (type &2) already assigned to profile &3 (type &4) |
| SRT_WSP092 |
No profile specified for assignment &1 (type &2) |
| SRT_WSP093 |
Profile &1 (type &2) is not active |
| SRT_WSP094 |
Cannot delete assignment &1 (type &2) |
| SRT_WSP095 |
Error when saving assignment &1 (type &2) |
| SRT_WSP096 |
Assignment &1 (type &2) is initial |
| SRT_WSP097 |
Hash calculation for assignment &1 (type &2) failed |
| SRT_WSP098 |
Could not activate assignment &1 (type &2) |
| SRT_WSP099 |
Preconfiguration is invalid |
| SRT_WSP100 |
Invalid subject type "&1" for this preconfiguration |
| SRT_WSP101 |
Profile type &1 cannot be mapped to an assignment type |
| SRT_WSP102 |
Non-fulfilled dependencies within property list |
| SRT_WSP103 |
Property '&1:&2' with value '&3' is invalid |
| SRT_WSP104 |
Assignment &1 (type &2) cannot be modified |
| SRT_WSP105 |
Profile type &1 cannot be mapped to a configuration type |
| SRT_WSP106 |
Profile &1 with type &2 has multiple service entries |
| SRT_WSP107 |
Invalid combination of parameters in assignment &1 (type &2) |
| SRT_WSP108 |
Cannot determine namespace for object &1 |
| SRT_WSP109 |
Assignment &1 not activated; error in configuration |
| SRT_WSP110 |
Property '&1:&2' is not valid in this property list |
| SRT_WSP111 |
No default value available for property "&1:&2" |
| SRT_WSP112 |
No default URL available for property "&1:&2" |
| SRT_WSP113 |
Cannot cancel changes for assignment &1 and &2 |
| SRT_WSP114 |
Could not modify assignment &1 for profile change |
| SRT_WSP115 |
Assignment &1 of type &2 is not yet saved |
| SRT_WSP116 |
Error when deleting assignment for object &1, &2, and binding &3 |
| SRT_WSP117 |
Cannot copy configuration; invalid name &1 |
| SRT_WSP118 |
Name and/or type of assignment is not specified |
| SRT_WSP119 |
Invalid variants and binding information in configuration &1 |
| SRT_WSP120 |
Invalid assignment type '&1' specified |
| SRT_WSP121 |
Cannot use profile type &1 for assignment type &2 |
| SRT_WSP122 |
Could not activate configuration &1 with type &2 |
| SRT_WSP123 |
Specified profile &1:&2 not the same as saved &3:&4 profile |
| SRT_WSP124 |
Assignment for &1:&2 is invalid; &3 |
| SRT_WSP125 |
Binding &3 in configuration &1:&2; object &4 cannot be deleted |
| SRT_WSP126 |
End point '&1' is not valid for SOAP applications |
| SRT_WSP127 |
No DT profile exists with the name "&1" for SOAP application "&2" |
| SRT_WSP128 |
Status "&1" not valid for DT profile |
| SRT_WSP129 |
Profile assignment not possible; no interface node exists |
| SRT_WSP130 |
Profile assignment not possible; no operation node exists |
| SRT_WSP131 |
Profile assignment not possible; assigned profile is invalid |
| SRT_WSP132 |
Error when reading variant "&2" of service definition "&1": &3 |
| SRT_WSP133 |
Error when reading variant "&2" of service definition "&1" |
| SRT_WSP134 |
No variants of type "&1" exist |
| SRT_WSP135 |
Error when opening LPT of proxy class "&1" |
| SRT_WSP136 |
Invalid WSDL attributes for LPT of proxy class "&1" |
| SRT_WSP137 |
Error: &1 |
| SRT_WSP138 |
Cannot determine LP name for endpoint &1 |
| SRT_WSP139 |
Could not determine name of service definition |
| SRT_WSP140 |
Incorrect combination of parameters |
| SRT_WSP141 |
Cannot find variant for endpoint &1 |
| SRT_WSP142 |
Invalid combination of namespace and interface name |
| SRT_WSP143 |
You cannot specify a generic inbound interface |
| SRT_WSP144 |
Cannot find unique inbound interface for &1:&2 |
| SRT_WSP145 |
Error reading service definition '&1' |
| SRT_WSP146 |
Error reading client proxy '&1' |
| SRT_WSP147 |
Characters &2 are not permitted in string "&1" |
| SRT_WSP148 |
Blanks are not permitted in string "&1" |