Hi All !
I have a management app running on Server 2008 (R2), which uses the
FileSystemWatcher object in .Net to monitor file change evnts. There are
two servers, where it does not work, like on the other [2008 R2] servers and
re-install is not an option.
This is a long running app, which is in use for several years now and it
is likely NOT a programming related thing [the same program behaves
differently on the two mentioned machines].
The underlying general behavior :
a) monitoted app opens log file, keeping it open. It makes writes from time to time.
b) monitoring app uses filesystemwatcher and get notified about opening/updating
the file once. It then polls the file via FileInfo.Refresh on a timer.
b) causes the filesystemeventwatcher to raise new events on the
"intact" servers, while NOT on the "damaged" servers.
I want to find out, what in the driver chain/underlying filesystem
could cause this behavior.
Any help will be really very great!
Thanks so far and
best regard
++mabra