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 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 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 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
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 Release Package gives error "RequestTimeout: The orchestration request was submitted but the server timed out waiting for the response"
Error occurred during web service invocation: SOAP Fault Code : env: Server SOAP Fault String: addDeployUnitsTo RP: RequestTimeout: The orchestration request was submitted but the server timed out waiting for the response
CMS-XML Web service relateVaultBaselines is too slow causing SOAP RequestTimeout error
Error occurred during web service invocation: SOAP Fault Code : env: Server SOAP Fault String: addDeployUnitsToRP: RequestTimeout: The orchestration request was submitted but the server timed out waiting for the response
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 VM 8.x shows gSOAP error code 505 and 505 HTTP Version Not Supported while communicating with the File Server
Error communicating with file server "http://or-richardg:8080/merantfs/FileServer ": Unknown gSOAP error code 505. SOAP FAULT : SOAP -ENV: Server "HTTP error " Detail: HTTP/1.1 505 HTTP Version Not Supported.
CMS-XML Error "DeploymentPath.message.NoTaskCollectionScheduleEnvironmentsFound 100083" when creating a release package
When creating a new Release Package, the user receives an error such as: Error occurred during web service invocation: SOAP Fault Code : soap : Server
CMS-XML Error "No scheduled environments found for collection id xx" when creating a Turnover
Error occurred during web service invocation: SOAP Fault Code : soap : Server SOAP Fault String: "No scheduled environments found for collection id xx.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs