Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML KM-Dim10: Delete Item - COR0005378E Error: You do not have the role to delete Item
User has the delete item privilege but the item type LifeCycle(LC) only has $Originator role. It appeared that only the user that generated the item has the role for the first lifecycle transition.
CMS-XML Dim10: COR4501498E Error: Cannot de-assign the last deployment area from this project because this project (and/or its subprojects) contain item revisions which had been deployed past the initial stage.
In several cases items were " deleted "/removed from the project, but were still in a progressed stage in deployment. In that case, it is necessary to track down those items in $Generic:$Global project and either deploy them back to the initial stage in the Global Stage Lifecycle or if they are test items, they can be deleted from Repository, to resolve this issue.
CMS-XML Dim 12.x / 14.x : not possible to browse an item from baseline view of desktop client, getting error : "Browse Item - COR7700246E You do not have the "Browse" (ITEM_BROWSE) privilege to perform this operation"
Whereas a Baseline is not really linked to a Project, the entry exists only in the history/pedigree records. Indeed, once the Baseline has been created the original Project or Stream could have been deleted and also the Items in a Baseline may not exist in the current Project which is why Dimensions has to use the Global Project to fetch the Baseline. Therefore the Baseline does not take roles from the Project, the same would apply actioning the Baseline.
CMS-XML DimCM: Error: COR7700243E The specified item revision is not in the project "QLARIUS:QLARIUS_MAIN"
Now, if needed you should be able to delete the item in Dimensions CM directly.
CMS-XML Dim CM: Error "VRS3202202E Path is not unique" when attempting to delete duplicate folder structure created by adding a new item
It was noticed after a user added a new item that the folder structure containing the item had completed duplicated an existing folder structure. The item was deleted and an attempt made to remove the duplicate folders but this generated the message "Must enter a valid object specification" follow by "VRS3202202E Path is not unique."
CMS-XML DimCM: Web Client: COR4501551E Error: cannot overwrite file
To work around the issue, just locate the item library as noted in the error message and rename the file. Then reattempt the delivery or check in of the item. Once the item has officially been added, you can delete the renamed file in the item library location.
CMS-XML Dim12: When doing an items deploy on z/os then got this error : MDHFSY0004581E RECFM=U,LRECL>0 not supported for output
DPR "CR_INIT_LIVRAISON_189" /WORKSET="INIT:PRJ_MAINFRAME" /STAGE="LIVRAISON-DEV" /NOCANCEL_TRAVERSE Deploy Request - MDHFSY0005002I MVS member delete of //DD:SRN00000(NAC1SAFF) (EXQL01.DIM.INT.COBOL) failed: EDC5091I The requested function could not be performed because a system utility failed.
CMS-XML KM-Dim7: 'Return item: Error: Failure writing to c:\temp\pcms203_e.tmp error0. No error: Error: Failure to send file to remote host.'
The file is created in the PCMS_TMP location prior to returning to the item library. If the file is larger than the space available, you will need to delete any unnecessary files in that location. If the file is not larger than the disk space available, check the directory permissions for PCMS_TMP.
CMS-XML Dim10: VM2Dim or DT: PCMS0005262E Error: baseline template selected no items, so baseline was not created
Baseline <PROD_ID>:<BASELINE_SPEC> has been forwarded to DMSYS PCM0005262E Error: baseline template selected no items, so baseline was not created RWS "<PROD_ID>:TMP_IMP!!1" Warning : Successfully deleted Project <PROD_ID>:TMP_IMP!!1 Operation completed
CMS-XML Dim12: When doing an UPDATE, an error of MDA4501691E Error: Failed to open file "...\.metadata\....metadata-item" for writing: fopen() failed with 13 (Permission denied) occurs
Scanning local work area: less than 1 microsecond Warning : Restoring deleted file 'C:\Work\S101\code\ data \k2.sql' MDA4501691E Error: Failed to open file "C:\Work\S101\code\data\.metadata\k2.sql.metadata-item" for writing: fopen() failed with 13 (Permission denied).
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