| |
Results |
|
Error coccured during web service invocation:Response failed...
|
In Business Mashups, when performing a Transition with a web service associated, you may receive the above error message. The full error message would be similar to:
|
|
|
|
SBM Web Service response is using two namespaces
|
In some cases the SOAP message returned from an SBM Web Service can use two different namespaces for its elements, where only a single namespace would be expected. The code does not correctly handle the case where the call is in one namespace and the elements type is defined in another namespace.
|
|
|
|
Specific description fields no longer translated in ZMF Connector 6.0 web service responses
|
A customer has reported that a number of fields are no longer being interpreted via the ZMF Connector 6.0 web services . For example, running the query (ZMF package search) service, the response for several *Desc fields used to be returned in the following manner:
|
|
|
|
Error occurred during web service invocation:Response failed
|
When running an orchestration, the user sees an error such as: Error occured during web service invocation: Response failed...
|
|
|
|
How can I get a C# web service program to work with NT Challenge Response?
|
If you would like to communicate to TeamTrack using Web Services but are using NT Challenge Response (NTLM) for authentication. And have also setup the gsoap virtual directory to use NTLM (otherwise there would be a security hole, since non-authenticated users would be able to execute web services programs on the TT database with only a valid loginid and no password).
|
|
|
|
Handling Large Web Service Responses in Service Steps
|
To handle the fault, you should place the Service step within a Scope step and catch the fault in the Catch All branch of the FaultHandler. In addition, you should consider reducing the size of the response SOAP message's payload by redesigning the way you invoke the Service step. For example, you could add filtering if the Web service supports it.
|
|
|
|
charset specification missing from HTTP header in WS responses
|
charset specification missing from HTTP header in WS responses
|
|
|
|
If a non-privileged user tries to use WS getitemsbyquery, XML response message should not include item id reference
|
If a non-privileged user tries to use WS getitemsbyquery, XML response message should not include item id reference
|
|
|
|
Calling out to webservices intermittantly gets no response - it times out
|
If calling out to web services intermittantly gets no response then the timeout parameter can be increased.
|
|
|
|
System Parameter to define web service timeout
|
WebServiceInvocationTimeout in TS_SYSTEMSETTINGS table defines how long TT will wait for a response from a web service . The default is 30 seconds.
|
|
|
