I have been running Microsoft Money from the first
version and have run Microsoft Money data files off my
server for five plus years. I was running Microsoft
Money 2003 and Money 2004 data files from my Windows 2000
server with out issue for over two years. After doing a
fresh install of Windows 2003 on my server and attempting
to run Money data files off my 2003 server, I can not
longer do it without data corruption of the Money data
file. Something changed with Windows 2003 server.

I am running all high end equipment, 10/100/1000 switched
networks and Windows XP SP1 with all of the Windows
updates. Everything stayed consistent between my servers
(Trend Micro antivirus, Veritas BU, etc) except the
installation of Windows 2003 instead of running Windows
2000 server. The server itself is a dual 1GHz Pentium,
with 5-18GB HDs in a RAID 5 with 2GB of RAM.

MS has given me mixed messages on running Money data
files off a network server depending on when I call.
They first tried to tell me that Money was not supported
on a network, but MS KB articles and the Money Help file
say otherwise (except for running over a UNC). I am NOT
trying to use Money with more than one user in a data
file at the same time. I just want to run the Money data
file on the server for backup and security.

I am using DFS, however I have tried using a straight
drive mapping as well. I have turned my antivirus on and
off on the client and server.

I have also found that Intuit QuickBooks Pro 2003 is
having similar issues. Almost exactly. The same
scenario holds true. It worked with Windows 2000 server
and since the install of Windows 2003 server, if you try
to run the data file on the Windows 2003 server, you run
into data file corruption issues. I have seen this at my
offices and my customer offices, so I know it is not my
network or configuration. Intuit QuickBooks is a multi-
user application and it is designed for such use. Intuit
is looking into this as well.

Has anyone else run into similar situation and is they a
fix or am I missing something.

Thanks.