| SRT_WSP306 |
No error messages selected |
| SRT_WSP307 |
Error in user query. &1 |
| SRT_WSP308 |
Deletion error |
| SRT_WSP309 |
Error making correction |
| SRT_WSP310 |
Endpoint type is not specified |
| SRT_WSP311 |
You cannot change the key attributes |
| SRT_WSP312 |
DT configuration is invalid |
| SRT_WSP313 |
Error in WSDL parsing: &1 |
| SRT_WSP314 |
Could not find DT configuration from WSDL |
| SRT_WSP315 |
Database operation '&1' in table '&2' failed |
| SRT_WSP316 |
Serialized data of design time object not found |
| SRT_WSP317 |
Design time object '&1' is not locked |
| SRT_WSP318 |
WSDL does not contain information about interface |
| SRT_WSP319 |
WSDL does not contain information about SOAP application |
| SRT_WSP320 |
ICF error: &1&2&3&4 |
| SRT_WSP321 |
No valid request name for operation: '&1' |
| SRT_WSP322 |
Error when creating DT configuration: '&1' |
| SRT_WSP323 |
Could not construct DT configuration |
| SRT_WSP324 |
Object from SIDL generation is unknown |
| SRT_WSP325 |
Method '&1' can get SIDL from DT object only |
| SRT_WSP326 |
Method '&1' can get proxy from ESR-generated service only |
| SRT_WSP327 |
Client object; SIDL generated for server objects only |
| SRT_WSP328 |
Design time configuration '&1' does not exist |
| SRT_WSP329 |
Design time configuration name is not specified |
| SRT_WSP330 |
DT configuration &1: Endpoint type is not unique |
| SRT_WSP331 |
Change is possible only for assigned profiles |
| SRT_WSP332 |
Qualified name of inbound interface is not specified |
| SRT_WSP333 |
Name of design time object is not specified |
| SRT_WSP334 |
No design time configuration found for '&1' |
| SRT_WSP335 |
No old SOAP server runtime configurations found |
| SRT_WSP336 |
Cannot find DT profile &2 for SOAP application &1 |
| SRT_WSP337 |
Error when deleting Web service configuration(s) |
| SRT_WSP338 |
At least one error or warning occurred. See long text for handling |
| SRT_WSP339 |
ESR IF name is not (fully) specified |
| SRT_WSP340 |
User &1 attempted to load a SOAP application at &3 on &2 |
| SRT_WSP341 |
User &1 loaded SOAP application &4 at &3 on &2 |
| SRT_WSP342 |
User &1 attempted to load a DT profile at &3 on &2 |
| SRT_WSP343 |
User &1 loaded DT profile &3 for SOAP application &4 on &2 |
| SRT_WSP344 |
Request/task &1 does not exist or cannot be used |
| SRT_WSP345 |
LP name &1 cannot be used for local calls |
| SRT_WSP346 |
Property &2:&3 missing in profile &1 |
| SRT_WSP347 |
Property &2:&3 missing in destination &1 |
| SRT_WSP348 |
Values in profile &1 and destination &2 do not match; property &3:&4 |
| SRT_WSP349 |
Destination &1; property not set &2:&3 |
| SRT_WSP350 |
Destination &1; HTTP error: &2&3&4 |
| SRT_WSP351 |
Separate browser window started |
| SRT_WSP352 |
Feature Factory of runtime environment not instantiated |
| SRT_WSP353 |
No property key for property "&1" of feature "&2" |
| SRT_WSP354 |
Multiple profiles found for destination &1 |
| SRT_WSP355 |
Invalid parameter values when opening RT cache instance |
| SRT_WSP356 |
No configuration exists for binding %1 |
| SRT_WSP357 |
Configuration key is initial |
| SRT_WSP358 |
'&1' is not a client-side SOAP application |
| SRT_WSP359 |
No valid configuration derived from WSDL |
| SRT_WSP360 |
Profile &1 (&2) already used in an assignment other than &3 |
| SRT_WSP361 |
RT configuration &1 blocked by another object in working memory |
| SRT_WSP362 |
RT cache object &1 blocked by another object in working memory |
| SRT_WSP363 |
Configuration &1 does not yet have an interface node |
| SRT_WSP364 |
RT cache object &1 does not have binding &2 |
| SRT_WSP365 |
User &1 saved configuration &2 for interface &3 |
| SRT_WSP366 |
User &1 activated configuration &2 for interface &3 |
| SRT_WSP367 |
User &1 deactivated configuration &2 for interface &3 |
| SRT_WSP368 |
User &1 deleted configuration &2 for interface &3 |
| SRT_WSP369 |
User &1 saved profile &2 |
| SRT_WSP370 |
User &1 activated profile &2 |
| SRT_WSP371 |
User &1 deactivated profile &2 |
| SRT_WSP372 |
User &1 deleted profile &2 |
| SRT_WSP373 |
User &1 saved destination &2 |
| SRT_WSP374 |
User &1 activated destination &2 |
| SRT_WSP375 |
User &1 deactivated destination &2 |
| SRT_WSP376 |
User &1 deleted destination &2 |
| SRT_WSP377 |
Error in assignment of LP '&1': &2&3&4 |
| SRT_WSP378 |
Cannot find binding '&1' for LP '&2' |
| SRT_WSP379 |
Property &1 not found in LP &2 and binding &3 |
| SRT_WSP380 |
Cannot find binding '&1' |
| SRT_WSP381 |
Not found: Property &1 (binding &2) |
| SRT_WSP382 |
Multiple properties found: Property &1 (binding &2) |
| SRT_WSP383 |
HTTP error in LP &1: &2&3&4 |
| SRT_WSP384 |
Not enough parameters for object instance: &1 |
| SRT_WSP385 |
Severe error when getting maximum property length of RT cache |
| SRT_WSP386 |
Destination cannot be modified |
| SRT_WSP387 |
Destination has not yet been saved |
| SRT_WSP388 |
Multiple values for parameter "&1" |
| SRT_WSP389 |
You cannot specify a service definition and binding at the same time |
| SRT_WSP390 |
No service definition, interface name, or binding specified |
| SRT_WSP391 |
Endpoint key &1 is invalid |
| SRT_WSP392 |
Service definition &1 is invalid |
| SRT_WSP393 |
Agreement &1 is invalid |
| SRT_WSP394 |
No value for parameter &1 |
| SRT_WSP395 |
Invalid value for protocol &1 |
| SRT_WSP396 |
You cannot specify a service definition and agreement at the same time |
| SRT_WSP397 |
Error occurred that cannot be handled |
| SRT_WSP398 |
Generated WSDL document does not contain data |
| SRT_WSP399 |
No data for binding key "&1" |
| SRT_WSP400 |
Subject context contains more than one endpoint for endpoint key "&1" |
| SRT_WSP401 |
Subject context does not contain an endpoint for endpoint key "&1" |
| SRT_WSP402 |
Invalid value "&1" for WSDL version |
| SRT_WSP403 |
Invalid value "&1" for WSDL style |
| SRT_WSP404 |
Invalid value "&1" for WSDL format |
| SRT_WSP405 |
Invalid value "&1" for WSDL section |