Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
ERROR: Couldn't write to directives file.
duartecordeiro
Hi, while trying to do a deployment I get the following log:
(2) client: [Thu Feb 27 10:15:45 2003] Comparing path[Y:\default\main\Internet\GSK_DEV\EDITION\ed_0001] with prev path[Y:\default\main\Internet\GSK_DEV\EDITION\INITIAL]
(3) client: Walking TeamSite directory[.]
(4) client: Teamsite 5.5.2 based deployment
ERROR: Couldn't write to directives file.
.
ERROR: Failed to deploy local_directory[0]: .
ERROR: Failed 1 directories
client: Remote status: server-OK
it seems a permissions problem.
But I don't see any info on this error.
Does someone knows what is this about ?
--
Duarte Cordeiro
Neoris Pootugal
Find more posts tagged with
Comments
Adam Stoller
What version of OpenDeploy are you using?
Can you post (as an attachment) the full log?
--fish
(Interwoven Senior Technical Consultant)
duartecordeiro
> - Open Deploy 5.5.1 SP2
--
Duarte Cordeiro
Neoris Pootugal
Adam Stoller
The log file you included in your zip file looks like only the tail-end of the log file - when I said "full" log - I meant "full" log - the micro log of that deployment (not the macro log) - but you might also include the hostname_odbase.log as well.
--fish
(Interwoven Senior Technical Consultant)
Migrateduser
I too am getting the "ERROR: Couldn't write to directives file" message when trying to do an OpenDeploy deployment. I tried to do a simulate using version 5.6.0.0 of OpenDeploy and TeamSite 5.5.2. Attached is the log file.
David M. Doggette
Certified Interwoven Consultant
Adam Stoller
I don't see anything glaringly wrong that would cause the problem to occur - I'll ask a few colleagues to take a look and hopefully one of them will be able to respond with more information (or at least more questions ...)
--fish
(Interwoven Senior Technical Consultant)
bboyle
did anyone solve this?
I am seeing this error, but only when running a TeamSite area deployment with a "previousArea" for comparison. If there's no previousArea it works.
I've logged it with support but thought I would double check as this thread just ends without any resolution ...