".~#~_del_" temp folder names causing a headache

[matthew.hearne]

We have a flow that moves a lot of folders from a network location, onto the machine running switch, and then onto an archive location again on the network.

For some reason, we are finding that it's leaving behind folders that have been renamed and start with ".~#~_del_"

It seems to be the inject job that we use to get the folder is doing this. I believe it gives the folder a temp name prior to injecting it, and then renames it back to it's original name when done. But for some reason, there are always a number of folders left behind, as if it's not completed the operation.

Has anyone seen a problem like this before and if so, how do we overcome it?

The purpose of the flow is that we receive daily XML from an MIS with information regarding jobs that can be archived. So, we use this XML to go and retrieve the job folder and it's contents from the network storage and then move it to a specified archive location on the network storage.

Thanks,
Matt

[magnussandstrom]

Hi Matt, we have exactly the same problem. We have not found any way to solve it.

Now I delete these manually..

folder.png (106.94 KiB) Viewed 973 times

[billy.olvestad]

Same problem here. No solution here either.

[matthew.hearne]

Thanks for the replies. At least it not just me having the problem then.

It's a real issue for us, because the folders being renamed and not moved, are actually needed (they are just being archived), so we need to keep them and they need to keep their original filename.

How can we highlight this to Enfocus as a worry?

Thanks,
Matt

[laurentd]

I found another quite old post mentioning the same problem: viewtopic.php?t=1164

In short, disabling the "safe move" feature should help. Please give it a try.

How can we highlight this to Enfocus as a worry?
For the record, this forum is a very useful place for discussion between Enfocus users.
Freddy and I consult it regularly and add our two cents where we can.
But we are not always available, for travel and events reasons.

This does not replace our support. You can always open a ticket here:
http://www.enfocus.com/supportportal