NonStop SOAP 4.1 User's Manual

Cause
The same service name appears twice in the SDL file.
Effect
The command fails.
Recovery
Select a unique name for each service in the SDL file and run the SoapAdminCL command.
SOAPADMIN ERROR >> HTML client file already exists...
Cause
The HTML client file exists at the mentioned location.
Effect
The command fails.
Recovery
Check whether the service is already deployed at the mentioned location. If you want to
regenerate the files or redeploy the services at the mentioned location, use the SoapAdminCL
command with the –f or –force option.
SOAPADMIN ERROR >> WSDL file already exists...
Cause
The WSDL file exists at the mentioned location.
Effect
The command fails.
Recovery
Check whether the service is already deployed at the mentioned location. If you want to
regenerate the files or redeploy the services at the mentioned location, use the SoapAdminCL
command with the –f or –force option.
SOAPADMIN ERROR >> Service configuration file already exists...
Cause
The service configuration file exists at the mentioned location.
Effect
The command fails.
Recovery
Check whether the service is already deployed at the mentioned location. If you want to
regenerate the files or redeploy the services at the mentioned location, use the SoapAdminCL
command with the –f or –force option.
SOAPADMIN ERROR >> Error in definition of service "<service_name>". Both attributes
"GenerateSessionHeader" and "GenerateTransactionHeader" cannot have a value "yes"
Cause
The GenerateSessionHeader and the GenerateTransactionHeader attributes are set
to yes.
Effect
The command fails.
Recovery
Ensure that the GenerateSessionHeader and the GenerateTransactionHeader attributes
are not set to yes.
302 NonStop SOAP 4 Error and Warning Messages