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 Dim cm : z/os build fails with this error : MDHBLD4207181E soap error sending build messages: SOAP FAULT: SOAP-ENV:Client"EDC9501I The name does not resolve for the supplied parameters."
Dim cm : z/os build fails with this error : MDHBLD4207181E soap error sending build messages : SOAP FAULT : SOAP -ENV:Client"EDC9501I The name does not resolve for the supplied parameters."
CMS-XML Getting the warning in the Common Log “Cannot enforce correct SOAP Message element order. Using build order. Schema object not found for namespace http://deployview.serena.com and localname getDeployView[org.jbpm.bpel.integration.soap.SerenaSoapUtil]”
Getting the warning in the Common Log “Cannot enforce correct SOAP Message element order. Using build order. Schema object not found for namespace http://deployview.serena.com and localname getDeployView[org.jbpm.bpel.integration.soap.SerenaSoapUtil]”
CMS-XML 14.3.3 / build => BCB1901000E Error: SOAP FAULT: SOAP-ENV:Client"No connection could be made because the target machine actively refused it."
Build fails with these error messages : BCB1901000E Error: SOAP FAULT: SOAP-ENV:Client"No connection could be made because the target machine actively refused it." COR1601012E The allocation of a build job by the SCBC failed with code -1; processing cannot continue
CMS-XML KB-DIM2009: SSL SOAP FAULT: SOAP-ENV:Client No connection could be made because the target machine actively refused it.
After implemented SSL, user could not perform " Build " via Desktop client and Web Client as it produced error message as below:
PDF Orchestration Scaling and Design in SBM
Orchestration workflows provide the integration point between SBM and legacy systems and can be initiated from either. Legacy systems without SOA capabilities can interact with the human workflow by sending specially constructed e-mails containing SOAP messages to fire off asynchronous orchestration workflows which interact with the SBM Application Engine. The Event Manager accepts e-mail events in multiple formats as shown in What is the SBM Orchestration Engine [page 3].
CMS-XML Dim10: Build error COR1900057E Error: SOAP FAULT: None
BLDB "<bld id>" /AREA="<area id>" /NOBATCH /BUILD_CLEAN /BUILD_CONFIG="<buildcfg>" /CAPTURE COR1900057E Error : SOAP FAULT : None "None"
CMS-XML During deploy you get this error: "ERROR -- Failed to deploy event map for orchestration...: Access to this endpoint and/or SOAP action is not allowed"
Deploying to server "Default Event Manager Server" at 11/16/15 2:58 PM. INFO -- Constructing the ALF Event Map(s)... INFO -- Found event map for the "MyOrch" process app.
CMS-XML Dim CM 14.2.x: Problems with Build having set up Dimensions CM to communicate via SSL
BCB1901000E Error : SOAP FAULT : SOAP -ENV:Client"SSL_ERROR_SSL: error :14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed; self signed certificate"
CMS-XML DIM14.1: Pulse: Review not being created/Jenkins Build is not being run
OR 2. Refer to the following in the documentation, (see attachment for further details): Verify the DM_ALF_ENDPOINT and the DM_WEB_URL in the dm.cfg file are set correctly e.g. DM_ALF_ENDPOINT %DM_PULSE_WEB_URL%/services/ soap /alf
CMS-XML Dim12: What are the definitions of DM_SOAP_RECV_TIMEOUT, DM_SOAP_SEND_TIMEOUT, DM_SOAP_RECV_SUBMIT_BUILD_TIMEOUT variables?
The DM_SOAP_SEND_TIMEOUT specifies the max time that gsoap will wait when sending a message, in seconds. DM_ SOAP _RECV_SUBMIT_BUILD_TIMEOUT is a special symbol for BUILD services as these can take a long time, in seconds. See also Knowledgebase Solution S134658 about the context of usage of these symbols
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs