R6025 pure virtual function call error on 2006 deluxe with XP

[Jason3fc]

I have the trial 2006 deluxe edition of Money. I have been using it
fine for about 2 months until just yesterday it started giving me this
error after I do an update to retrieve info from my bank.

Runtime Error!

Program:..gram files\Microsoft Money 2006\MNYCoreFiles\msmoney.exe

R6025
- pure virtual function call

I found a KB article on older version of money and it suggests
registering Cyptography DLLs which it doesnt work that way on XP. I
also found some mention of reinstalling MDAC which I tried by
reinstalling the MDAC.INF from my XP install files. None of this works.
I even uninstalled and reinstalled, restored my backup and it still
fails. Any ideas?

This occurs after the information has been downloaded and it says
"updating accounts" up in the corner.

I am on XP SP2

[Matt]

Hi Jason,

I've just started experiencing this problem as well. Recently I installed
iTunes and the MS Fingerprint reader. I can't imagine it's a coincidence. I
have found several references to this problem but haven't tried any fixes yet
- that's on today's to-do list.

Here's what I found:
http://pftalk.com/ftopic38971.html
http://www.generation.net/~hleboeuf/er6025.htm
http://support.microsoft.com/?kbid=240437

[Matt]

Well, I spent some time tinkering around. My quest finally brought me to

http://groups.google.com/group/microsoft.public.uk.money/browse_thread/thread/80f531a81226f657/4ce97eb7decd746d?lnk=st&q=microsoft+money+r6025&rnum=10&hl=en#4ce97eb7decd746d

Which instructed me to create a regkey...
HKCurrentUser\Software\Microsoft\Money\11.0
New DWORD: DeleteLifeTimePlan, Value set to 1.

I have no idea why this worked but it did - or at least appears to have.

There was another thing I tried earlier today that looked promising because
it dealt with crypto machine keys but that didn't fix. Basically, I went to
my all users application data microsoft\rsa\crypto\machinekeys location and
found one file that I didn't have access to. I used Properties to correct
this. I was pointed here from a KB article that I can't find now. But again,
this didn't fix the problem by itself and I don't know enough about this area
to recommend anything else.

[Jason3fc]

Matt,

Thanks for the for the pointers. I tried both and niether worked. I
also had a crypto key I didnt have permissions on. I'll keep trying.
This is pretty frustrating, I was really getting some serious use out
of this program. Just when I started to depend on it, and planned on
buying it, this happened.