Couldn't write to directives file

HI all,
I m running OD 5.6 and using Teamsite Comparison Deploy. I see the following error message
ERROR: Couldn't write to directives file.
.
ERROR: Failed to deploy local_directory[0]: .
ERROR: Failed 1 directories
client: ROLLBACK Transactional Deployment

I did check the forum and there was a posting about this problem in 2003 but there was no resolution mentioned in that posting. I am running TS 6.0 in WIN2k server.
Can anybody provide me some direction about this issue.
Thanks

Find more posts tagged with

Comments

iwovGraduate

Can you post your OD config file ? What are you using for previousArea ? Do you have any editions besides INITIAL ?
Your target OS is Windows or Solaris ?
Is this error in the logs for Sender/Base or Receiver ? Check both for errors and post details if relevant.

gopin77

HI there,
I wiped out my opendeploy and reinstalled it and found the same error.
I m running the sample site (rudimentary configuration), and you can view all the relevant documents in the attached zip file. For the present configuration (mostly default values), the host and the target are the same win2K server. I still get the same error.
Thanks

iwovGraduate

Do you have any editions published (besides INITIAL) ?
If not, then publish an edition and try your deployment again.

Also, try using

<sourceTeamsite area="Y:\store2\main\www\EDITION" previousArea="Y:\store2\main\www\EDITION\INITIAL" >

OR

<sourceTeamsite area="Y:\store2\main\www\EDITION" previousArea="Y:\store2\main\www\EDITION\<GIVE_A_SPECIFIC_EDITION_NAME_HERE>" >

instead of

<sourceTeamsite area="Y:\store2\main\www\EDITION" previousArea="Y:\store2\main\www\EDITION\IW_PREV" >

what happens when you do this?

Migrateduser

Something to check...

Do you have TMP defined as a system variable on the Windows host?

If so, does the directory it points to exist?

If so, does the owner of the OD service have authority to access the directory?

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

gopin77

I did check the TMP variable and it was set and OD service do have rights to those directories. However, I did find a work around solution for this problem that was quite odd. I was able to run opendeploy without any issues when I ran the deploy using the command line tool instead of OD Admin user interface.
$$>iwodstart <deploy config file>
This command ran perfectly and the log files created did'nt have any error details. The files got deployed without any hitch. I did see in the reports that the user id when I ran from command line just specified as "Administrator" while when for my failed attempts the report specified the user as \\<dopmain>\Administrator.
THat was the only change i found in the reports. I dont know whether that holds a solution for the weird behaviour. Thanks for all your help