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
Change the SLM server configuration so that the main (lmgrd) server is always using the same port. You can pick the default value of 27000. For detailed instructions, please see KB article S136346 .
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.
CMS-XML KM-Build6: ERROR 31/32: USERID does not have privilidges to the Search Path entry for and
Doing this introduces another problem, when two build jobs are submitted at the same time, the html logs are inconsistent. In fact, from within the first build log, I got information from the second build and vice-versa.
CMS-XML Builder 6.41 Version Information
The Build value is a MMDDYY date. If the build reflects a November '05 value rather than the October '06 dates shown above, the patch has not been applied.
HTML Serena Builder Readme
4.2 Use Sun's JRE, Not jview.exe During the installation of the Serena Builder Knowledge Base server, you are asked to select a Java runtime executable. In the dialog provided for selecting this item , you may see jview.exe selected by default, but you should NOT select jview.exe. If you do, the install of a needed Serena Builder service (the "Openmake" service) may fail.
PDF Serena Builder for Professional User’s Guide
6 If you change your mind about using a dependency, select it from the Detail tab, then click the Delete icon. This will remove the dependency from the build task. (It will not delete the item from disk.)
PDF Getting Started
bldmake can derive the low-level dependency information by scanning the high-level dependencies. High-level dependency information can not be derived, so the developer must enter it. Dependencies that need to be entered for the Target include: the high-level source code, libraries, and resource files that cannot be derived though the process of scanning other files for the information.
CMS-XML Product Lifecycle and Platform Matrix
On the bottom half of the screen, click the + for one of the items in the list.
MS-WORD build_a_java_code.doc
After setting up the Search Path we will now define the Targets for the Java Project. To do this select “Setup Build” menu item and select “DEVELOPMENT” under the “HELLOWORLD” project.
CMS-XML Serena License Manager 2.1.4 (SLM 2.1.4)
to address item 1.3). Where that is not possible, for example if you are using Tracker or Meritage, you can use the attached client libraries to replacement the ones that are currently installed with your product.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Working with items, part 1 (demonstration)
This Dimensions CM demonstration shows you how to perform impact analysis to determine which files are affected by specific changes

Additional Assistance

  • Submit a Case Online
  • FAQs