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 HTTP 500 error connecting to ZMF web services.
HTTP 500 error connecting to ZMF web services .
CMS-XML Dim14: HTTP Connector: Windows could not start the Serena Dimensions HTTP Connector
In some circumstances the HTTP connector service does not start on a Windows Server. When trying to manually start the service from the Services option in Control Panel, it reports: Windows could not start the Serena Dimensions HTTP Connector
CMS-XML The Orchestration Engine cannot send the Web service request at Service step SAC_GetMapRecordForProductAndRelease with Agile Connector
The Orchestration Engine cannot send the Web service request at Service step SAC_GetMapRecordForProductAndRelease to the endpoint defined as http ://agileserver/SerenaConnectors/SerenaAgileConnector.asmx . You should verify that the definition is correct and that the server is responding.
CMS-XML ALM Connector: RestGrid using /almzmfws/services/SernetProxyHttpServer gives: Unknown error received 500
Unknown error received from https://XXXXX/sbmproxy/xhp [url: ' http ://XXXXX:8080/almzmfws/ services /SernetProxyHttpServer?system=ZMF&hostName=999.999.999.999&hostPortId=999&userId=XXXXX&responseType=JSON&request=PACKAGE%2FGENERAL%2FSEARCH%2Fpackage%3D*%2
CMS-XML Composer fails to connect to the repository using HTTPS after successfully connecting using HTTP
Release Control 6.0SBM 10.1.5 Service Manager 5.2
CMS-XML RLC 6.0.1: Submit Release Package gives error "Timeout expired... Response failed... Couldnt connect to http://myServer:80/rlc/scriptRunnerService"
Open SBM Configurator, and click Apply to restart all of the services .
CMS-XML KM-Dim6: TBI Caliber and Dimensions Inet installation cause Error: Page cannot be found when attempting to connect to INET URL http://server hostname>:8000.
ERROR: <Drive>:\Win32App\PVCS\DIMENS~1\6.0\inet\apache.exe: [date][time] [error](1073)The specified service already exists: CreateService failed.
CMS-XML Sequence of the steps to allow an independant program / service to connect through SSO to SDA / SBM - includes generating an SSO token and extracting the SAML from this
<soapenv:Envelope xmlns:soapenv=" http ://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"> <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" soapenv:mustUnderstand="1">
CMS-XML Get the following error when using test connect in Composer "Underlying error: (The HTTP request was forbidden with client authentication scheme 'Anonymous'.)"
clientcertssl-accesscontrol.log [ClientCertSSLAccessControlFilterAccessLog] [00000::] -- DENIED HTTP /mashupmgr/ services /AppRepositoryService You will see these errors if you have enabled "Client Certificate Authentication" from within Configurator but have not followed the steps yet to configure Composer to use those settings.
CMS-XML Error getting SLA data: Connection Refused: Connect when clicking on a service icon in Request Center.
The other option is to not use https for JBoss. In order to do that remove the port value for the https field in the JBoss Server tab and uncheck the use https checkbox on the Component Server tab in the JBoss section. After clicking Apply this will force JBoss to always connect via http and you won't see this error in Request Center.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs