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 ZMF4ECL: Users still unable to connect to ZMF Server with SER8210E error messages, despite applying previous fixes
ZMF4ECL: Users still unable to connect to ZMF Server with SER8210E error messages, despite applying previous fixes
CMS-XML ZMF4ECL: Multiple users still unable to connect to ZMF Server (SER8210E) despite running fix for OCTCR46A38001
However, a number of users continue to report the same symptoms using the fixed build (the fix was originally implemented in build 511, customer is currently running build 512). To recap the original problem, many users are reporting that they cannot connect to a ZMF Server instance from the ZMF4ECL interface, ChangeMan
CMS-XML Unable to see components in participating package.
This issue occurs if you have a Complex package which is linked to two participating packages from different Applications. When you expand the second participating package that is not from the same application as the complex packages application, in the folder view it does not display the components.
CMS-XML "Approve" is grayed out after an unplanned package is baselined. POST approvals cannot be done.
The "Approve" link is grayed out after an unplanned package is baselined. POST approvals cannot be done. POST baseline approvals should be allowed for unplanned packages.
CMS-XML "Approve" is grayed out after an unplanned/TEMP package is in TCC status. POST approvals cannot be done.
The "Approve" link is grayed out after an unplanned/TEMP package is backed out to TCC status. POST approvals cannot be done. POST TCC status approvals should be allowed for unplanned packages.
CMS-XML Unexplained TCP/IP connectivity issues to ZMF Server started task
A customer is reporting that since upgrading to ZMF 8.2 Patch 3 a number of their ZMF4ECL users are unable to connect to their ZMF Server started task at certain times. The failures to connect are linked
CMS-XML HTTP 500 error connecting to ZMF web services.
HTTP 500 error connecting to ZMF web services.
CMS-XML Intermittent S33E abends during ZMF4ECL CONNECT/LOGON
Intermittent S33E abends during ZMF4ECL CONNECT /LOGON
CMS-XML Defects resolved in ChangeMan ZMF for Eclipse (ZMF4ECL) 8.2 Patch 5
OCTCR46A56004 ZMF4ECL: Multiple users still unable to connect to ZMF Server (SER8210E) OCTCR46A61001
CMS-XML Web Services XJRJESTYPE needs additional fields defined
Users cannot connect to ZMF from the ZMF4ECL plug-in, because Web Services rejects the ENVIRONMENT LIST response because XJRJESTYPE is D in their environment. The Web Services definition only permits '2' or '3'. Any Character should be permitted in this field
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs