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 "Error occurred during fetching backlog content" message in Serena Work Center
" Error occurred during fetching backlog content" message in Serena Work Center
CMS-XML DA: During installation on Linux or Unix get error bc: command not found
DA: During installation on Linux or Unix get error bc: command not found
CMS-XML ALM: During install get error: Unsupported Oracle home selected
While installing ALM 4.5, after filing in Oracle home, get error : Unsupported Oracle home selected. Installation cannot proceed.
CMS-XML Dim12: AIX64: Get error during build/link of event: munch: The input file x is not valid in the current object mode
Dim12: AIX64: Get error during build/link of event: munch: The input file x is not valid in the current object mode
CMS-XML Error getting services: com.serena.solfwk.ae.exception.AEWebServiceException: org.apache.axis2.AxisFault: Remote host closed connection during handshake
Error getting services: com.serena.solfwk.ae.exception.AEWebServiceException: org.apache.axis2.AxisFault: Remote host closed connection during handshake
CMS-XML KM-Dim6: During TBO, user gets error: SQL-0136-14(12119) ORA-00955: name is already used by an existing object
KM-Dim6: During TBO, user gets error : SQL-0136-14(12119) ORA-00955: name is already used by an existing object
CMS-XML KM-Dim9: During web client logon get error: Please give signed java applet permission to run before logging in and enable java if it is not enabled.
KM-Dim9: During web client logon get error : Please give signed java applet permission to run before logging in and enable java if it is not enabled.
CMS-XML Dim14: RAD: An internal error occurred during "Fetching children" when opening a workspace within RAD
When opening a workspace in RAD, the following error occurs: An internal error occurred during: "Fetching children".
CMS-XML Get "An error happened during the import to Application Engine: AEWebservicesFaultFault" in deploy log in Composer or Application Repository.
When doing a deploy you may see the following error in Composer or the Application Repository logs which may be the result of a couple different situations. ERROR -- An error happened during the import to Application Engine: AEWebservicesFaultFault
CMS-XML Dim2009R2: During Move Item Type (MIT) get error: 2249-Error: Item spec is already used by an existing item
This error is especially common if automatic item id generation is enabled for the item type(s). The problem is that the item id's are generated in sequence from A1 to A9999 (and much higher). Because of this, the new item id that will be used after the MIT command may already be in use by another item of that item type.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Updating a work area from a stream (demonstration)
This Dimensions CM demonstration shows you how to update a work area from a stream, restrict the update to specific folders in the stream, and exclude files from the update.
Dimensions CM: Working with Items, Part 2 (demonstration)
This Dimensions CM demonstration shows you how to copy item revisions to a work area using the Get and Update commands, deliver a modified file from a work area to a stream using the Deliver command, and action an item revision

Additional Assistance

  • Submit a Case Online
  • FAQs