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 Ports listed in Admin Guide are incorrect.
ChangeMan DS requires that certain TCP/IP ports are open or available. These
CMS-XML SQL Express Bad Port Error
This can be due to the TCP/IP client protocol being set to disabled. To enable the protocol, edit the TCP/IP option in the corresponding Client Configuration option in the SQL Server Configuration Manager
CMS-XML Microsoft patches KB4338815 and KB4338818 may causes services to fail with port in use errors
(Windows 2008 R2 SP1), TCP/IP connectivity to services may stop working following a service restart. The logs for these services may subsequently have errors similar to:
CMS-XML TCP/IP port list in Troubleshooting appendix of Administrator Guide
The lists of ports provided in the answer to the "Why can’t I access areas or servers through a firewall?" question is incorrect .
CMS-XML DOC ISSUE : TCP/IP Ports defined to CMN Technical Note.
In the TCP/IP Trouble Shooting section of the ZMF Installation Guide, there should be some text to say that TCP/IP PORTS reserved for CMN should be assigned the subtask ID (CMN). The results of this not being performed is the following error . TCP/IP BIND: RC=FFFF ERRNO=00013
CMS-XML Incorrect SQL Server Port Appears in the Configuration Utility
"Your database must have TCP/IP protocol enabled. For example, TCP/IP protocol is not enabled by default if you install Microsoft SQL Express independently of the installer. Refer to your database documentation for enabling TCP/IP protocol."
CMS-XML SLM: Servers in triad configuration fail to start with error: Missing Port on Server line , exiting.
As of SLM 2.2.0, each SERVER line in the license file needs to end in the TCP/IP port number that the lmgrd process on this server should use. See the section How to install the license key in KB doc S129439 for more information.
CMS-XML Started task TCP/IP ErrNo=47s binding to ports
Once this error is encountered ZMF automatically retries to connect to an IPv4 socket. So, as long as the SER1020I/ErrNo=47 message is followed by a successful connection then it can be ignored. However, if it is accompanied by IPv4 failures for the same port number then further investigation will be required.
CMS-XML DIM: z/OS Getting Bind failed error when starting Dimensions ZOS Listener
Make sure the user who starts or submitts the Listener job has BPX.SUPERUSER profile and the TCP/IP Port used is larger than 1025.
CMS-XML DimCM: AdminConsole: Connection Pooling statistics returns a 500 error
AND/OR 2. If using a non-default port for SDP or TCP/IP (other than 671). This error can then occur.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs