DFS Replication errors - sharing violation and losing files etc

[Idris]

Hi,

We set up DFS (R2) on two servers with full two way replication 24/7.

It works fine for most of the time.

However we often get errors with event ID of 4303 saying:
The DFS Replication service has been repeatedly prevented from replicating a
file due to consistent sharing violations encountered on the file. The
service failed to stage a file for replication due to a sharing violation.

We also get 4412:

The DFS Replication service detected that a file was changed on multiple
servers. A conflict resolution algorithm was used to determine the winning
file. The losing file was moved to the Conflict and Deleted folder.

Every now and again our users ring up and say a certain file is missing or
not the latest one and we have to find it in the conflicted folder and
restore it for them. It's becoming tiresome and awkward.

I've a few questions.
Why do these happen? The only thing i can guess or see is that more than 1
user has the file open and so it can't replicate? These are mainly .mdb
files that have the problems.

We're in a position now where we're looking to turn of DFS because we can't
solve it.

Someone suggested using one way replication only but my thoughts are this
will still happen?

To try and solve the problem we asked users to target one server instead of
the namespace but it still happens?

Does anyone have any ideas on what might be causing this and how we could
resolve?

If not does anyone know of a similiar program that could be used?

Thanks.

[Hii Sing Chung]

Hi, I am experiencing exactly the same type of problems. I forced all my
users to only target one server, and indeed they are, but still in the event
logs it keep on saying a file is changed on multiple servers and move to
conflictanddeleted folder. It is very weird. I recall that this happen only
after we changed the antivirus from Mcafee to Forefront, but it may just be
a coincidence. The problem is really a serious one. Somebody please
enlighten us.

"Idris" <id...@iddiinisde.com> wrote in message
news:OY$2bVsVI...@TK2MSFTNGP06.phx.gbl...

[Zman@discussions.microsoft.com Bill Zman]

I am experiencing the same "sharing violation" problem. Shows up
periodically then goes away on the diagnostic report. I'm set up with a
one-way replication from a branch office over a big pipe (OC3) and don't have
any other errors showing up in the log. Anyone else?

[Mangrum@discussions.microsoft.com Joe Mangrum]

I am getting the same issue coming up. I am about to test out a software
package called Peerlock which should eliminate the issues with people opening
files one one server and not registering on the others, if that is the case
that should handle the error, however this is not for certain. If anyone else
has some input I would be very interested in hearing about it