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 REST Grid reports authentication failure if no results returned - message: Rest service called failed. Check the authentication settings of the endpoint used by the REST grid in Application Repository
REST Grid reports authentication failure if no results returned - message: Rest service called failed . Check the authentication settings of the endpoint used by the REST grid in Application Repository
CMS-XML Azure AD: Rest service report fails with username / password
Issue with call to RestService/Report/Run with username/password
CMS-XML Get "peer not authenticated, Exception calling REST service" when using the rest caller widget calling an https url
This can be caused by the certificate used by the target url in the rest caller widget not being "trusted" by Tomcat/JBoss. When Tomcat/JBoss attempts to make the rest call and the ceriticate isn't trusted or there is a problem with the certificate the connection can't be made and the request will fail .
CMS-XML PulseUno: Http failure response for http://server:8080/pulse/services/rest/hostedrepos: 500 internal server error.
On UNIX systems we rely on an environment variable called “HOSTNAME” (set to the local hostname). If this is not set the installer is supposed to fall back to using “localhost” but there was a typographical error in the logic which meant “lcoalhost” was used instead.
CMS-XML HLLX service calls failing with CMN1174A message
HLLX service calls failing with CMN1174A message
CMS-XML Static diagnostic test 'SBM Services' failed with "The calling thread cannot access this object because a different thread owns it" error
The static diagnostic test 'SBM Services' fails with a "The calling thread cannot access this object because a different thread owns it" error in a distributed environment with components installed on separate servers. The failure does not necessarily indicate an actual problem.
CMS-XML ERO: Checkin XML Services failing to copy IMS executable components in correct manner
In order to ensure that the executable components built by PSB source components (i.e. IMS library subtype = S components) are copied correctly from dataset to dataset we enforce use of IEBCOPY rather than SERCOPY executed with the ALIAS BSAM MFS REALLOC RETRY options, even if IEBCOPY is called from SERCOPY 'behind-the-scenes'. This works fine when ERO package or area checkin is invoked
CMS-XML PACKAGE.PRM_HIST.LIST XML Service fails to return existing promotion history data (CMN6504I)
For example, a SERXMLBC batch call will end with a step return code 8 and the following response: <statusMessage CMN6504I - No information found for this request.</statusMessage
CMS-XML Web service call TransitionItem with TranId = 0 fails in 10.1.1.3
Manager 4.0Release Manager 4.0.1Requirements Manager 4.0.1SBM 10.1.1.4 Service Manager 4.0Service Manager 4.0.1
CMS-XML Orchestration with Web Service call that uses dynamic endpoint is not able to find service
The problem is reproduced if the WSDL that describes the service which dynamic endpoint accords to imports any XSD or WSDL - in this case WSDL read operation fails as the child XSD/WSDL is not prepared in the local system as it is performed in the case of static endpoints usage due to the following:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs