I have tried this fix and I still get the same error.

I have obviously done uninstalls and clean installs and
still have the problem. I'm using the same OS and SP as
previous inquiry.

- quote -

I had the same problem (posted 3/26) and had an open
incident report with MS. They couldn't help me. Through a
little investigation of the .DLL's I located a problem
with a video controller. Something someone in the
newsgroup said about eFax triggered a memory. Here's what
worked for me... I have eFax as well. I disabled the live
menu function in eFax (there are a lot of new programs
using live menu and sharing MSO dll's) and reloaded my
video driver. I've not had the problem since. I also
disabled the sponsor support links within money and
disabled automatic updates from MS so nothing is
overwritten without my knowledge. This worked for me, but
there's no guarantee it will work for everyone. It's worth
a shot if you're like me and actually NEED access to your
files
- quote -

Try start-> run and reregister the msxml3.dll file with the command regsvr32
msxml3.dll


--
Glyn Simpson, Microsoft MVP - Money

Check http://support.microsoft.com/default...d=fh;EN-GB;mny
for UK tips and fixes for MS Money. To send Microsoft your wishes or
suggestions, use http://register.microsoft.com/mswish/suggestion.asp
or email mnyukwsh[at]microsoft.com especially if it's a UK specific wish.

I do not respond to any unsolicited email regarding Money


"Ernie" <ebiancarelli[at]_NO_SPAM_comcast.net> wrote in message
news:1ae8901c41e86$26181560$a101280a[at]phx.gbl...
- quote -

I've been using Money 2004 for several months. The other
day it stoped working and it generated this error dialog
box:
Runtime Error!
Program: c:\Program Files\Money2004\System\msmoney.exe
abnormal program termination


I've run msmoney.exe via GDB and found that the
segmentation fault occurs here:
(0x73ea393d) - MFC42 DllGetClassObject+3681175

I have Windows XP, with SP1a installed. My ole32.dll
version is 5.1.2600.1263(xpsp2.030819-2129) if that helps.

Can someone at Microsoft debug this problem further and
determine the root cause of this error?