We thought that too, but our ftp area is not being used to display the
files, its just a publication point that later on is picked up by a
Liveserver import job. The only thing connected to the ftp site is the
publication job itself. Its happened forever this one, but it doesnt
actually seem to
We get it all the time... its due to files being locked / accessed on
the webserver which the ftp is occurring.
On 16 July, 00:29, markus giesen markus.gie...@gmail.com wrote:
The weird thing is, that it is not a permanent error.
It shows up every now and then.
On 15 Jul., 04:18, Rob Palmer
The weird thing is, that it is not a permanent error.
It shows up every now and then.
On 15 Jul., 04:18, Rob Palmer robpalmer...@gmail.com wrote:
Markus:
That looks like the sort of error message we get with the wrong FTP
setting (active vs. passive). Try changing that in the [Administer
Markus:
That looks like the sort of error message we get with the wrong FTP
setting (active vs. passive). Try changing that in the [Administer
Publication - Project - Edit General Settings] zone.
-Rob.
On Jul 13, 1:03 am, markus giesen markus.gie...@gmail.com wrote:
Hey folks,
did anyone of
Markus--
Not specifically. But if I am to attempt a guess, it is due to a binary file
transfer failure in your ftp process. It could be a file lock or corrupted
binary file in the src folder.
But you can take the process out of RedDot by directly ftp (or sftp) from
the folder to your target box
