Troubleshooting
Problem
This technote provides information about possible causes for getting the error, Checked out version, but could not copy data to
Symptom
Symptom 1:
Checkout fails with:
Checked out version, but could not copy data to "M:\vob\dir\file.doc" in view: permission denied. Correct the condition, then uncheckout and re-checkout the element.
Symptom 2:
Attempts to read or checkout file elements in a VOB fail with certain views.
During a checkout operation the following error is reported:
Error checking out 'M\atw11af9_view\f_rimc\dummy\cm_tool.txt'.
Checked out version, but could not copy data to "M:\atw11af9_view\f_rimc\dummy\cm_tool.txt" in view: unknown error in VOB.
Correct the condition, then uncheckout and re-checkout the element.
Unable to check out "M:\atw11af9_view\f_rlmc\dummy\cm_tool.txt".
In the view server log the following entries can be found:
6/12/2007 11:53:26 AM view_server(4576): Error: view_server.exe(4576): Error: Unable to construct cleartext for object "0x3456" in VOB "ambw3r1a:E:\cc_s7p\vobs\infra\S7P_INFRA.vbs": error detected by ClearCase subsystem
6/12/2007 11:53:26 AM view_server(4576): Error: view_server.exe(4576): Error: Unable to construct version.
6/12/2007 11:53:26 AM view_server(4576): Error: (Operation pathname was: "C:\Program Files\Rational\ClearCase\lib\mgrs\text_file_delta\construct_version")
6/12/2007 11:53:26 AM view_server(4576): Error: view_server.exe(4576): Error: Operation "construct_version" unavailable for manager "text_file_delta"
If the element is successfully accessed by a different view, the failing view is then able to access the element without errors.
All views located on a specific machine or machines are affected. Other machines are running fine.
Cause
Possible cause for Symptom 1 above:
There are multiple reasons for this error:
- The file is located inside a directory. During checkout ClearCase is copying the file from the cleartext pool into that directory. This means that the user or the group needs write permissions on the parent directory of the file that is being checkedout. So if for example the directory permissions were 755, the only user who could checkout files in the directory would be the directory owner (as the owner is granted write permissions).
- Verify if the file can be read from within the VOB while checked-in. If the file cannot be read, it cannot be copied.
- If the file can be read, it means that the VOB storage permissions are OK.
- If the file cannot be read, it means that the VOB storage permissions are problematic.
Note: If the permissions were not OK, this would cause an MVFS error to be seen from a dynamic view as well. Also when the view storage permissions or the share permissions are insufficient, you would normally see an Access Denied message and not Permission Denied. Being able to copy the file into the view requires that the correct write permissions are applied to the view storage directory.
- This error can also occur if the "ClearCase Administrator" group owns the VOB.
- The user is a member of the parent directories group but this is not set as ClearCase primary group.
Possible cause for Symptom 2 above:
ClearCase is unable to construct the file element version being accessed which under the covers creates a cleartext container for that version. The underlying failure is caused by a permissions restriction on the type manager map file (located by default in: C:\Program Files\Rational\ClearCase\lib\mgrs) which blocked ClearCase from reading that file. The ClearCase albd user (service account user) must be able to read the map file in order to construct the cleartext container.
Diagnosing The Problem
Diagnosing Symptom 2:
Using a tool such as Process Monitor (procmon) to monitor the view server will expose the problem where the albd user is unable to open the type manager map file.
Resolving The Problem
Resolution options for Symptom 1:
- If the issue is related to permissions on the directory element, run the cleartool protect command to add the correct privileges.
Example: cleartool protect -chmod 777 <directory where file element resides>
Review the IBM Rational ClearCase Command Reference Guide on the topic of protect (cleartool man protect) for more information. - If the issue is related to the view storage area, try correcting the protections on the view storage directory using operating system commands and functionality. It may also be necessary to use fix_prot to correct the protections on the view as detailed in technote 1142606.
Example:
%> fix_prot -r -chown <user name> -chgrp <primary group> -chmod 775 <Path to View storage>
%> fix_prot -root -chown <user name> -chgrp <primary group> <Path to View storage>
- If the "ClearCase Administrator" group owns the VOB, refer to the following technote for instructions on how to resolve the issue.
Technote 1264867 Problems that occur if the ClearCase Administrator group owns the VOB or VOB objects .
WORKAROUND:
If the above does not resolve the problem, then a new view storage area could be created. You can try moving the view to the new location, refer to technote 1129835 for guidance.
Resolution for Symptom 2:
- Windows: The permissions on the ClearCase installation directory and sub-directories must allow full control for the ClearCase administrators group. If this is not the case, modify your permissions accordingly.
Refer to technote 1143292 "About ClearCase permissions on Windows" for additional permissions information.
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21146571