Jump to content

DFS Replication and file sharing violations


Recommended Posts

Guest Richard Price
Posted

Hi,

 

I am using the version of DFS that was introduced in Win2k3 R2, and

keep getting errors appearing in the replication group diagnostic

reports to do with file sharing violations - in other words, files

that were held open by someone when the replication service tried to

replicate the file.

 

Now, at the moment I am simply ignoring these as there is little you

can do, but the fact that the replication diagnostic report flags them

up as errors rather than warnings is a little worrisome - is there

actually something I should infact be doing?

 

Cheers

Richard

  • Replies 1
  • Created
  • Last Reply

Popular Days

Guest Meinolf Weber
Posted

Re: DFS Replication and file sharing violations

 

Hello Richard,

 

If an application opens a file and creates a file lock on it (preventing

it from being used by other applications while it is open), DFS Replication

will not replicate the file until it is closed. If the application opens

the file with read-share access, the file can still be replicated.

Think the only way you have is to teach users to close there files when they

are ready working on it. Or you have to hardly disconnect them via the Open

files in computer management console on the server where the file is opened.

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Hi,

>

> I am using the version of DFS that was introduced in Win2k3 R2, and

> keep getting errors appearing in the replication group diagnostic

> reports to do with file sharing violations - in other words, files

> that were held open by someone when the replication service tried to

> replicate the file.

>

> Now, at the moment I am simply ignoring these as there is little you

> can do, but the fact that the replication diagnostic report flags them

> up as errors rather than warnings is a little worrisome - is there

> actually something I should infact be doing?

>

> Cheers

> Richard


×
×
  • Create New...