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 PCLI : Error: <file>: Could not find a revision named * in the archive, <archive file>.
PCLI : Error: &lt;file&gt;: Could not find a revision named * in the archive, &lt;archive file&gt;.
CMS-XML Random "Could not find a revision named XXX" errors when using a Version Label that starts with a number for a Get operation
Random " Could not find a revision named XXX" errors when using a Version Label that starts with a number for a Get operation
CMS-XML Get on split archive shows "Could not find a revision named * in the archive" if the target directory is not writable
Get on split archive shows " Could not find a revision named * in the archive" if the target directory is not writable
CMS-XML Checkout or Get by a Version Label which starts with a number will give the error: "Could not find a revision named [LabelName] in the archive [ArchivePath]"
This happens because Version Manager is interpreting the label as a Revision Number instead of a Version Label. Example using a Version Label named "5.2": Doing a Check Out by Version label, entering the Version Label in the Revision field, will generate an error:
CMS-XML VM: Warning: Could not complete action because the archive "archive name>" contains no revisions.
Q: How and why was this created? A: These empty archives could have been created by a user with appropriate rights by selecting the 'Do not check in workfile' option while using the 'Add Workfiles' option (this option is available only if that user has SUPERUSER or UNLIMITED privileges). This creates an empty archive with the following details in it - create time, user id for the person that created the archive, work file name , access list (if any), owner, attributes, and archive description.
CMS-XML Dim10: Cannot compare item revision when item name contains "%" character
Dim10: Cannot compare item revision when item name contains "%" character
CMS-XML KM-Dim9: Action Change Doc: 1197-The item does not have an IN RESPONSE To revision in change document
Action Change Doc: 1197-The item <item name > does not have an IN RESPONSE TO revision in change document <change doc id>
CMS-XML DIM2009: Building from a stream with option to Capture Build Outputs does not place the branch name on created revisions
Example: branch_name for the stream is "branch_1", all revisions created in the stream are correctly prefixed with "branch_1" with the exception of the revisions delivered by the builds. The branch_ name does not appear for the revisions delivered by the build.
CMS-XML KM-Dim9: Extract Item - Error: Cannot create revision name#2 from 1 because 1 does not descend from the leaf revision(s) on branch name.
| | | | NAME #1 NAME #2
CMS-XML The minus sign / dash character (-) is no longer allowed in version label names because it conflicts with revision offset calculations
By using these characters in the names of labels you run the risk of getting unexpected behavior. For example, if the labels "Project" and "Project-2" are both used in Version Manager, a query for revision "Project-2" will get the correct revision for files that have this label, but get a revision 2 prior to the one for label "Project" if a file only has that label, where you would have expected to not get this file
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