Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
ERROR: Error writing contents of file
jbonifaci
Alright, I've never actually posted a question before, but here goes... Any ideas what would cause the error below:
ERROR: Error writing contents of file (<filepath>).
ERROR: Could not get file data(<filepath>).
It began happening about a week ago when deploying files from both a 5.5.2 w2k and 6.1 w2k TeamSite server. This has previously been working without any issues for over a year. The files are being deployed to 10 identical w2k web servers, yet only failing to one of them.
Base OD Versions: Version 5.6.0.0.0 Build 18354 Interwoven 20030404
Receiver OD Versions: Version 5.6.0.1.0 Build 21220 Interwoven 20030618
Any ideas would be greatly appreciated.
Find more posts tagged with
Comments
Adam Stoller
Generally speaking, one should have the same-or-newer version of the software running on the Base Server - you seem to have newer software running on the Receiver. This *might* cause the problem - or it might be a red-herring.
If someone (Todd or someone else) doesn't respond soon (Todd's probably recovering from GearUp) - you might consider contacting Support to see if they can help you track down the source of the problem.
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
Migrateduser
Is the failure consistent or intermittent?
Could the target file be locked by IIS or some other process?
Are two deployment legs attempting to update the same target area at the same time?
Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e:
tscallan@interwoven.com
jbonifaci
Hey Todd, thanks for getting back to me, I know you were busy with GearUp this week.
Q: Is the failure consistent or intermittent?
A: It is consistent. I can not deploy any file to any location on the server.
Q: Could the target file be locked by IIS or some other process?
A: It is happening with existing and new files alike, so I would think not.
Q: Are two deployment legs attempting to update the same target area at the same time?
A: No, they are completely separate deployments that deploy to different locations on the server.
Bowker
We've seen this when we ran out of available disk space on the receiver and we have seen this when the permissions on the receiver didn't allow for OD to write them.
Dan Bowker
Northern Trust
Web Publishing Technology
jbonifaci
Thanks Dan, it was the disk space,
.