W2K3 DFS/FRS and temporary files

[Michel]

Hi,

We're using a DFS/FRS setup and everything is working ok. Problems
arrise with applications, like for example Excel (97) and tailer-made
Clipper applications when reorganising data (dbf/ndx).

The problem is already described in the list of issues fixed in
Windows 2000 post-SP3 (ntfrs.exe, google on Q811370), and seems to
(re)appear in Windows 2003.

For the unenlighted:
- Connect an FRS'ed set (for example \\server1\share )
- Edit an excel file on the share
- Save the file
- Et voila, you're stuck with a random 8 character filename (the xls).

I know Excel's behaviour (save under temporary name, write succesfull
then delete old file and rename temporary name to original filename).
The problem also appears with Clipper applications reorganising tables
(using temporary files); there files also 'dissapear'.

I've tried frsdiag (res.kit), but that reports everything's ok with
both FRS systems..

Anyone similar problems/experiences with Windows 2003?

Regards,
Michel

Note: when replying through e-mail, remove the nospam from the address

[Richard Chinn [MSFT]]

For future FRS related questions, you may want to try posting to
microsoft.public.windows.server.dfs_frs.

You need to get the latest FRS QFE for Windows Server 2003. That is
Q823230; it has the same fix as Q811370 for W2K.

You may also want to consider installing Ultrasound to monitor your FRS
replica's health. To get Ultrasound, go to http://www.microsoft.com/frs.
Follow the link for "FRS Troubleshooting and Monitoring." You should see
the link for Ultrasound there. Note you will need to follow the
instructions in the Ultrasound help file (FRS Monitoring Help File) to
install Ultrasound - it requires MSDE (free) or a SQL database.

--Richard

Please post FRS related questions to microsoft.public.windows.server.dfs_frs
and prefix the subject line with "FRS:" to make it easier to spot. Note
that FRS is used to replicate SYSVOL on domain controllers and DFS root and
link targets.

For additional FRS resources, please visit http://www.microsoft.com/frs.

This posting is provided "AS IS" with no warranties, and confers no rights.

Post by Michel
Hi,
We're using a DFS/FRS setup and everything is working ok. Problems
arrise with applications, like for example Excel (97) and tailer-made
Clipper applications when reorganising data (dbf/ndx).
The problem is already described in the list of issues fixed in
Windows 2000 post-SP3 (ntfrs.exe, google on Q811370), and seems to
(re)appear in Windows 2003.
- Connect an FRS'ed set (for example \\server1\share )
- Edit an excel file on the share
- Save the file
- Et voila, you're stuck with a random 8 character filename (the xls).
I know Excel's behaviour (save under temporary name, write succesfull
then delete old file and rename temporary name to original filename).
The problem also appears with Clipper applications reorganising tables
(using temporary files); there files also 'dissapear'.
I've tried frsdiag (res.kit), but that reports everything's ok with
both FRS systems..
Anyone similar problems/experiences with Windows 2003?
Regards,
Michel
Note: when replying through e-mail, remove the nospam from the address

[Michel]

On Mon, 9 Feb 2004 17:12:53 -0800, "Richard Chinn [MSFT]"

Post by Richard Chinn [MSFT]
For future FRS related questions, you may want to try posting to
microsoft.public.windows.server.dfs_frs.
You need to get the latest FRS QFE for Windows Server 2003. That is
Q823230; it has the same fix as Q811370 for W2K.

We have no (support) contract with MS, neither does the customer. Can
we obtain the QFE through support (phone) ?

regards,
Michel

[Richard Chinn [MSFT]]

QFEs are available for free. Call the MS support number and refer to the
QFE(s) you need.

--Richard

Please post FRS related questions to microsoft.public.windows.server.dfs_frs
and prefix the subject line with "FRS:" to make it easier to spot. Note
that FRS is used to replicate SYSVOL on domain controllers and DFS root and
link targets.

For additional FRS resources, please visit http://www.microsoft.com/frs.

This posting is provided "AS IS" with no warranties, and confers no rights.

Post by Michel
On Mon, 9 Feb 2004 17:12:53 -0800, "Richard Chinn [MSFT]"

Post by Richard Chinn [MSFT]
For future FRS related questions, you may want to try posting to
microsoft.public.windows.server.dfs_frs.
You need to get the latest FRS QFE for Windows Server 2003. That is
Q823230; it has the same fix as Q811370 for W2K.

We have no (support) contract with MS, neither does the customer. Can
we obtain the QFE through support (phone) ?
regards,
Michel