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 SLM: Certain clients sometimes/consistently cannot connect to the License Server, especially from remote locations
As a result, client libraries used in SLM 2.1.4-based product only wait 100ms for a response from the License Server if those clients only specify the name of the SLM server (and not port number as wel). This is quite a bit shorter than the timeout found in previous releases.
PDF Serena Builder for Professional User’s Guide
* You do not have to specify any file that is named as an included file. 96 Serena® Builder™ for Professional™ 6.4.1 Setting Up a Build
CMS-XML Search Filters for SBM Reports and RegEX
last name CONTAINS '[C-P]arsen' finds author last names ending with arsen and starting with any single character between C and P, for example Carsen, Larsen, Karsen, and so on. ... Any single character not within the specified range ([^a-f]) or set ([^abcdef]). last name CONTAINS 'de[^l]%' all last names starting with de and where the following letter is not l.
CMS-XML KM-Build6: License Vendor '@' is not supported
Make sure the proper vendor name is the first line and the SLM information is the second. This error will occur if the vendor of 'MERANT' or 'SERENA' is not the first line. i.e.
HTML Serena Builder Readme
6.1 Spaces in Build Directory Path Can Cause PCLI Error In the first case, you will see a message indicating that the directory does not exist , or that the specified substitution is not valid for the command. For example:
CMS-XML KM-Build6: Build 6.3.1 error Prohibited Package Name: java.lang when building java war projects
KM-Build6: Build 6.3.1 error Prohibited Package Name : java.lang when building java war projects
CMS-XML BUILD: Necessary patch for Merant Build for Merant Professional Suite to operate with Named Licenses - IMPORTANT: This only applies ot the Merant Professional Suite.
BUILD: Necessary patch for Merant Build for Merant Professional Suite to operate with Named Licenses - IMPORTANT: This only applies ot the Merant Professional Suite.
CMS-XML SSO/CAC can use PIV Cards in addition/instead of CAC Cards. Identity Transform
+3),1); // the ",1" parameter indicates PIV log.trace("Transforming SubjectUID:" +username); } } if (username == null) { log.error(" Cannot transform certificate for subject common name (CN): " + String(subj)); } RESULT = username; ]]>
CMS-XML Serena License Manager 2.1.4 (SLM 2.1.4)
1.7 Character Corruption in Version Manager Windows Client Host Name (DEF98893 - Client) Server names are no longer corrupted when users connect to the Version Manager Windows client and the host name for the client contains double-byte characters.
CMS-XML How To successfully build an example Java application using Builder and Version Manager
The attached files, one in a Microsoft Word document (.doc) and one in an Adobe Acrobat (.pdf) format, provide example source code for a HelloWorld Java application, named HelloWorld.java. The documents then give step-by-step instructions to create a build job in Builder and execute the build job through both Builder as a standalone and the Version Manager/Builder integration. Note: The example uses a Java build type which requires Builder Enterprise licensing.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs