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 The "Check in on" Column shows incorrect version when opening an Process App from the repostiory.
The "Check in on" Column shows incorrect version when opening an Process App from the repostiory.
CMS-XML Dim CM 12.2.2: Revisions created on named branch incorrectly
Dim CM 12.2.2: Revisions created on named branch incorrectly
CMS-XML Version numbers get out of sequence which can lead to error when checking out of the repository.
Version numbers get out of sequence which can lead to error when checking out of the repository.
CMS-XML Dim CM 12.1: Revision identifiers are incorrect when unique branch name contains a space
Items will be created with an incorrect revision if a Named Branch containing a space is used. For example:
CMS-XML Old version of ICU4j library wrongly apply daylight saving time for Moscow timezone
Old version of ICU4j library wrongly apply daylight saving time for Moscow timezone
CMS-XML Dim12: Comparing item revisions with long filename gives Error: Unable to access the following file for reading:
Using desktop client to compare an item revision where the total pathname (directory path and filename) is long causes an error: Error : Unable to access the following file for reading: This error was encountered in a situation where the project directory was 210 characters long and the filename was 28 characters long.
CMS-XML DMCM: Some items created with a dash (-) revision cannot be checked out without error
Users in desktop client can create new items with initial revision "-" using an item type with a sngle state lifecycle. Such items cannot then be checked out without error . If item is created as a type using a multi-state lifecycle it can be checked out.
CMS-XML Error: "org.jbpm.bpel.BpelException: process not found: name=00000$orchestrationName$ochDesginNumber, targetNamespace=null, version=xx"
In rare circumstances, an error such as the following could occur in the server.log. When this happens, the orchestration given in the error will not be run.
CMS-XML Dim12: VM2DM: Error: 498 revision count mismatches occurred
The above error is caused by having invalid characters within the VM data. The invalid characters can exist either in the Project (Directory) name or the archive name. The data is properly migrated with the special characters into Dimensions but we are unable to perform the official auditing of the revision count on the items.
CMS-XML Error Promoting Dev Change Requests Snapshot
On promoting the Dev Change Requests snapshot after upgrading to DVM 4.5 from a previous version , the promotion may fail with the following error appearing in the log file:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs