| SRT_WSP2121 |
No Service Group is specified |
| SRT_WSP2122 |
Neither Service Group nor LRD Filter is specified; Check Input |
| SRT_WSP2123 |
You must not use defaults and specify an auth method at the same time. |
| SRT_WSP2124 |
Only Simple Client configurations can be deactivated or deleted. |
| SRT_WSP2125 |
No Simple Client Provider API defaults are maintained. |
| SRT_WSP2126 |
LRD Filter could not be retrieved from Service Group |
| SRT_WSP213 |
Object is still being used and cannot be deleted |
| SRT_WSP214 |
Could not delete usage relationship |
| SRT_WSP215 |
Specified configuration &1 with type &2 does not exist |
| SRT_WSP2150 |
Deserialization of WSIL document failed |
| SRT_WSP216 |
Configuration type &1 not supported for this operation |
| SRT_WSP217 |
Unknown protocol '&1' specified |
| SRT_WSP218 |
Error when reading local information for protocol '&1' |
| SRT_WSP219 |
Calculated URL path does not exist for binding &1 (&2) |
| SRT_WSP220 |
IIF '&1' has no active service definition: NS '&2' |
| SRT_WSP221 |
LP name &1 is already allocated for DT object &2 |
| SRT_WSP222 |
Property &1 has an empty value for channel &2 |
| SRT_WSP223 |
IIF '&1' has no active auto-generated service definition: NS '&2' |
| SRT_WSP224 |
Specify a SOAP application name and subject type |
| SRT_WSP225 |
Could not calculate hash value (RC: &1) |
| SRT_WSP226 |
Could not lock configuration entry (hash: &1) |
| SRT_WSP227 |
Could not lock secure link entry &1 |
| SRT_WSP228 |
Could not save secure link entry &1 |
| SRT_WSP229 |
Data too long for secure link entry &1; &2 |
| SRT_WSP230 |
Secure link entry &1 is read-only and not locked |
| SRT_WSP231 |
Write error in secure link ID &1. &2&3&4 |
| SRT_WSP232 |
Read error in secure link ID &1. &2&3&4 |
| SRT_WSP233 |
Could not delete secure link entry &1; &2 |
| SRT_WSP234 |
Cannot navigate to entry &1 in SOAP Runtime |
| SRT_WSP235 |
Key (ID and/or type) of SOAP Runtime objects is not specified |
| SRT_WSP236 |
Transport binding contains properties with differing releases |
| SRT_WSP237 |
Caller cannot call this method |
| SRT_WSP238 |
Entry in configuration &1 does not exist for property &2 |
| SRT_WSP239 |
Error when saving configuration &1 for property &2 |
| SRT_WSP240 |
Unknown data type &1 specified for secure store |
| SRT_WSP241 |
Entry in profile &1 does not exist for property &2 |
| SRT_WSP242 |
Error saving profile &1 for property &2 |
| SRT_WSP243 |
Service node and binding node are in same namespace |
| SRT_WSP244 |
Web service configuration "&1" is not active |
| SRT_WSP245 |
Access URL for administration tool is not defined |
| SRT_WSP246 |
Unknown error: &1&2&3&4 |
| SRT_WSP247 |
Enter a host name |
| SRT_WSP248 |
Enter a valid port number [1..65535] |
| SRT_WSP249 |
Enter a valid access path |
| SRT_WSP250 |
Access information for web service administration saved |
| SRT_WSP251 |
Enter a valid Web service administration user |
| SRT_WSP252 |
Enter a Web service administration password |
| SRT_WSP253 |
Error saving: &1&2&3&4 |
| SRT_WSP254 |
Entered access data is formally correct |
| SRT_WSP255 |
Could not generate GUI container |
| SRT_WSP256 |
Could not create HTML control |
| SRT_WSP257 |
Query error; no action |
| SRT_WSP258 |
Configuration data removed from permanent memory |
| SRT_WSP259 |
Configuration data not changed in permanent memory |
| SRT_WSP260 |
Error deleting configuration data; &1&2&3&4 |
| SRT_WSP261 |
Error repeating read of configuration data; &1 |
| SRT_WSP262 |
Configuration data read from persistent memory again |
| SRT_WSP263 |
Error when getting administration data; &1 |
| SRT_WSP264 |
No administration data exists yet |
| SRT_WSP265 |
Internal error; cannot set protocol details |
| SRT_WSP266 |
Profile &1 of type &2 is still used in assignments |
| SRT_WSP267 |
Hash value calculation failed; &1 |
| SRT_WSP268 |
Namespace/name of property missing for calculation of hash value |
| SRT_WSP269 |
Error in database access for client-wide configuration |
| SRT_WSP270 |
Property cannot be locked: &1, &2 |
| SRT_WSP271 |
Object cannot be modified; switch to change mode |
| SRT_WSP272 |
Permanent error. &1&2&3&4 |
| SRT_WSP273 |
Error when reading secure store for SOAP key '&1' |
| SRT_WSP274 |
Invalid state: &1 |
| SRT_WSP275 |
Unknown end point type: &1 |
| SRT_WSP276 |
Unknown state change: &1 |
| SRT_WSP277 |
Could not get configuration &1 with state &2 |
| SRT_WSP278 |
Error when starting browser (RC=&1) |
| SRT_WSP279 |
Browser started |
| SRT_WSP280 |
IIF does not have an inbound proxy; IIF: &1:&2 |
| SRT_WSP281 |
IIF does not have a service definition; IIF: '&1':'&2' |
| SRT_WSP282 |
DT object '&1' is inconsistent; operation '&2' is missing (NS: '&3') |
| SRT_WSP283 |
No configuration for binding key "&1" |
| SRT_WSP284 |
Configuration with binding key "&1" is not active |
| SRT_WSP285 |
Property '&1' is not numerical |
| SRT_WSP286 |
Cannot map language code &1 to ISO code |
| SRT_WSP287 |
Binding names are empty or have different namespaces |
| SRT_WSP288 |
Interface "&1" is not active |
| SRT_WSP289 |
Protocol &1 is not supported |
| SRT_WSP290 |
No interface node exists |
| SRT_WSP291 |
Cannot determine server name of database |
| SRT_WSP292 |
Cannot determine design time URL; &1 |
| SRT_WSP293 |
Invalid value for WSDL version "&1" |
| SRT_WSP294 |
Invalid value for WSDL format "&1" |
| SRT_WSP295 |
Invalid value for WSDL style "&1" |
| SRT_WSP296 |
Invalid cardinality. Property: &1. Namespace: &2 |
| SRT_WSP297 |
Design time configuration name is not specified |
| SRT_WSP298 |
Server design time object '&1' does not exist |
| SRT_WSP299 |
Client design time object '&1' does not exist |
| SRT_WSP300 |
You cannot use this API to change DT object &1 |
| SRT_WSP301 |
No DT object and DT configuration found |
| SRT_WSP302 |
Error reading directory entry (&1, &2, &3) |
| SRT_WSP303 |
DT configuration does not exist (&1, &2, &3) |
| SRT_WSP304 |
Serialiazation of object is missing: &1 (status: &2) |
| SRT_WSP305 |
Error getting ESR data: &1 |