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 SQL Server instance name ignored and port only is used
SQL Server instance name ignored and port only is used. The port seems to be the only factor controlling this and doesn't need to match the Instance name provided.
CMS-XML How To: VMINET - Customize the port used by VM Server
3. For Netscape Enterprise Server / iPlanet Change the "proxyport" value to match the one you specified above,e.g. proxyport="8081" For VM Server 6.7.10+ (using Tomcat) There is no need to modify anything since parameters in obj.conf
CMS-XML SDA gives error "SSO Gatekeeper error has occurred: Authentication processing error" with "Invalid federation server"
To resolve this message, modify the file gatekeeper-core-config.xml (located in C:\Program Files\Common\tomcat\8.0\alfssogatekeeper\conf ), changing the following parameters as shows here: <parameter name="SecurityTokenService" Type="xsd:anyURI">http://sbm- server :sbm- port /idp/services/Trust<parameter>
CMS-XML Installing Mariner and Server name keeps adding :8080 (or any port)
Installing Mariner and Server name keeps adding :8080 (or any port )
CMS-XML How to test a port connection on a Windows Server
At times, it is necessary to test that a connection is open to a given port. Windows Server / Workstation no longer comes with Telnet installed by default, but it does come with PowerShell. Here are the steps to test your connection to your LDAP server (myldap.company.com), for instance.
CMS-XML After installing Microsoft Windows patch KB3172605 on a client PC, Internet Explorer can no longer access Tomcat-based servers via HTTPS (ports 8443/8444)
After installing Microsoft Windows patch KB3172605 on a client PC, Internet Explorer can no longer access Tomcat-based servers via HTTPS ( ports 8443/8444)
CMS-XML Started task TCP/IP ErrNo=47s binding to ports
When starting a ZMF 8.1.1+ started task the following type of messages can often be seen:
CMS-XML Do not require the Tomcat Server section for HTTPS for client certificate port be specified.
If SBM Authentication is set to SmartCard, the Configurator will require a port be specified in the Tomcat Server section for HTTPS for client certificates. There are 3 ways of setting up SmartCard and only one of them requires the HTTPS for client certificate port to be specified in Configurator.
CMS-XML SLM: Servers in triad configuration fail to start with error: Missing Port on Server line , exiting.
SLM servers in a three- server redundancy configuration fail to start. The SerenaLicenseServer.log files show errors similar to:
CMS-XML SRA: What ports and protocols are used for communications between SRA Server and SRA Agent
Communications between the Serena Release Automation Server and Agent utilizes the Java Message Service (JMS) protocol. The default port for this communications is 7918 -- though this may be changed/configured at installation time.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs