Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Orchestration call gives "Error occurred during web service invocation: SOAP Fault Code: env:Client SOAP Fault String: java.lang.NullPointerException"
Make sure they are pointing to the correct servers . For examples, if this is your production environment, make sure the URLs are not pointing at staging. If SBM is installed across multiple servers, make sure the URL gives the server names instead of "localhost".
CMS-XML Submitting a new Release Packages gives error "SOAP Fault String: Could not send Message"
Error occurred during web service invocation: SOAP Fault Code : soap : Server SOAP Fault String: Could not send Message.
CMS-XML RLC: Task Template submit fails with error: SOAP Fault String: String index out of range: -1
a call has succeeded SOAP Fault Code : soap : Server SOAP Fault String: String index out of range: -1
CMS-XML Orchestrations and/or notifications stop running after server is restarted
When a synchronous orchestration fires, the user will see error: Error occurred during web service invocation: SOAP Fault Code : env:ClientSOAP Fault String : could not retrieve jms destination: ORCH_LINK_NAME In Composer, if debug logging is turned on for the process app's workflow, you will see error:
CMS-XML SOAP Fault String "Unexpected subelement XXXX"
The goal is to raise an external event with event manager at http:// Server :8085/eventmanager/services/ALFEventManager?wsdl. Make a web service call for service ALFEventManager, function name EventNotice. After populating the necessary inputs, the web service call returns an error because some inputs were left unmapped.
CMS-XML DimCM: Build: SOAP-ENV:Server"HTTP Error" when running build
Internal SPI error: BCB1901000E Error: SOAP FAULT: SOAP-ENV:Server"HTTP Error". COR1601012E The allocation of a build job by the SCBC failed with code -1; processing cannot continue COR3600433E Job Queue id = 0; Job Id = 0 (BCB1901000E Error: SOAP FAULT: SOAP-ENV:Server"HTTP Error".
CMS-XML RLM: When creating a new Release Train, an error of get SOAP Fault String: checkUniqueness error
SOAP Fault Code: env:Client SOAP Fault String: checkUniqueness: Blank: This error occurred during the execution of the orchestration workflow. Upgrading from 2.1 changes the default port for tomcat from 9095 to 8080 and if this changes on the server than this must be reflected in all endpoints and web services.
CMS-XML RLC: When submit a new Release Package, user gets error "SOAP Fault String: Error writing to XMLStreamWriter" (any action using ScriptRunner)
The URL that RLC is using to communicate with the SBM Application Engine is not valid. This is typically set by Configurator from the settings on the Component Server and IIS Server views. Here are a couple tips to try:
CMS-XML Creating an Application Release gives error "SOAP Fault String: uniquenessCheck: Blank: Transport error: 404 Error: Not Found"
Log into the ALM Configurator ( http://MyReleaseManagerServer:8080/alm/config/alm ) and update the values on the ALF and SBM pages. After the changes are complete, restart the Serena Common Tomcat service. The values should be like this: (You will use your server names and your port number if different than the default.)
CMS-XML Synchronous orchestration times out after 30 seconds with error "SOAP TimeoutRequest"
Error occurred during web service invocation: SOAP Fault Code : env: Server SOAP Fault String: <orchestration_name_here>: RequestTimeout: The orchestration request was submitted but the server timed out waiting for the response
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs