In general, whenever you get an outgoing (to ClearCase) synchronization
error, you will want to:

- logon to the synchronization machine (the one where you invoked the
syncengine.startup.bat script), using the same userid as you used when
you logged on to invoke the syncengine.startup.bat

- try to execute the cleartool command that failed

In this case, just CD to that directory, i.e.:

M:\DO_NOT_USE_design_project_Int_4082ef77-31b6-4e58-a3f9-65c237c4ae4e\m5a_vob\design\ADM\1000\1010
plan

and see if you can access the file named "Created in CC.txt".

I'm guessing that there is something wrong with the ALBD server on that
machine, or some such thing (the various ClearCase logs should give you
the necessary information to figure out what is wrong).

Alternatively, you can just go initially to the ClearCase logs, and see
if there are any errors reported there (in this case, probably the
view-server logs will probably have some errors).

Cheers,
Geoff


gdang wrote:

After making changes to a file and successful deliver, I performed
'Sync Streams'. The following access denied error is displayed. Any
idea? Thanks.

Synchronization exception: Could not doWriteContent for
location
CONTROLLABLE_RESOURCE|M:/DO_NOT_USE_design_project_Int_4082ef77-31b6-4e58-a3f9-65c237c4ae4e/m5a_vob/design/ADM/1000/1010
plan/Created in CC.txt
Caused by:
M:\DO_NOT_USE_design_project_Int_4082ef77-31b6-4e58-a3f9-65c237c4ae4e\m5a_vob\design\ADM\1000\1010
plan\Created in CC.txt (Access is denied.)
SYNCHRONIZATION FAILED. (Ignore subsequent lines automatically
added by Ant.)