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 Dim12: z/OS: When starting z/os agent, got the error "MDHAZJ160006E Failed to bind to port: errno 1115 - EDC8115I Address already in use."
a) ...PARM(MDHTDIMV) : agent 1 : DM_META_DATASET=+DMSYS.DIM 671 .MTABASE@10.31.16.150:4524 agent 2 : DM_META_DATASET=+DMSYS.DIM672.MTABASE@10.31.16.150:4524
CMS-XML Server applications on Linux fail to re-bind to a TCP port when they are restarted within 60 seconds of being stopped
When a server process uses a fixed TCP port, stopping and restarting that process on a Linux OS may result in a failure indicating that the port is in use. For example, if your SLM (Serena License Manager) server is using a fixed port , restarting the server will result in the following error in the SerenaLicenseServer.log file: 12:32:13 (lmgrd) Failed to open the TCP port number in the license.
CMS-XML HTTP Server (SERSERV) fails to bind to port: Return Code 2016 Reason: EHOSTNOTFOUND message
08/29/12 15:15:52 SerServ system : zOS 08/29/12 15:15:52 SerServ Port : 7100 08/29/12 15:15:52 SerServ jobname: SERSERVT
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 Dim10: LDAP: Failed to connect to the Dimensions server. LDAP Error: (49) Invalid credentials, LDAP Server Error: 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 52e, vece, PRG4500325E Error: User authentication failed - LDAP bind to server failed
DFSTrace: 23368: Jan 24 08:52:24 2008 Attempting LDAP login DFSTrace: 23368: Jan 24 08:52:24 2008 Using LDAP host <severname> and port 389 DFSTrace: 23368: Jan 24 08:52:24 2008 LDAP search binding as <bind user>
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 Using SBM web service with Visual Studio or Visual Web Developer gives The request failed with HTTP status 404: Not Found when run.
<documentation>gSOAP 2.7.17 generated service definition</documentation> < port name="aewebservices71" binding ="tns:aewebservices71"> <SOAP:address location=" http://localhost:80/gsoap/gsoap_ssl.dll?aewebservices71"/ >
CMS-XML Serena VM Web Application Server or Serena Common Tomcat fails to start when VM and SBM 11 are installed on the same system
SBM 11 inadvertently introduced a Tomcat port conflict that prevents the secondary Tomcat server from starting, so depending on the startup order either Serena Common Tomcat ... will fail to start. ... java.net.BindException: Address already in use: JVM_ Bind
CMS-XML Dim10: LDAP: Failed to connect to Dimensions Server, LDAP: (10) Referrals, PRG4500325E Error: User authentication failed - LDAP search failed, ACL4500326E Error: User authentication failed when connecting to host occurs
Failed to connect to the Dimensions server ... PRG4500325E Error: User authentication failed - LDAP search failed ACL4500326E Error: User authentication failed when connecting to host <servername> User authentication failed ... DFSTrace: 10802: Jan 17 18:07:32 2008 Using LDAP host <hostname> and port 389 DFSTrace: 10802: Jan 17 18:07:32 2008 LDAP search binding as < bind user> ... DFSTrace: 10802: Jan 17 18:07:32 2008 LDAP: ldap_search_s failed
HTML SBM Version Diff
Differences Between Versions ... -wrap: break -word; ... ... -wrap: break -word; ... ... { page- break -after: ... ... -wrap: break -word; ... + break ; + break ; ... = false; break ; } @ ... ... !hideRow) break ; // ... ... bother checking further break ; } @ ... ... , server and port portion of the ... ... [:optional port ]/. ... ... , server and port of the url ... ... [:optional port ]/. ... ... this might get broken after next upgrade ... ... / if it failed , we're probably ...
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs